Head to head · Market fundamentals · October 2026 research run

BeliefState vs Financial Datasets

BeliefState and Financial Datasets score within a point of each other on agent readiness, 61.1 (C) and 61.1 (C). Financial Datasets leads on reliability, agent ergonomics and transparency & trust. Both do market fundamentals.

Best financial market data APIs for AI agents · All 89 markets comparisons

Which one, for what

BeliefState C

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 80
  • Security & auth, 59 against 49
  • Payments & pricing, 84 against 69
  • Maintenance & community, 78 against 56

Watch for

Which sources the theses come from, and under what rights, isn't on any public page

Financial Datasets C

Best for An agent doing US company research from SEC-sourced statements, filings, insider and institutional data that wants to pay per call with no account, or a small team on credits.

Ahead on

  • Reliability, 43 against 20
  • Agent ergonomics, 73 against 67
  • Transparency & trust, 63 against 52

Watch for

No status page, incident history or published uptime; the Professional plan's SLA terms aren't public

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.

Reliability Financial Datasets +23

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.

Financial Datasets 43

Graded as a hosted service. No status page was found; status.financialdatasets.ai does not resolve and no page links one (0), so there is no incident history to read (5). The only published limit is 10,000 requests a minute per wallet over x402, with monthly request caps per plan and none per minute for keyed plans (8 of 15). The OpenAPI file declares 429 and the x402 page documents a 503 with Retry-After from the facilitator and a duplicate_payment check on replayed signatures (10 of 15). The Professional plan lists uptime SLAs, with no figure published (10). The API is generally available (10). Total 43.

Maintenance & community BeliefState +22

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.

Financial Datasets 56

UK fundamentals went live on 26 October 2026, India on 23 October, with Japan and South Korea dated for November on the coverage page (30). Dated changes in the last 90 days are x402 on 23 October, UK fundamentals on 26 October, terms and subprocessor list on 29 October, privacy policy on 20 August, with no changelog as such (12 of 20). Contact is a form and the dashboard; no support email, Discord or forum was found, and the GitHub organisation's four repositories couldn't be read because the GitHub API rate limit was reached (6 of 15). The PyPI package is 0.1.18 of 26 May 2024 by the founder, and the docs point to the OpenAPI file and the MCP server rather than an SDK (5 of 15). Package health unknown, dependencies not checked (3 of 10). Total 56.

Payments & pricing BeliefState +15

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.

Financial Datasets 69

x402 on the vendor's own endpoints for every documented GET data endpoint, 36 of them, with the last 365 days only and a Non-Professional licence; full history, the market snapshot, filing items and the POST endpoints need a key (35 of 40). Plan prices and overage rates are public, and each x402 endpoint quotes its price in the 402 header, $0.02 on /earnings (20). No free tier or trial found; data calls return 402 until an account holds credits, from $20 (0). An agent can pay by x402 with no account, or open an account with POST /agent/signup and have the owner fund it (20). Total 75. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 35 of 40 is 8.75 of 10, and the other lines' 40 is 60 at 30 each, so 75 is 69.

Transparency & trust Financial Datasets +11

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.

Financial Datasets 63

A closed service under terms dated 29 October 2026 that name Financial Datasets, Inc., set New York law, and state the licence per plan (15 of 30). The privacy policy of 20 August 2026 gives retention periods (accounts up to seven years after closure, API and MCP logs up to three years, backups 90 days), says inputs aren't used for training, and links a subprocessor list; no DPA text was found (24 of 30). No deprecation policy; the terms say the Services may be discontinued and material changes get reasonable notice (3 of 20). Subprocessors (AWS, Heroku, Stripe, Google sign-in, Vercel) and the United States as hosting location are disclosed (18 of 20). Total 60.

Security & auth BeliefState +10

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.

Financial Datasets 49

A plain account key in the X-API-KEY header only, revoked from the dashboard, with no scopes, rotation or expiry; the MCP server adds OAuth 2 with PKCE (plain and S256), dynamic client registration, a revocation endpoint and one scope (20 of 30). Every data endpoint is a read; the x402 route and agent signup don't change the account beyond funding it (15 of 20). Filing text, filing items and news are third-party content, with no guidance on treating them as untrusted (5 of 15). The privacy policy says requests and responses are logged for up to three years; no per-call log is shown to the key holder (5 of 15). security.txt returns 404 and no bounty, SOC 2 or ISO 27001 was found; the terms ask for prompt notice of a compromised key and a subprocessor list is published (4 of 20). Total 49.

Schema & documentation BeliefState +6

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.

Financial Datasets 80

OpenAPI 3.0.1 at financialdatasets.ai/openapi.json, 68 operations with 13 response codes and one security scheme, named the source of truth by the docs (25). llms.txt and a Markdown twin of every page (10). Every operation has a description, and the 402 terms carry a resource description that says when an agent should use the endpoint (17 of 20). 330 parameters, 36 with enums, 32 required, no free-form blobs (12 of 15). Code samples in Python, JavaScript and curl, x402 error values documented, but response examples on only six operations in the spec (11 of 15). No API version and no changelog; the news page has four dated posts in 2026 (5 of 15). Total 80.

Score by category

CategoryWeight this runBeliefStateFinancial DatasetsEdge
Reliability16%202043Financial Datasets +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28680BeliefState +6
Agent ergonomics13%16.26773Financial Datasets +6
Security & auth14%17.55949BeliefState +10
Payments & pricing10%12.58469BeliefState +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87856BeliefState +22
Transparency & trust7%8.85263Financial Datasets +11
Negative events≤1500
TotalC 61.1/100C 61.1/100

Facts side by side

FactBeliefStateFinancial Datasets
KindHTTP APIHTTP API
VendorBeliefStateFinancial Datasets, Inc.
Hosted endpointhttps://beliefstate.ai/v1/research/mcphttps://api.financialdatasets.ai
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402yes, from $0.02/callyes, from $0.02/call
Tools exposed2328
Read-only variant documentedyesno
llms.txtyesyes
MCP registryai.beliefstate/investor-researchnot listed
Last release2026-11-102026-10-26
Terms last updatednot read yet2026-10-29
Privacy policy last updatednot read yet2026-08-20
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text

How the scores have moved

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.

Financial Datasets

Every documented GET data endpoint takes x402 with no key, failed calls uncharged, and an agent can open and fund an account by API. A public OpenAPI file, llms.txt and a 28-tool OAuth MCP server cover the same data. There is no status page or free tier, keyed rate limits aren't published, and x402 data stops at 365 days.

Before you call either

BeliefState

  1. Check coverage first with the free get_tickers or get_companies; an absent ticker means unreleased, not unknown
  2. Show the x402 quote to the user and keep the exact URL, body and signature; on 503 payment_pending retry those, never pay again
  3. Start a company with get_brief, then open cases with get_case; get_search_results costs 1.50 USDC a call
  4. Keep each record's publication date and first-seen date apart, and read source_text_coverage before treating a source as complete
  5. Don't use the device-flow API key inside a hosted chat; use OAuth there

Financial Datasets

  1. Without a key, read the price from the PAYMENT-REQUIRED header of the 402 and pay with x402 on Base; each page of next_page_url is a separate paid request
  2. Keep limit small and ask for one period at a time; premium endpoints count as 2, 4 or 8 requests on keyed plans
  3. Send the key only to api.financialdatasets.ai in the X-API-KEY header; on 401 ask the owner for a new key rather than signing up again
  4. Treat a 402 on a keyed account as an empty balance and mint a checkout link for the owner; don't retry the call
  5. Check the plan's licence before showing the data to anyone else; redistribution needs Professional or Enterprise

Questions

Which is better for AI agents, BeliefState or Financial Datasets?

BeliefState and Financial Datasets score within a point of each other on agent readiness, 61.1 (C) and 61.1 (C). Financial Datasets leads on reliability, agent ergonomics and transparency & trust.

Do BeliefState and Financial Datasets need an API key?

BeliefState needs an API key. Financial Datasets takes an API key or an OAuth sign-in. An agent can also pay BeliefState per call over x402, with no account. An agent can also pay Financial Datasets per call over x402, with no account.

Can an agent call BeliefState and Financial Datasets without installing anything?

Yes. BeliefState has a hosted endpoint at https://beliefstate.ai/v1/research/mcp and Financial Datasets at https://api.financialdatasets.ai.

Other comparisons with BeliefState or Financial Datasets

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.