Stock scores your code — and your agent — can call

The AI Score ranks covered companies against each other at a point in time. It is not a forecast, a price target or a probability. Its measured forward ranking power is small and concentrated in short horizons — /v1/track-record returns the real figures, including the horizons where it has shown none, and /proof explains them in plain language. Nothing here is investment advice, and no endpoint places a trade.

export BMI_KEY=bmi_live_your_key

curl -H "Authorization: Bearer $BMI_KEY" \
  https://brimindinvest.com/api/v1/scores/NVDA

$env:BMI_KEY = "bmi_live_your_key"

Invoke-RestMethod -Uri "https://brimindinvest.com/api/v1/scores/NVDA" `
  -Headers @{ Authorization = "Bearer $env:BMI_KEY" } | ConvertTo-Json -Depth 5

AI Score, verdict band, universe rank and the six factor scores for one stock.

curl -H "Authorization: Bearer $BMI_KEY" \
  https://brimindinvest.com/api/v1/scores/NVDA

{
  "data": {
    "symbol": "NVDA",
    "score": 81,
    "rank": 62,
    "band": { "key": "strong-buy", "label": "Strong Buy" },
    "factors": {
      "value": 23, "growth": 94, "profitability": 88,
      "health": 76, "momentum": 71, "risk": 44
    },
    "asOf": "2026-09-25T00:00:00.000Z"
  },
  "meta": { "ratiosAreFractional": true }
}

Batch lookup. Results come back in the order you asked for; anything outside the scored universe is listed in notFound rather than dropped.

curl -H "Authorization: Bearer $BMI_KEY" \
  "https://brimindinvest.com/api/v1/scores?symbols=NVDA,AMD,INTC"

{
  "data": [ { "symbol": "NVDA", "score": 81, ... }, ... ],
  "notFound": ["XYZQ"],
  "meta": { "requested": 4, "returned": 3, "truncatedToPlanLimit": null }
}

Screen the ranking. rank=top|bottom, with optional limit, minScore and maxScore.

curl -H "Authorization: Bearer $BMI_KEY" \
  "https://brimindinvest.com/api/v1/scores?rank=top&limit=25&minScore=80"

Every score we have published for a symbol, oldest first. Never revised after publication, so it is an audit trail rather than a backtest.

curl -H "Authorization: Bearer $BMI_KEY" \
  "https://brimindinvest.com/api/v1/scores/NVDA/history?days=365"

The graded forward performance of the score against SPY: hit rate, excess return, within-day rank correlation and per-band results at 5, 21 and 63 trading days.

curl -H "Authorization: Bearer $BMI_KEY" \
  https://brimindinvest.com/api/v1/track-record

The valuation, growth, margin, balance-sheet, risk and dividend metrics the score is computed from, grouped by theme.

curl -H "Authorization: Bearer $BMI_KEY" \
  https://brimindinvest.com/api/v1/fundamentals/NVDA

Daily closes and volume, one bar per trading day. The same bars /v1/track-record is graded on, so a backtest built here reproduces our published figures.

curl -H "Authorization: Bearer $BMI_KEY" \
  "https://brimindinvest.com/api/v1/prices/NVDA?days=730"

Resolve a company name or partial ticker. Searches our own universe, so every result is answerable by the rest of the API.

curl -H "Authorization: Bearer $BMI_KEY" \
  "https://brimindinvest.com/api/v1/symbols?q=nvidia"

What this key is, which plan it is on, and how much of today's quota is left.

curl -H "Authorization: Bearer $BMI_KEY" \
  https://brimindinvest.com/api/v1/me

A filer's filings, newest first. The entry point: everything else needs an accession number. Filter by form and date; asking for 10-K also returns 10-K/A, because an amendment is the current truth for that period.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings?ticker=AAPL&form=10-K&limit=3"

{
  "data": [
    {
      "accession": "0000320193-25-000079",
      "form": "10-K",
      "filed_at": "2025-11-01",
      "period": "2025-09-27",
      "items": [],
      "primary_document": "aapl-20250927.htm",
      "source_url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000079/"
    }
  ],
  "meta": { "company": "Apple Inc.", "returned": 3, "truncated": false }
}

The section outline of one filing: what is in it, how long each part is, and where each one starts and ends in the normalized text. This is the call to make before asking for text, so a budget can be spent on the section that matters. `is_stub` marks a section under 500 characters, which is usually the filer saying "none" or pointing at the proxy statement.

curl -H "Authorization: Bearer $BMI_KEY"   https://brimindinvest.com/api/v1/filings/0000320193-25-000079/sections

{
  "data": [
    {
      "section_name": "item_1a_risk_factors",
      "label": "Item 1A. Risk Factors",
      "part": "I",
      "item": "1A",
      "char_start": 14982,
      "char_end": 73551,
      "char_length": 58569,
      "paragraph_count": 118,
      "is_stub": false
    }
  ],
  "meta": {
    "form": "10-K",
    "parser_version": 2,
    "normalized_char_length": 205471,
    "source_url": "https://www.sec.gov/Archives/..."
  }
}

One section as chunks that fit a token budget you set. Paragraphs are never split unless one alone exceeds the budget, and then the pieces say so. Follow `next_page_token` until it is null. Accepts the full id, "Item 1A" or "item_1a".

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/0000320193-25-000079/sections/item_1a_risk_factors?max_tokens=1500"

{
  "data": [
    {
      "text": "The Company's business, reputation, results of operations...",
      "para_idx": 0,
      "char_start": 15042,
      "char_end": 16380,
      "token_count": 271,
      "citation": "AAPL 10-K 2025-11-01 (0000320193-25-000079) Item 1A, para 0, chars 15042-16380"
    }
  ],
  "meta": {
    "section_name": "item_1a_risk_factors",
    "parser_version": 2,
    "tokenizer": "o200k_base",
    "paragraph_count": 118,
    "section_token_count": 14238,
    "max_tokens": 1500,
    "returned": 6,
    "returned_tokens": 1487,
    "next_page_token": "eyJhIjoiMDAwMDMyMDE5My0yNS0wMDAwNzki..."
  }
}

What changed in one section between two filings, paragraph by paragraph: added, removed and rewritten, each with a citation into the filing it came from. The structural answer to "what is new in this year's risk factors", without sending both documents to a model and asking it to spot the difference.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/diff?accession_a=0000320193-24-000123&accession_b=0000320193-25-000079&section=item_1a_risk_factors"

The same section across a filer's recent filings, in one call. Three years of MD&A without three round trips and without the caller having to resolve three accession numbers first.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/cross-section?ticker=AAPL&section=item_7_mda&lookback=3"

Recent 8-K events for one filer, tagged by the item number that was reported, so "did they change auditors" is a filter rather than a reading exercise. Item 5.02 is officer changes, 2.02 is results, and so on.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/events?ticker=AAPL&lookback_days=90"

Insider transactions read out of Form 4 filings: who, what, how much, at what price, and whether it was an open-market trade or an award. Cluster buys are computed with a definition you can move, because one person's cluster is another's coincidence.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/insider?ticker=AAPL&lookback_days=90&transaction_codes=open_market"

Institutional holdings from Form 13F, either by manager or by stock: who holds it, how much, and how that changed from the quarter before. Ask by manager for a portfolio, by ticker for a shareholder list.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/holdings?ticker=NVDA&quarter=latest"

Segment revenue, operating income and store counts as the filer tagged them, grouped by breakdown: by reportable segment, by product, by geography. Answers which part of the business grew, which a consolidated income statement cannot. Store and location counts come from the filing's own concept index, under topic=counts.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/segments?ticker=WMT&lookback=3"

A company's revenue growth beside its industry's, period by period, with the difference in percentage points. The denominator is the US Census survey covering the filer's SIC code, summed over the exact fiscal period the company reported. Needs no API keys of its own: Census is read directly when CENSUS_API_KEY is set and through FRED's keyless mirror otherwise.

curl -H "Authorization: Bearer $BMI_KEY"   "https://brimindinvest.com/api/v1/filings/sector?ticker=WMT&periods=5"

Settings → Developer → Edit Config. Restart the app afterwards.

{
  "mcpServers": {
    "brimindinvest": {
      "command": "npx",
      "args": ["-y", "@brimindinvest/mcp"],
      "env": { "BRIMINDINVEST_API_KEY": "bmi_live_your_key" }
    }
  }
}

One command. Add --scope project to share it with your team via .mcp.json.

claude mcp add brimindinvest \
  --env BRIMINDINVEST_API_KEY=bmi_live_your_key \
  -- npx -y @brimindinvest/mcp

~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one.

{
  "mcpServers": {
    "brimindinvest": {
      "command": "npx",
      "args": ["-y", "@brimindinvest/mcp"],
      "env": { "BRIMINDINVEST_API_KEY": "bmi_live_your_key" }
    }
  }
}

goose configure → Add Extension → Command-line Extension, or edit ~/.config/goose/config.yaml.

extensions:
  brimindinvest:
    enabled: true
    type: stdio
    cmd: npx
    args: ["-y", "@brimindinvest/mcp"]
    envs:
      BRIMINDINVEST_API_KEY: bmi_live_your_key
    timeout: 300

opencode.json in the project, or ~/.config/opencode/opencode.json globally.

{
  "mcp": {
    "brimindinvest": {
      "type": "local",
      "command": ["npx", "-y", "@brimindinvest/mcp"],
      "enabled": true,
      "environment": { "BRIMINDINVEST_API_KEY": "bmi_live_your_key" }
    }
  }
}

Open the MCP configuration from the Agent panel's tools menu, then refresh the server list.

{
  "mcpServers": {
    "brimindinvest": {
      "command": "npx",
      "args": ["-y", "@brimindinvest/mcp"],
      "env": { "BRIMINDINVEST_API_KEY": "bmi_live_your_key" }
    }
  }
}