Head to head · Market fundamentals · October 2026 research run

BeliefState vs TickerLayer

BeliefState scores 61.1 (C) on agent readiness against TickerLayer's 57.2 (C), and leads in 2 of 7 scored categories. TickerLayer leads on reliability, agent ergonomics and payments & pricing. 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

  • Security & auth, 59 against 49
  • Transparency & trust, 52 against 38

Also in its favour

  • No incidents deducted, where TickerLayer loses 15 points for them

Watch for

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

TickerLayer C

Best for An agent that needs latest prices, bars and market hours across stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures from one schema, and wants to pay per call without an account.

Ahead on

  • Reliability, 70 against 20
  • Agent ergonomics, 79 against 67
  • Payments & pricing, 98 against 84

Also in its favour

  • Free to start without a card

Watch for

The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange

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 TickerLayer +50

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.

TickerLayer 70

Read with the hosted lines, on the REST API. status.tickerlayer.com is an UptimeRobot page linked from the site header (20). Its monitors and history load by script from /api/, which its robots.txt disallows, so no incident record was read, as for eodhd and apitemplate-io (5). Limits are published with numbers, 10 requests a second per account on Free and Individual, 100 on Business, and monthly call quotas per feed (15). The OpenAPI file's 429 carries Retry-After and a body with retryAfterMs, resetsAt and a code that separates the per-second limit from the monthly quota, and every response has carried X-RateLimit-Limit and X-RateLimit-Remaining since 14 September 2026. Every data operation is a GET, and x402 retries with the same payment identifier return the stored response (15). An SLA is named only for Enterprise under a written agreement and as 'partially available' on Business, with no published terms or figure, and the terms of use promise no uptime. Financial-datasets took 10 for SLAs listed on a self-serve plan, so this is half (5 of 10). No beta or preview label on the REST API, the MCP server or the x402 gateway (10). 20+5+15+15+5+10 = 70.

Payments & pricing TickerLayer +14

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.

TickerLayer 98

x402 on the vendor's own gateway, x402.tickerlayer.com, for 41 GET routes. That is six routes for each of stocks, forex, crypto, indices, ETFs and commodities, plus bond yields and four market-calendar routes. Perpetuals, Futures CFDs, the add-ons, the symbol catalogue and WebSocket need a key. Between massive's 30 for US stock routes only and financial-datasets' 35 for every documented data endpoint (32 of 40). Per-call x402 prices from 0.01 to 0.10 USDC in the catalogue and docs, and plan prices per feed on the pricing page, all without a login (20). A Free plan of 3,000 REST calls every 30 days with 'no card', per llms.txt (20). An agent with a funded Base wallet pays per call with no account or key (20). 32+20+20+20 = 92. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 32 of 40 is 8 of 10, and the other lines' 60 is 90 at 30 each, so 92 is 98.

Transparency & trust BeliefState +14

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.

TickerLayer 38

The editorial half. A closed service whose terms of use, user agreement and market data disclaimer (all effective 3 November 2026) set out internal, commercial and redistribution rights by plan and a liability cap. They name no legal entity, address or governing law, so the contracting party is unknown. The plugin and npm client are MIT. Soldfetch took 10 in the same position (10 of 30). The privacy policy keeps WebSocket connection records for 7 days but gives no period for request and tool-call logs or account data after closure, says nothing on model training, names no transfer mechanism and has no DPA (12 of 30). No deprecation policy. The terms allow MCP tools to change 'with reasonable notice where practical' and the user agreement promises notice before a plan is materially reduced, and the changelog records changes after the fact. Kite took 4 (4 of 20). Subprocessors are given only as categories (hosting, authentication, card and crypto payments, email, an AI model for support replies), with analytics vendors deferred to the cookie policy, no data locations, and no named data suppliers (4 of 20). 10+12+4+4 = 30. The provenance half is computed from the provenance block.

Agent ergonomics TickerLayer +12

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.

TickerLayer 79

Read on the REST API, with the MCP server where a line covers it. Responses are sized by limit (bars up to 5,000, catalogue up to 1,000), sort, date ranges and batch calls for futures quotes and market status, with no field selection. The MCP server has 12 tools, 11 shown to the model. Massive and financial-datasets took 15 (15 of 25). limit, offset and next_offset, cursors on fundamentals and economic events, total_count on bars, search on symbols and updated_since on signals (18 of 20). Errors carry statusCode, message, a code, retryAfterMs, resetsAt, limitRps, plansUrl and the missing product or market, and the skill gives an action per status. Above financial-datasets' 16 (17 of 20). Every data call is a GET, and x402 settles only after a valid response with payment identifiers bound to the request, but no readOnlyHint or other annotation was found for the MCP tools. Financial-datasets took 14 without annotations (15 of 20). Data tools need only asset_class and symbol, with defaults for limit and sort, and official clients exist for JavaScript or TypeScript and Python, both at 0.1.0 from 20 October 2026. Stocks need the COUNTRY:TICKER form (14 of 15). 15+18+17+15+14 = 79.

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.

TickerLayer 49

A plain account key with no scopes, shown once and replaced by regenerating it in the dashboard (20). The OpenAPI file defines an apiKey query parameter as a 'compatibility fallback', and the WebSocket takes the key only in its URL, so 10 off. The MCP server adds OAuth 2.1 with PKCE S256, dynamic registration, refresh tokens, a revocation endpoint and one scope, market.read. Twelve-data took 18 on the same pattern, one less here because the WebSocket has no header option (17 of 30). Every operation reads data, and the OAuth scope is read-only, as for twelve-data and financial-datasets (15 of 20). Responses are prices, bars, symbols, calendars and yields. There is no news feed, and SignalPoint signals are structured fields, so no untrusted text reaches the agent (10 of 15). Rate-limit headers on every response, quota 429s that state the limit and when it renews, and a dashboard list of WebSocket connections with source IP, key and how each ended (24 October 2026). No per-call REST log for the key holder was found, though the privacy policy says request logs are kept (7 of 15). security.txt answered a client error, and no disclosure policy, bug bounty, SOC 2 or ISO 27001 was found (0 of 20). 17+15+10+7+0 = 49.

Score by category

CategoryWeight this runBeliefStateTickerLayerEdge
Reliability16%202070TickerLayer +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28688TickerLayer +2
Agent ergonomics13%16.26779TickerLayer +12
Security & auth14%17.55949BeliefState +10
Payments & pricing10%12.58498TickerLayer +14
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87879TickerLayer +1
Transparency & trust7%8.85238BeliefState +14
Negative events≤150-15
TotalC 61.1/100C 57.2/100

Facts side by side

FactBeliefStateTickerLayer
KindHTTP APIHTTP API
VendorBeliefStateTickerLayer
Hosted endpointhttps://beliefstate.ai/v1/research/mcphttps://mcp.tickerlayer.com/mcp
TransportsStreamable HTTPHTTP, Streamable HTTP, websocket
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402yes, from $0.02/callyes, from $0.01/call
LicencenoneProprietary hosted service under the TickerLayer terms of use, user agreement and market data disclaimer (all effective 3 November 2026), which name no legal entity or governing law. Free and Individual plans are for internal use, Business adds use inside the customer's own product, and redistribution needs a written Enterprise agreement. The agent plugin (github.com/tickerlayer/agent-plugin) and the npm client are MIT
Tools exposed2312
Read-only variant documentedyesno
llms.txtyesyes
MCP registryai.beliefstate/investor-researchcom.tickerlayer/market-data
Last release2026-11-102026-11-06

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.

TickerLayer

An agent can read quotes, bars and market hours across eight asset classes through a documented REST API, 12 MCP tools or 41 x402 resources with no account, and 429s carry Retry-After. The data is derived from unnamed non-exchange sources, no operator is named, and the status history couldn't be read.

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

TickerLayer

  1. Write stocks as COUNTRY:TICKER, such as US:KO, and always pass asset_class to the data tools.
  2. If a 429 carries REST_QUOTA_EXCEEDED, stop and tell the user. Waiting doesn't reset the monthly quota.
  3. Present prices as indicative TickerLayer values, never as official exchange prices.
  4. Call get_market_status before you report a quiet symbol as missing data.
  5. Send the key in the x-api-key header, never as the apiKey query parameter.

Questions

Which is better for AI agents, BeliefState or TickerLayer?

BeliefState scores 61.1 (C) on agent readiness against TickerLayer's 57.2 (C), and leads in 2 of 7 scored categories. TickerLayer leads on reliability, agent ergonomics and payments & pricing.

Do BeliefState and TickerLayer need an API key?

BeliefState needs an API key. TickerLayer 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 TickerLayer per call over x402, with no account.

Can an agent call BeliefState and TickerLayer without installing anything?

Yes. BeliefState has a hosted endpoint at https://beliefstate.ai/v1/research/mcp and TickerLayer at https://mcp.tickerlayer.com/mcp.

Other comparisons with BeliefState or TickerLayer

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.