Head to head · Market fundamentals · October 2026 research run
BeliefState vs Finnhub
BeliefState scores 61.1 (C) on agent readiness against Finnhub's 47 (D), and leads in 6 of 7 scored categories. Finnhub leads on reliability. Both do market fundamentals. BeliefState accepts x402. Finnhub doesn't.
Best financial market data APIs for AI agents · All 89 markets comparisons
Which one, for what
Best for Agents doing equity research that want who said what about a US stock, why, and what changed, with citations.
Ahead on
- Schema & documentation, 86 against 58
- Agent ergonomics, 67 against 56
- Security & auth, 59 against 32
- Payments & pricing, 84 against 45
- Maintenance & community, 78 against 60
- Transparency & trust, 52 against 27
Also in its favour
- An agent can pay per call over x402, with no account
Watch for
Which sources the theses come from, and under what rights, isn't on any public page
Finnhub D
Best for Agents that need one key across quotes, fundamentals, estimates, filings and transcripts with official libraries, and a free key for prototypes.
Ahead on
- Reliability, 48 against 20
Also in its favour
- Free to start without a card
Watch for
The Swagger document declares the key only as a token query parameter, and the examples carry it in the URL
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing BeliefState +39
BeliefState 84
x402 v2 on the vendor's own domain for all 20 paid research tools, over HTTP and the wallet MCP server; /v1/beliefs and /v1/sources need a key (9 of 10). Per-call prices (0.02, 0.50 and 1.50 USDC) and plan prices published without a login (30). Free ticker, company and SEC-filing discovery with no account or wallet, and five signup credits for eligible new accounts; no free research call without paying or signing up was found (15 of 30). An agent with a funded Base wallet buys research with no account or key (30). 9+30+15+30 = 84.
Finnhub 45
No x402, MPP or L402 (0). Plan prices are public without login, read from the pricing page's script data, sold per dataset by the month with calls a minute rather than per call (10). A free key at 60 calls a minute with no card, which the pricing FAQ says can be used forever (20). The key comes from a browser signup and no key API was found (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Reliability Finnhub +28
BeliefState 20
Read with the hosted lines. No status page found; /status returns 404 and /v1/status is an account utility (0). No incident history to read (5). No rate limits with numbers found in the docs, agents.md or the OpenAPI file, though the x402 routes list a 429 response (0). The quickstart documents Retry-After on a 503 payment_pending and retrying the same saved request and signature, which returns the original response instead of charging twice, and says what a 402 or 410 means (10 of 15). No SLA (0). The wallet routes carry no preview label, but some API references are marked Preview, the MCP guide says open registration stays closed until a public admission gate passes, and A2A is gated (5 of 10). 0+5+0+10+0+5 = 20.
Finnhub 48
Read with the hosted lines. No status page was found on the site, in the docs document or on the MCP page (0), so no incident history could be read (5). Limits are published with numbers, 60 calls a minute on the free key, 150 to 900 a minute by plan, and 30 calls a second on top of every plan (15). The docs say the limit answers 429 and the MCP page says to wait a minute, with no Retry-After or backoff guidance (8 of 15). The home page says 99.99 per cent uptime with an SLA available for enterprise clients (10). The API is generally available (10). 0 + 5 + 15 + 8 + 10 + 10 = 48.
Schema & documentation BeliefState +28
BeliefState 86
OpenAPI 3.1.0 with 48 operations, request and response schemas, and an x402 security scheme. The MCP tool schemas weren't read because robots.txt closes /mcp (23 of 25). llms.txt, agents.md, skill.md, index.md and Markdown tool pages (10). Descriptions say when to use each tool and when to use another, such as starting company overviews with get_brief and paging get_cases only when the user wants more (18 of 20). Typed parameters and bounds on the operations read, not checked for every tool (11 of 15). Examples on tool pages, a sample Broadcom record, and error guidance for 402, 409, 410 and 503 (12 of 15). Routes under /v1, dated OpenAPI publications and a dated changelog, but pages disagree on counts in the same week: the quickstart says fourteen data tools at 0.02 USDC, the FAQ and agents.md eighteen, and the account server is 25 tools in the changelog and 26 on the tools page (12 of 15). 23+10+18+11+12+12 = 86.
Finnhub 58
A public Swagger 2.0 document covers 116 paths with a description on every operation, declaring the key as a query parameter and a 200 response only; the MCP tools were not read (20 of 25). /llms.txt returns the site's HTML shell and no Markdown docs exist (0 of 10). Each operation states its purpose, a premium marker and, on quote, advice against polling, with little on when not to use it (14 of 20). Required flags and types are set on 248 parameters, but allowed values such as news categories sit in description text and no enum is declared (8 of 15). Every operation has example URLs and sample code in five languages, while the only documented error is the 429 (9 of 15). The path carries v1 and no changelog or dated change notes were found (7 of 15). 20 + 0 + 14 + 8 + 9 + 7 = 58.
Security & auth BeliefState +27
BeliefState 59
OAuth browser sign-in for account MCP with one revocable grant per client, and revocable read-only workspace keys made through device authorisation and stored as hashes. The pricing page calls keys scoped, but no scope list or rotation was found (24 of 30). Every tool reads, and the device-flow key is read-only (18 of 20). Results include text drawn from third-party research, news and filings. The docs tell agents to check sources and flag partial or unverified source text, with no prompt-injection guidance (6 of 15). A usage and credit metering endpoint and x402 receipts, with no per-call log found (6 of 15). security.txt is valid but its contact is a personal Gmail address, and no disclosure policy, bug bounty or certification was found (5 of 20). 24+18+6+6+5 = 59.
Finnhub 32
One key per account with no scopes, documented as token= in the query string or an X-Finnhub-Token header, and the Swagger document declares only the query form. The MCP server uses OAuth with fixed public client ids and keeps the key from the assistant (20 less 10 for the query string, plus 2 for the MCP route, so 12). Every data operation is a read (15 of 20). News, transcripts and filings are third-party text and no guidance was found (5 of 15). No usage log for the key holder was found (0 of 15). security.txt redirects to the home page and no disclosure policy, bug bounty or certification was found (0 of 20). 12 + 15 + 5 + 0 + 0 = 32.
Transparency & trust BeliefState +25
BeliefState 52
The editorial half. A closed service whose terms (version 2026-10-16) name a Wyoming LLC with its filing ID and say outputs can be wrong and need review. The integrations repository is MIT. Which publications the theses come from, and under what rights, isn't stated on a page the public can read; /v1/sources needs a key (13 of 30). The privacy policy lists data categories, Google API Limited Use, encrypted provider credentials and retired Discord data, but gives no retention periods for API calls and no DPA (12 of 30). Lifecycle labels with announcement and removal dates since 4 September 2026, but eleven routes were retired without aliases on 9 September with no notice period (8 of 20). No subprocessors or data locations named (2 of 20). 13+12+8+2 = 35. The provenance half is computed from the provenance block.
Finnhub 27
A closed service whose terms exist at a page that robots.txt disallows, so they were not read; the pricing page says every self-serve plan is personal use, and no legal entity or governing law was found (8 of 30). No privacy policy was found, /privacy redirecting to the home page (0 of 30). No deprecation policy or dated notices found (0 of 20). Stripe and Braintree scripts load on the site, but no processor list or data location is disclosed (0 of 20). 8 + 0 + 0 + 0 = 8.
Maintenance & community BeliefState +18
BeliefState 78
Read as a closed service. The newest dated change is the registry entry 1.1.1 on 10 November 2026, after changelog entries on 8 November (30). Six dated changelog days from 3 September to 8 November (20). A public changelog, support@beliefstate.ai, @beliefstate on X and a docs feedback tool, none tested (8 of 15). Six versions in the official MCP registry under the domain-verified namespace ai.beliefstate (15). The MIT integrations repository has 18 commits since 27 October, three pinned x402 dependencies, tests and no CI workflow (5 of 10). 30+20+8+15+5 = 78.
Finnhub 60
Read as a closed service. The newest dated change is 2 November 2026, when finnhub-go, finnhub-ruby and finnhub-php gained a price target history endpoint; the MCP page is dated 6 August 2026 (30). Only that one dated change falls in the last 90 days, the previous library commits being 22 June 2026 (5 of 20). Support by email, with no public changelog or community channel found (5 of 15). Six official client libraries, finnhub-python at 2.4.29 of 24 June 2026 (15). The libraries are generated from the API document; no CI run was visible and the Python README names an older version than PyPI (5 of 10). 30 + 5 + 5 + 15 + 5 = 60.
Score by category
| Category | Weight this run | BeliefState | Finnhub | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 20 | 48 | Finnhub +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 58 | BeliefState +28 |
| Agent ergonomics | 13%16.2 | 67 | 56 | BeliefState +11 |
| Security & auth | 14%17.5 | 59 | 32 | BeliefState +27 |
| Payments & pricing | 10%12.5 | 84 | 45 | BeliefState +39 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 78 | 60 | BeliefState +18 |
| Transparency & trust | 7%8.8 | 52 | 27 | BeliefState +25 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.1/100 | D 47/100 |
Facts side by side
| Fact | BeliefState | Finnhub |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BeliefState | Finnhub |
| Hosted endpoint | https://beliefstate.ai/v1/research/mcp | https://finnhub.io/api/v1 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, websocket |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for market fundamentals | not published | $50 per month (plan) |
| x402 | yes, from $0.02/call | no |
| Tools exposed | 23 | 70 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | ai.beliefstate/investor-research | not listed |
| Last release | 2026-11-10 | 2026-11-02 |
| Terms last updated | not read yet | couldn't be read |
| Privacy policy last updated | not read yet | no document linked |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | none | 1.1k stars |
How the scores have moved
BeliefState
No score change since it was listed.
Verdicts
BeliefState
Agents can buy cited investor theses, price targets, risks and revisions per call by x402 with no account, at published USDC prices, or connect by OAuth or a read-only key. Sources and their rights aren't public, there is no status page or rate-limit figure, and docs pages disagree on tool counts.
Finnhub
A public Swagger document covers 116 endpoints, six official client libraries exist, and a free key gives 60 calls a minute with no card. The key is documented in the query string, no status page, changelog, error reference or privacy policy was found, and robots.txt kept the terms from our reader.
Before you call either
BeliefState
- Check coverage first with the free
get_tickersorget_companies; an absent ticker means unreleased, not unknown - Show the x402 quote to the user and keep the exact URL, body and signature; on 503
payment_pendingretry those, never pay again - Start a company with
get_brief, then open cases withget_case;get_search_resultscosts 1.50 USDC a call - Keep each record's publication date and first-seen date apart, and read
source_text_coveragebefore treating a source as complete - Don't use the device-flow API key inside a hosted chat; use OAuth there
Finnhub
- Send the key as the
X-Finnhub-Tokenheader, not astoken=in the URL, and keep under 30 calls a second on top of the plan's per-minute limit - Check the
premiummarker before calling; a free key reaches 29 operations and the rest answer with an error - Poll /quote sparingly; the docs say constant polling is not recommended and point to the websocket for real-time updates
- Expect 401
{"error":"Please use an API key."}without a key and 429 over the limit; wait a minute before retrying, as the MCP page advises - Self-serve plans are personal use; anything commercial needs the enterprise contact route
Questions
Which is better for AI agents, BeliefState or Finnhub?
BeliefState scores 61.1 (C) on agent readiness against Finnhub's 47 (D), and leads in 6 of 7 scored categories. Finnhub leads on reliability.
Do BeliefState and Finnhub need an API key?
BeliefState needs an API key. Finnhub takes an API key or an OAuth sign-in. An agent can also pay BeliefState per call over x402, with no account.
Can an agent call BeliefState and Finnhub without installing anything?
Yes. BeliefState has a hosted endpoint at https://beliefstate.ai/v1/research/mcp and Finnhub at https://finnhub.io/api/v1.
Other comparisons with BeliefState or Finnhub
- Alpha Vantage vs Finnhub
- Databento vs Finnhub
- Finnhub vs Intrinio
- Finnhub vs Massive (formerly Polygon.io)
- Finnhub vs TickerLayer
- Finnhub vs Tiingo
- Finnhub vs Twelve Data
- Alpha Vantage vs BeliefState
- BeliefState vs Benzinga
- BeliefState vs EODHD
- BeliefState vs Eulerpool Financial Data API
- BeliefState vs Financial Datasets
- BeliefState vs Financial Modeling Prep
- BeliefState vs Intrinio
- BeliefState vs TickerLayer
- BeliefState vs Tiingo
- BeliefState vs Twelve Data
- Eulerpool Financial Data API vs Finnhub
- Financial Datasets vs Finnhub
- Financial Modeling Prep vs Finnhub
- EODHD vs Finnhub
- Benzinga vs Finnhub
Machine-readable
- This page as Markdown
/compare/beliefstate-vs-finnhub.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/beliefstate.json·/api/v1/tools/finnhub.json - From a terminal
anchor compare beliefstate finnhub(the CLI) - Over MCP
compare_tools {"a": "beliefstate", "b": "finnhub"}at/mcp, no key