Head to head · Market fundamentals · October 2026 research run

BeliefState vs Twelve Data

Twelve Data scores 71.9 (BB) on agent readiness against BeliefState's 61.1 (C), and leads in 4 of 7 scored categories. BeliefState leads on security & auth and payments & pricing. Both do market fundamentals. BeliefState accepts x402. Twelve Data doesn't.

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

  • Security & auth, 59 against 54
  • Payments & pricing, 84 against 45

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

Twelve Data BB

Best for Agents that need prices and time series across many exchanges and asset classes with one contract, CSV output, and a documented error table.

Ahead on

  • Reliability, 83 against 20
  • Agent ergonomics, 84 against 67
  • Transparency & trust, 67 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card

Watch for

The REST docs and OpenAPI accept the key as ?apikey= in the query string alongside the header

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 Twelve Data +63

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.

Twelve Data 83

Read with the hosted lines. A public status page at twelvedata.isitup.cloud lists Price API, Fundamentals API, WebSocket and Website with uptime figures (20). Its history shows two incidents in the 90 days to 3 November 2026, 20 minutes of unavailability across the three APIs on 1 September and 16 minutes on the WebSocket on 14 October, minor only (20). Limits are published with numbers, credits a minute by plan from 8 to 10,946 and 800 a day on Basic (15). The docs document a 429 on the limit and the usage endpoint, with no Retry-After or backoff guidance; reads only (8 of 15). The terms sell a 99.9 per cent SLA with service credits, and the Enterprise plan carries 99.99 per cent (10). The REST API and MCP server are generally available (10). 20 + 20 + 15 + 8 + 10 + 10 = 83.

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.

Twelve Data 45

No x402, MPP or L402 (0). Plan prices are public without login in pricing.md and on the pricing page, sold by credits a minute per month rather than per call (10). A free Basic plan at 800 credits a day with no card (20). The key comes from a browser signup and no key API was found; MCP needs an OAuth login by a person (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.

Agent ergonomics Twelve Data +17

BeliefState 67

23 wallet tools and 26 account tools, in the 11 to 30 band (15). Briefs come in overview, current and full views, cases page with a cursor, and filters cover investor, direction, time, changed_since and as_of cut-offs (18 of 20). Documented status meanings and recovery steps for payment states, with no full error-code table found (15 of 20). An unfinished purchase is retried with the same saved URL, body and signature, and the docs say not to pay twice. MCP annotations couldn't be read (12 of 20). Few required arguments on the tools read. No official SDK; a Postman collection, plugins and an MIT examples repository (7 of 15). 15+18+15+12+7 = 67.

Twelve Data 84

The REST API is the surface graded. outputsize 1 to 5,000 with a default of 30, format=CSV, dp, date ranges and batch requests size responses, and the MCP server lists 27 tools (20 of 25). Date ranges, outputsize and exchange, country and type filters, with no cursor pagination (15 of 20). Error codes with meanings an agent can branch on, 403 for plan limits and 429 for credits (16 of 20). Every operation is a read, and the MCP source marks tools readOnlyHint (18 of 20). Few required parameters, a demo key, and official SDKs in Python, Node.js, Go, Java and R (15). 20 + 15 + 16 + 18 + 15 = 84.

Transparency & trust Twelve Data +15

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.

Twelve Data 67

A closed service under terms that name the entity, define internal use, business use and redistribution, and were last updated 1 January 2026; the MCP repository is open source but ships no licence file (15 of 30). The privacy policy of 22 September 2026 states retention periods and names its processors, the terms require data deletion within 30 days of termination, and no DPA is named (20 of 30). No deprecation policy or notice period; the terms allow changes and the monthly updates record them after the fact (3 of 20). Subprocessors are named on the privacy policy and the trust centre, with no data locations beyond transfer mechanisms (12 of 20). 15 + 20 + 3 + 12 = 50.

Security & auth BeliefState +5

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.

Twelve Data 54

The REST key is a plain per-account key with no scopes, accepted as a header or as ?apikey= (20 less 10 for the query string). The hosted MCP server refuses keys and uses OAuth 2.1 with PKCE, a resource indicator, refresh tokens, revocation and one scope, which lifts the credential model for that surface (18 of 30). Every operation is a read (15 of 20). Company news is third-party text and no guidance was found (5 of 15). An /api_usage endpoint and dashboard usage give the key holder a view of consumption, not a per-call log (6 of 15). A trust centre on SafeBase lists SOC 2, GDPR and CCPA and ten policies; no security.txt, disclosure process or bug bounty was found (10 of 20). 18 + 15 + 5 + 6 + 10 = 54.

Score by category

CategoryWeight this runBeliefStateTwelve DataEdge
Reliability16%202083Twelve Data +63
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28683BeliefState +3
Agent ergonomics13%16.26784Twelve Data +17
Security & auth14%17.55954BeliefState +5
Payments & pricing10%12.58445BeliefState +39
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87882Twelve Data +4
Transparency & trust7%8.85267Twelve Data +15
Negative events≤1500
TotalC 61.1/100BB 71.9/100

Facts side by side

FactBeliefStateTwelve Data
KindHTTP APIHTTP API
VendorBeliefStateTwelve Data Pte. Ltd.
Hosted endpointhttps://beliefstate.ai/v1/research/mcphttps://api.twelvedata.com
TransportsStreamable HTTPHTTP, Streamable HTTP, stdio, websocket
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402yes, from $0.02/callno
Tools exposed2327
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryai.beliefstate/investor-researchnot listed
Last release2026-11-102026-10-12
Terms last updatednot read yet2026-01-01
Privacy policy last updatednot read yet2026-09-22
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularitynone791 stars

How the scores have moved

BeliefState

No score change since it was listed.

Twelve Data

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.

Twelve Data

A public OpenAPI 3.1 document with error responses on all 187 operations, Markdown docs and pricing for agents, a status page with two short incidents in 90 days, and an MCP server behind OAuth 2.1. The REST key still travels in the query string as a documented option, no enums are declared, and free and individual plans forbid company use.

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

Twelve Data

  1. Send the key as Authorization: apikey <key>, not in the URL; the hosted MCP server takes OAuth only, so never paste a key into a connector's key field
  2. Set outputsize (1 to 5,000, default 30) and format=CSV on time_series to keep responses small, and read status in the JSON body since errors come with HTTP codes and a message
  3. Count credits, not calls; most endpoints cost one credit per symbol and the Basic plan allows 8 a minute and 800 a day, with 429 when exceeded
  4. A 403 means the key's plan lacks the endpoint or symbol, not a bad key; check pricing.md before escalating
  5. Use trial symbols from twelvedata.com/exchanges to test premium data on the free plan

Questions

Which is better for AI agents, BeliefState or Twelve Data?

Twelve Data scores 71.9 (BB) on agent readiness against BeliefState's 61.1 (C), and leads in 4 of 7 scored categories. BeliefState leads on security & auth and payments & pricing.

Do BeliefState and Twelve Data need an API key?

BeliefState needs an API key. Twelve Data 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 Twelve Data without installing anything?

Yes. BeliefState has a hosted endpoint at https://beliefstate.ai/v1/research/mcp and Twelve Data at https://api.twelvedata.com.

Other comparisons with BeliefState or Twelve Data

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.