{ "data": { "a": { "slug": "databento", "name": "Databento", "vendor": "Databento, Inc.", "vendorUrl": "https://databento.com", "kind": "http-api", "category": "market-data", "summary": "Databento is a market data platform with historical and live tick, order book and bar data for US and European equities, futures, options and indices, through HTTP and streaming APIs with Python, C++ and Rust clients.", "url": "https://www.anchorterminal.com/tools/databento", "markdownUrl": "https://www.anchorterminal.com/tools/databento.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/databento.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/databento.json", "dns": "databento.grade.anchorterminal.com", "repo": "https://github.com/databento/databento-python", "license": "Apache-2.0 (clients)", "transports": [ "http" ], "remoteUrl": "https://hist.databento.com", "packages": [ { "registry": "pypi", "name": "databento" } ], "auth": "api-key", "authNotes": "API key (32 characters starting `db-`) created in the portal, up to 100 per account with unique names, rotated or deleted from the portal, and sent as the username in HTTP Basic auth (`-u $KEY:`). Team members can be given per-member permissions. The vendor revokes keys it finds published. No query-string option.", "pricing": "usage", "pricingNotes": "Historical data is metered per GB of uncompressed binary data at rates per dataset in the portal catalogue, with no subscription; batch jobs are billed once and streams per byte sent. New users get $125 of credits valid six months, one set per team, for historical data or the first month of a plan. Live data needs a plan, Standard at $199 a month (no licence fees), Plus $1,750 and Unlimited $4,500 a month in licence fees on annual contracts by sales. Metadata, symbology and account calls are free.", "priceSummary": "$199 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt, pricing page or release notes (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 309, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://databento.com/docs/", "llmsTxt": "https://databento.com/docs/llms.txt", "capabilities": [ "market.prices", "market.history", "market.indices", "data.markets" ], "tags": [ "official", "hosted", "usage", "usage-priced", "free-tier", "llms-txt", "status-page", "pre-1.0", "python", "rust", "closed-source" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 663, "ranked": true, "rankOf": 1520, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 84, "payments": 22, "reliability": 50, "schema": 75, "security": 61, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Exchange-level tick and order book data metered per GB, with published per-IP rate limits, Retry-After on 429, dated release notes and clients in three languages. The HTTP API is still at major version 0, the status page lists two critical and several major incidents in 90 days, there is no OpenAPI document, and the legal pages were unreadable.", "bestFor": "An agent that needs exchange-level trades, quotes, order book and bar data for US and European futures, options and equities, or corporate actions and a security master, and can budget per GB.", "strengths": [ "Per-IP rate limits published with numbers, 429 with Retry-After, and a documented error format with a code, a message and a docs link", "`metadata.get_cost` quotes a request before it is billed, batch jobs are billed once with 30 days of re-download, and a monthly historical spending limit can be set in the portal", "Dated release notes per component with breaking changes and deprecations called out, and Python 0.85.0 to 0.89.0 released between 25 August and 28 October 2026", "Up to 100 named API keys per account with rotation, per-member permissions, and keys found in public revoked by the vendor", "$125 of credits at signup and metered historical pricing with no subscription; metadata and symbology calls are free" ], "weaknesses": [ "Two critical and several major incidents on the status page in the 90 days to 3 November 2026, mostly Historical API outages and batch job delays", "The HTTP API is at major version 0 and the docs say it is not considered stable", "No OpenAPI document; per-GB rates sit in the portal catalogue behind a login, and the pricing page shows plans only", "The terms and privacy policy are drawn by script and could not be read, and no security.txt, SOC 2 or ISO 27001 was found", "Live data and the Plus and Unlimited plans need a subscription on an annual contract by sales, and signup is in a browser" ], "agentNotes": [ "Call `metadata.get_cost` before `timeseries.get_range`, and set a monthly historical limit in the portal; a duplicate streaming request is charged twice", "Send the key as the Basic auth username (`-u $DATABENTO_API_KEY:`) to hist.databento.com/v0; never put it in the URL or source code", "On 429 wait for the Retry-After header; keep under 100 time series requests a second and 20 batch submissions a minute per IP", "Check status.databento.com before retrying a slow or 504 Historical request, since several incidents since August were API outages or batch delays", "Use batch download for requests over 5 GB, split by time range or `limit`, and read `schema` and `stype_in` from the dataset page before querying" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 80, "maintenance": 84, "payments": 22, "reliability": 50, "schema": 75, "security": 61, "transparency": 28 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install databento", "http": "curl -G 'https://hist.databento.com/v0/metadata.list_datasets' -u $DATABENTO_API_KEY:" }, "letme": { "capability": "https://letme.dev/market.prices", "tool": "https://letme.dev/databento" }, "area": "domain-data", "unitPrices": [ { "item": "Standard plan", "unit": "month", "usd": 199, "note": "live data, no licence fees, monthly" }, { "item": "Plus plan licence fees", "unit": "month", "usd": 1750, "note": "annual contract, by sales" }, { "item": "Unlimited plan licence fees", "unit": "month", "usd": 4500, "note": "annual contract, by sales" } ], "provenance": { "legalEntity": "Databento, Inc.", "domain": "databento.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://databento.com/legal/terms", "privacy": "https://databento.com/legal/privacy", "statusPage": "https://status.databento.com", "changelog": "https://databento.com/docs/release-notes", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "Databento, Inc. is named in the about page footer and as the GitHub organisation's name. The legal pages at databento.com/legal, /legal/terms and /legal/privacy answer 200 with a script shell and no text, so the terms, privacy policy, legal entity details and any automated-access clause are unread.", "databento.com/robots.txt disallows only /portal for all crawlers. status.databento.com and roadmap.databento.com allow reading.", "RDAP for databento.com was refused (403 from rdap.org), so the registration date is unchecked.", "/.well-known/security.txt returns 404.", "The status page is an Atlassian Statuspage at status.databento.com with Portal, Historical, FTP and seven live-feed components." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/databento.json", "live": { "slug": "databento", "probe": { "target": "https://hist.databento.com", "method": "get", "lastAt": "2026-11-11T06:59:33.033123073Z", "lastOk": true, "lastStatus": 200, "lastMs": 312, "authRequired": false, "uptime24h": 95.49, "uptime30d": 99.1, "p50ms24h": 356, "p95ms24h": 6309, "samples24h": 244, "samples30d": 1558, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 240 }, { "date": "2026-11-07", "probes": 243, "ok": 242 }, { "date": "2026-11-08", "probes": 243, "ok": 243 }, { "date": "2026-11-09", "probes": 243, "ok": 242 }, { "date": "2026-11-10", "probes": 244, "ok": 234 }, { "date": "2026-11-11", "probes": 72, "ok": 71 } ], "since": "2026-11-04T00:00:00Z" }, "vendorStatus": { "page": "https://status.databento.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-11T06:54:49.539441883Z" }, "versions": [ { "registry": "github", "name": "databento/databento-python", "version": "v0.90.0", "released": "2026-11-03", "seenAt": "2026-11-11T05:50:33.222656286Z" }, { "registry": "pypi", "name": "databento", "version": "0.90.0", "released": "2026-11-03", "seenAt": "2026-11-11T05:50:31.211637922Z" } ], "githubStars": 311, "pypiWeekly": 334751, "securityTxt": { "url": "https://databento.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-10T16:08:37.60216587Z" }, "llmsTxt": { "url": "https://databento.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-10T15:42:50.973302279Z" }, "domain": { "domain": "databento.com", "registered": "2019-09-13", "source": "https://rdap.verisign.com/com/v1/domain/databento.com", "checkedAt": "2026-11-08T14:48:04.428143356Z" }, "pages": [ { "url": "https://databento.com/docs/release-notes", "kind": "changelog", "status": 304, "checkedAt": "2026-11-10T16:13:01.418028981Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "029092e580e4" }, { "url": "https://databento.com/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-10T16:13:03.623117583Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0d15ff5427bd" }, { "url": "https://databento.com/legal/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-10T16:13:05.622592739Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0d15ff5427bd" } ], "github": { "repo": "databento/databento-python", "checkedAt": "2026-11-09T09:44:16.845309716Z", "stars": 310, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-03T19:24:17Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 3, "issuesClosed90d": 3, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 29, "success": 29, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-03T19:23:48Z" }, "replies": { "sampled": 25, "unanswered": 0, "medianDays": 0.2 } }, "updatedAt": "2026-11-11T06:59:33.033123073Z" }, "streak": { "days": 7, "from": "2026-11-04", "sinceWatching": true, "best": 7 } }, "answer": "TickerLayer scores 71.5 (BB) on agent readiness against Databento's 60.3 (C), and leads in 3 of 7 scored categories. Databento leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "tickerlayer", "name": "TickerLayer", "vendor": "TickerLayer", "vendorUrl": "https://tickerlayer.com", "kind": "http-api", "category": "market-data", "summary": "TickerLayer is a market data API for stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures, over REST and WebSocket with an API key, a hosted MCP server and pay-per-call x402 access in USDC on Base.", "url": "https://www.anchorterminal.com/tools/tickerlayer", "markdownUrl": "https://www.anchorterminal.com/tools/tickerlayer.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tickerlayer.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tickerlayer.json", "dns": "tickerlayer.grade.anchorterminal.com", "repo": "https://github.com/tickerlayer/agent-plugin", "license": "Proprietary 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", "transports": [ "http", "streamable-http", "websocket" ], "remoteUrl": "https://mcp.tickerlayer.com/mcp", "packages": [ { "registry": "npm", "name": "tickerlayer" }, { "registry": "pypi", "name": "tickerlayer" } ], "auth": "mixed", "authNotes": "REST takes an API key in the `x-api-key` header. The OpenAPI file also defines `ApiKeyQuery`, an `apiKey` query parameter described as a 'compatibility fallback' that 'keeps the key in logged URLs', and the WebSocket at wss://stream.tickerlayer.com takes the key only in the URL as `apiKey`. A person creates the key in the dashboard after a browser signup. It is shown once and has no scopes, and regenerating it invalidates the previous key. The hosted MCP server takes the key as `x-api-key` or `Authorization: Bearer`, or OAuth 2.1 against https://api.tickerlayer.com (authorisation code with PKCE S256, dynamic client registration, refresh tokens, a revocation endpoint and one scope, `market.read`). The x402 gateway at https://x402.tickerlayer.com needs no account or key (https://tickerlayer.com/llms.txt, https://tickerlayer.com/openapi.json, https://tickerlayer.com/docs/mcp, https://api.tickerlayer.com/.well-known/oauth-authorization-server, https://tickerlayer.com/terms-of-use, checked 2026-11-10).", "pricing": "freemium", "pricingNotes": "Free plan at 0 USD with no card, per llms.txt, covering crypto, forex and US stocks over REST, 3,000 calls every 30 days, 10 requests a second, no WebSocket, internal use only. Individual plans are priced per feed, 49 USD a month for crypto, commodities or indices, 59 USD for forex or ETFs and 59 to 99 USD per stock market (United States 99 USD), each with 250,000 REST calls a month, 1 WebSocket connection and 10 symbols. Business runs 449 to 999 USD per feed with 25 million calls and 100 requests a second, for use inside the customer's own product. Perpetuals 179 or 799 USD, Futures CFDs 219 or 849 USD, add-ons (overnight session, SignalPoint, Fundamentals, Bonds) 39 to 449 USD. Yearly billing is 20 per cent lower. Enterprise is custom, with redistribution and an SLA. Without an account, x402 charges 0.01 to 0.10 USDC a call on Base and settles only after a valid response (https://tickerlayer.com/pricing, https://tickerlayer.com/llms.txt, https://tickerlayer.com/ai/x402.md, checked 2026-11-10).", "priceSummary": "$0.01 / call", "where": "hosted", "x402": { "level": "yes", "evidence": "Production gateway https://x402.tickerlayer.com on Base mainnet (`eip155:8453`) in USDC, with a sandbox at https://x402-testnet.tickerlayer.com on Base Sepolia. The catalogue lists 41 GET resources, scheme exact, protocol version 2, facilitator `coinbase-cdp-mainnet`, accountRequired false. Six routes each for stocks, forex, crypto, indices, ETFs and commodities, plus bond yields and four market-calendar routes. Perpetuals, Futures CFDs, the add-ons and WebSocket are not covered. Settlement only after a valid response, and payment identifiers bound to the request (https://x402.tickerlayer.com/catalog, https://tickerlayer.com/ai/x402.md, checked 2026-11-10).", "endpoints": [ { "url": "https://x402.tickerlayer.com/v1/stocks/quote/{symbol}", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/crypto/snapshot/{symbol}", "priceUsd": 0.02, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/forex/agg/{symbol}/{multiplier}/{timespan}/{from}/{to}", "priceUsd": 0.03, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/bond/last/{symbol}", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/markets/status", "priceUsd": 0.01, "network": "eip155:8453" } ] }, "toolCount": 12, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-10" }, "docsUrl": "https://tickerlayer.com/docs", "llmsTxt": "https://tickerlayer.com/llms.txt", "openapi": "https://tickerlayer.com/openapi.json", "registryName": "com.tickerlayer/market-data", "capabilities": [ "market.prices", "market.history", "market.crypto", "market.indices", "market.fundamentals", "data.markets" ], "tags": [ "official", "hosted", "x402", "freemium", "free-tier", "no-card", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "websocket", "streaming", "status-page", "closed-source", "python", "typescript", "agent-skills", "pre-1.0", "new" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 71.5, "grade": "BB", "agentReady": true, "rank": 160, "ranked": true, "rankOf": 1520, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 79, "payments": 92, "reliability": 70, "schema": 88, "security": 49, "transparency": 38 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-10" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "x402 on its own gateway for 41 routes across six asset classes, bond yields and market hours, from 0.01 USDC, settled only after a valid response", "OpenAPI 3.1 with enums, examples and one error schema carrying `retryAfterMs`, `resetsAt` and the missing product, plus `Retry-After` and `X-RateLimit-*` headers", "llms.txt, llms-full.txt, a Markdown twin of every docs page and a skill that says which MCP tool to use for which question", "A dated changelog of 50 entries from 8 September to 6 November 2026", "MCP server under OAuth 2.1 with PKCE, dynamic registration, revocation and one read scope, listed in the official registry as `com.tickerlayer/market-data`" ], "weaknesses": [ "The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange", "No legal entity, address or governing law in the terms, user agreement or privacy policy", "The REST key can travel as an `apiKey` query parameter, and the WebSocket takes it only in the URL", "The privacy policy names no subprocessors and gives no period for request logs", "No security.txt, bug bounty or certification found, and the status page's history loads from a path robots.txt disallows" ], "agentNotes": [ "Write stocks as `COUNTRY:TICKER`, such as `US:KO`, and always pass `asset_class` to the data tools.", "If a 429 carries `REST_QUOTA_EXCEEDED`, stop and tell the user. Waiting doesn't reset the monthly quota.", "Present prices as indicative TickerLayer values, never as official exchange prices.", "Call `get_market_status` before you report a quiet symbol as missing data.", "Send the key in the `x-api-key` header, never as the `apiKey` query parameter." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.5 } ], "editorialScores": { "ergonomics": 79, "maintenance": 79, "payments": 92, "reliability": 70, "schema": 88, "security": 49, "transparency": 30 }, "provenanceScore": 46, "checked": { "categories": { "ergonomics": "2026-11-10", "maintenance": "2026-11-10", "payments": "2026-11-10", "reliability": "2026-11-10", "schema": "2026-11-10", "security": "2026-11-10", "transparency": "2026-11-10" }, "last": "2026-11-10", "oldest": "2026-11-10", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install tickerlayer", "http": "curl -H \"x-api-key: $TICKERLAYER_API_KEY\" \"https://api.tickerlayer.com/stocks/quote/US:KO\"", "claudeCode": "claude mcp add --transport http tickerlayer https://mcp.tickerlayer.com/mcp", "config": { "mcpServers": { "tickerlayer": { "type": "http", "url": "https://mcp.tickerlayer.com/mcp" } } }, "x402": "curl -i \"https://x402.tickerlayer.com/v1/stocks/quote/US:KO\"" }, "letme": { "capability": "https://letme.dev/market.prices", "tool": "https://letme.dev/tickerlayer" }, "area": "domain-data", "unitPrices": [ { "item": "x402 quote, last trade or previous close", "unit": "call", "usd": 0.01, "note": "USDC on Base, no account, with snapshot and symbol lists at 0.02" }, { "item": "x402 historical bars, up to 100", "unit": "call", "usd": 0.03, "note": "0.05 for up to 500 bars and 0.10 for up to 1,000" }, { "item": "Individual crypto, commodities or indices feed", "unit": "month", "usd": 49, "note": "250,000 REST calls a month, 10 requests a second, internal use only" }, { "item": "Individual US stocks feed", "unit": "month", "usd": 99, "note": "other stock markets 59 to 99 USD each, internal use only" }, { "item": "Business crypto, commodities or indices feed", "unit": "month", "usd": 449, "note": "25 million REST calls a month, 100 requests a second, use inside the customer's own product" } ], "provenance": { "legalEntity": "", "domain": "tickerlayer.com", "domainRegistered": "2026-04-29", "domainNote": "RDAP (Verisign) gives tickerlayer.com a registration date of 29 April 2026 through Cloudflare, last changed 5 October 2026. No page read names a company, registration number, address or country.", "endpointOnVendorDomain": true, "terms": "https://tickerlayer.com/terms-of-use", "privacy": "https://tickerlayer.com/privacy-policy", "statusPage": "https://status.tickerlayer.com", "changelog": "https://tickerlayer.com/docs/changelog", "securityTxt": "none", "checked": "2026-11-10", "notes": [ "No legal entity is named anywhere read. The terms of use, the user agreement and the privacy policy (all effective 3 November 2026), the about page and the pricing footer name only 'TickerLayer' or 'the operator of TickerLayer', with no company, registration number, address, country or governing law. Their contact addresses are obfuscated and weren't read. The plugin README gives info@tickerlayer.com.", "The terms say the Services come 'AS IS', promise no uptime, cap liability at the greater of 12 months' fees or US$100, and allow MCP tools to change 'with reasonable notice where practical'. The user agreement makes payments non-refundable, refunds at TickerLayer's discretion. The terms ban scraping public pages at a volume that interferes with the Services. A handful of pages were read at a person's pace.", "The privacy policy keeps WebSocket connection records for 7 days and request and tool-call logs for 'a limited operational window', names subprocessor categories but no vendors, and says nothing on model training or transfer mechanisms.", "robots.txt on tickerlayer.com disallows ia_archiver and archive.org_bot entirely and, for `*`, /dashboard, /admin, /login, /signup, /auth, /oauth, /api, /billing, /profile, the market pages and /cdn-cgi/, with no Content-Signal. x402.tickerlayer.com disallows /v1/ and status.tickerlayer.com disallows /api/. robots.txt on mcp.tickerlayer.com and api.tickerlayer.com answered a client error, read as no rules. Only their OAuth metadata and one unauthenticated GET to /mcp (client error) were sent there.", "/.well-known/security.txt answered a client error.", "firstReleased is 2026-08-07, the first commit of tickerlayer/agent-plugin ('Release v0.1.0'), whose changelog names the hosted MCP server. The about page says the API opened in 'Early 2026' with no day. lastRelease is 2026-11-06, the newest changelog entry." ], "score": 46 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tickerlayer.json", "live": { "slug": "tickerlayer", "probe": { "target": "https://mcp.tickerlayer.com/mcp", "method": "get", "lastAt": "2026-11-11T07:00:06.406304915Z", "lastOk": true, "lastStatus": 405, "lastMs": 160, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 222, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-11", "probes": 43, "ok": 43 } ], "since": "2026-11-11T02:53:34.214194678Z" }, "vendorStatus": { "page": "https://status.tickerlayer.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-11T05:35:55.448183455Z" }, "versions": [ { "registry": "npm", "name": "tickerlayer", "version": "0.1.0", "seenAt": "2026-11-11T06:42:09.859295043Z" }, { "registry": "pypi", "name": "tickerlayer", "version": "0.1.0", "released": "2026-10-20", "seenAt": "2026-11-11T06:42:10.714909327Z" } ], "githubStars": 0, "npmWeekly": 6, "pypiWeekly": 5, "updatedAt": "2026-11-11T07:00:06.406304915Z" }, "streak": { "days": 0, "from": "2026-11-11", "sinceWatching": true, "best": 0 } }, "edges": [ { "by": 70, "category": "payments", "leads": "tickerlayer", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Plans are public ($199, $1,750 and $4,500 a month) and historical data is metered per GB, but the per-dataset rates are in the portal catalogue behind a login and the pricing page's estimator shows only an example (12 of 20). $125 of credits for every new user, expiring after six months; whether a card is needed at signup was not found on the pricing, credits or billing pages (10 of 20). A person signs up in a browser and creates keys in the portal; no key API (0). Total 22.", "b": "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." }, "scores": { "a": 22, "b": 92 } }, { "by": 20, "category": "reliability", "leads": "tickerlayer", "name": "Reliability", "reasons": { "a": "Graded as a hosted service. Atlassian Statuspage at status.databento.com with ten components, Portal, Historical, FTP and seven live feeds (20). The incident feed for the 90 days to 3 November 2026 lists a critical outage of the portal and Historical API on 6 August lasting about eight hours, critical live authentication timeouts in NY4 on 28 August for about seven hours, major batch job delays of about two days each opened on 6 and 12 October, a six-hour GLBX.MDP3 delay in the Historical API on 6 October, and a Frankfurt outage affecting XEUR and XEEE opened on 2 November and still in monitoring. Several majors (0 of 30). Per-IP limits are published with numbers (15). 429 with a Retry-After header and a code to sleep on it; streams cut off aren't billed for unsent data, batch jobs are billed once (15). No SLA found; the pricing page names none and the terms were unreadable (0). The HTTP API is at major version 0 and the docs say it is not considered stable (0 of 10). Total 50.", "b": "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." }, "scores": { "a": 50, "b": 70 } }, { "by": 13, "category": "schema", "leads": "tickerlayer", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI document was found. The contract is the per-endpoint reference with typed parameters, the DBN schemas with field tables and enums, and a .http.md variant of every page (8 of 25). llms.txt and a Markdown twin of every page with language variants (10). Endpoint pages say what each call returns and the basics pages say when to use streaming against batch (15 of 20). Typed parameters with enums for schema, encoding, symbology type and split duration (13 of 15). Code in Python, C++, Rust and curl on every page, and an error table with codes, named error identifiers and a docs link in each body (14 of 15). Semantic versioning with dated release notes per component, breaking changes and deprecations called out (15). Total 75.", "b": "OpenAPI 3.1 at tickerlayer.com/openapi.json (TickerLayer Market Data API 1.0.0, about 386,000 characters), read in its first 100,000 and last 96,000 characters, with summaries, descriptions, tags and examples on the operations read and shared 400, 401, 403, 404, 429 and 503 responses. The WebSocket is described in prose only and the hosted MCP tool schemas weren't read (23 of 25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation descriptions state purpose and plan gating, and the vendor's skill says which MCP tool to use for each question and when not to, such as `get_quote` not being the tool for a price. Financial-datasets took 17 (17 of 20). Enums on `interval`, `multiplier`, `timespan` and `sort`, `format: date` on dates, bounded `limit`, required path parameters, as for massive (13 of 15). Examples on most parameters and responses, one Error schema with ten fields and documented codes, but the codes appear only as example values with no enum or table (13 of 15). A dated changelog of the last 50 changes, 8 September to 6 November 2026, but no version in the REST paths ('no /v1/') and the spec at 1.0.0. Above twelve-data's 10 for monthly updates and below massive's 15 for versioned paths (12 of 15). 23+10+17+13+13+12 = 88." }, "scores": { "a": 75, "b": 88 } }, { "by": 12, "category": "security", "leads": "databento", "name": "Security \u0026 auth", "reasons": { "a": "Named API keys, up to 100 per account, rotated or deleted in the portal, with per-member permissions, sent only as the Basic auth username; no scopes per key and no expiry (25 of 30). Every API call is a read, and a monthly historical limit caps what a leaked key can spend; live usage is not capped (14 of 20). The API returns market data and reference records, not free text from third parties (10). A data usage page in the portal and a billing page per cycle, with no per-key call log documented (8 of 15). The vendor revokes keys it finds in public and documents key hygiene; security.txt returns 404 and no bounty, SOC 2 or ISO 27001 was found on readable pages (4 of 20). Total 61.", "b": "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." }, "scores": { "a": 61, "b": 49 } }, { "by": 11, "category": "transparency", "leads": "databento", "name": "Transparency \u0026 trust", "reasons": { "a": "A closed service whose terms could not be read, because databento.com/legal and its /terms and /privacy pages are drawn by script; the client libraries are Apache-2.0 (10 of 30). The privacy policy was unread for the same reason, and the docs say nothing about retention of account data (0 of 30, unchecked). Dated release notes carry deprecations, and the versioning policy keeps a prior major version for a year after the next (18 of 20). No subprocessor list or data location statement was found on readable pages; the architecture docs name the company's own data centres (0 of 20). Total 28.", "b": "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." }, "scores": { "a": 49, "b": 38 } }, { "by": 5, "category": "maintenance", "leads": "databento", "name": "Maintenance \u0026 community", "reasons": { "a": "Python 0.89.0 on 28 October 2026 and data release notes dated 20 October (30). Python 0.85.0 (25 August), 0.86.0 (1 September), 0.87.0 (22 September), 0.88.0 (21 October) and 0.89.0, plus Rust 0.64.0 and C++ 0.69.0 on 27 October and four dated data notes since 8 August (20). A Slack community, Intercom chat, support@databento.com, a public roadmap and a public issue tracker linked from the release notes; GitHub issue replies were not read because the GitHub API rate limit was reached (12 of 15). Official clients in Python, C++ and Rust released the same week as each other (15). The Python client is Apache-2.0 with releases on GitHub and PyPI; CI and dependency pins were not checked (7 of 10). Total 84.", "b": "Read as a closed service. The newest changelog entry is 6 November 2026, a bond yield curve endpoint (30). 50 dated changelog entries from 8 September to 6 November 2026 (20). A public changelog, a consultation form, info@tickerlayer.com and a support chat, all untested, with no community channel and no issues on the plugin repository read. Massive and twelve-data took 10 (9 of 15). Official clients for JavaScript or TypeScript (npm) and Python (PyPI), both 0.1.0 from 20 October 2026, and an MCP registry entry under the verified namespace `com.tickerlayer` (15). The npm package has no dependencies or install hooks but no repository field, the clients' source isn't public and no CI is visible (5 of 10). 30+20+9+15+5 = 79." }, "scores": { "a": 84, "b": 79 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Databento, Inc.", "b": "TickerLayer", "name": "Vendor" }, { "a": "https://hist.databento.com", "b": "https://mcp.tickerlayer.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, websocket", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "yes, from $0.01/call", "name": "x402" }, { "a": "Apache-2.0 (clients)", "b": "Proprietary 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", "name": "Licence" }, { "a": "none", "b": "12", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.tickerlayer/market-data", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-11-06", "name": "Last release" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not read yet", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "309 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "TickerLayer scores 71.5 (BB) on agent readiness against Databento's 60.3 (C), and leads in 3 of 7 scored categories. Databento leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Databento or TickerLayer?" }, { "answer": "Databento needs an API key. TickerLayer takes an API key or an OAuth sign-in. An agent can also pay TickerLayer per call over x402, with no account.", "question": "Do Databento and TickerLayer need an API key?" }, { "answer": "Yes. Databento has a hosted endpoint at https://hist.databento.com and TickerLayer at https://mcp.tickerlayer.com/mcp.", "question": "Can an agent call Databento and TickerLayer without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 61 against 49", "Maintenance \u0026 community, 84 against 79", "Transparency \u0026 trust, 49 against 38" ], "also": null, "goodFor": "An agent that needs exchange-level trades, quotes, order book and bar data for US and European futures, options and equities, or corporate actions and a security master, and can budget per GB.", "slug": "databento", "watchFor": "Two critical and several major incidents on the status page in the 90 days to 3 November 2026, mostly Historical API outages and batch job delays" }, { "aheadOn": [ "Reliability, 70 against 50", "Schema \u0026 documentation, 88 against 75", "Payments \u0026 pricing, 92 against 22" ], "also": [ "Agent-ready, a grade of BB or better", "An agent can pay per call over x402, with no account", "Free to start without a card" ], "goodFor": "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.", "slug": "tickerlayer", "watchFor": "The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange" } ], "history": null, "job": { "capability": "market.prices", "name": "Market prices" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-databento.json", "title": "Alpha Vantage vs Databento", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-databento" }, { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer.json", "title": "Alpha Vantage vs TickerLayer", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-databento.json", "title": "Benzinga vs Databento", "url": "https://www.anchorterminal.com/compare/benzinga-vs-databento" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.json", "title": "Benzinga vs TickerLayer", "url": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-eodhd.json", "title": "Databento vs EODHD", "url": "https://www.anchorterminal.com/compare/databento-vs-eodhd" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-eulerpool.json", "title": "Databento vs Eulerpool Financial Data API", "url": "https://www.anchorterminal.com/compare/databento-vs-eulerpool" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-financial-datasets.json", "title": "Databento vs Financial Datasets", "url": "https://www.anchorterminal.com/compare/databento-vs-financial-datasets" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-financial-modeling-prep.json", "title": "Databento vs Financial Modeling Prep", "url": "https://www.anchorterminal.com/compare/databento-vs-financial-modeling-prep" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-finnhub.json", "title": "Databento vs Finnhub", "url": "https://www.anchorterminal.com/compare/databento-vs-finnhub" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-intrinio.json", "title": "Databento vs Intrinio", "url": "https://www.anchorterminal.com/compare/databento-vs-intrinio" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-massive.json", "title": "Databento vs Massive (formerly Polygon.io)", "url": "https://www.anchorterminal.com/compare/databento-vs-massive" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-tiingo.json", "title": "Databento vs Tiingo", "url": "https://www.anchorterminal.com/compare/databento-vs-tiingo" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-twelve-data.json", "title": "Databento vs Twelve Data", "url": "https://www.anchorterminal.com/compare/databento-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer.json", "title": "Finnhub vs TickerLayer", "url": "https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer.json", "title": "Intrinio vs TickerLayer", "url": "https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/massive-vs-tickerlayer.json", "title": "Massive (formerly Polygon.io) vs TickerLayer", "url": "https://www.anchorterminal.com/compare/massive-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo.json", "title": "TickerLayer vs Tiingo", "url": "https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo" }, { "json": "https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data.json", "title": "TickerLayer vs Twelve Data", "url": "https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer.json", "title": "Eulerpool Financial Data API vs TickerLayer", "url": "https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer.json", "title": "Financial Datasets vs TickerLayer", "url": "https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer.json", "title": "Financial Modeling Prep vs TickerLayer", "url": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer.json", "title": "EODHD vs TickerLayer", "url": "https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer" } ], "panel": null, "scores": [ { "by": 20, "databento": 50, "edge": "tickerlayer", "key": "reliability", "name": "Reliability", "tickerlayer": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "databento": 75, "edge": "tickerlayer", "key": "schema", "name": "Schema \u0026 documentation", "tickerlayer": 88, "weight": 13 }, { "by": 1, "databento": 80, "edge": "databento", "key": "ergonomics", "name": "Agent ergonomics", "tickerlayer": 79, "weight": 13 }, { "by": 12, "databento": 61, "edge": "databento", "key": "security", "name": "Security \u0026 auth", "tickerlayer": 49, "weight": 14 }, { "by": 70, "databento": 22, "edge": "tickerlayer", "key": "payments", "name": "Payments \u0026 pricing", "tickerlayer": 92, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "databento": 84, "edge": "databento", "key": "maintenance", "name": "Maintenance \u0026 community", "tickerlayer": 79, "weight": 7 }, { "by": 11, "databento": 49, "edge": "databento", "key": "transparency", "name": "Transparency \u0026 trust", "tickerlayer": 38, "weight": 7 } ], "summary": "TickerLayer scores 71.5 (BB) on agent readiness against Databento's 60.3 (C), and leads in 3 of 7 scored categories. Databento leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do market prices. TickerLayer accepts x402. Databento doesn't.", "tasks": null, "tutorials": [], "verdicts": { "databento": "Exchange-level tick and order book data metered per GB, with published per-IP rate limits, Retry-After on 429, dated release notes and clients in three languages. The HTTP API is still at major version 0, the status page lists two critical and several major incidents in 90 days, there is no OpenAPI document, and the legal pages were unreadable.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer", "json": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer.min.md" }, "markdown": "TickerLayer scores 71.5 (BB) on agent readiness against Databento's 60.3 (C), and leads in 3 of 7 scored categories. Databento leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do market prices. TickerLayer accepts x402. Databento doesn't.\n\n- Databento: grade C, 60.3/100, rank #663 of 1520. Markdown https://www.anchorterminal.com/tools/databento.md · JSON https://www.anchorterminal.com/api/v1/tools/databento.json\n- TickerLayer: grade BB, 71.5/100, rank #160 of 1520. Markdown https://www.anchorterminal.com/tools/tickerlayer.md · JSON https://www.anchorterminal.com/api/v1/tools/tickerlayer.json\n- Best financial market data APIs for AI agents: https://www.anchorterminal.com/best/market-data/index.md\n- All 78 markets comparisons: https://www.anchorterminal.com/compare/market-data/index.md\n\n## Which one, for what\n\n### Databento (C)\n\nGood for: An agent that needs exchange-level trades, quotes, order book and bar data for US and European futures, options and equities, or corporate actions and a security master, and can budget per GB.\n\nAhead on:\n- Security \u0026 auth, 61 against 49\n- Maintenance \u0026 community, 84 against 79\n- Transparency \u0026 trust, 49 against 38\n\nWatch for: Two critical and several major incidents on the status page in the 90 days to 3 November 2026, mostly Historical API outages and batch job delays\n\n### TickerLayer (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 70 against 50\n- Schema \u0026 documentation, 88 against 75\n- Payments \u0026 pricing, 92 against 22\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- An agent can pay per call over x402, with no account\n- Free to start without a card\n\nWatch for: The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange\n\n\n## Why the edge\n\n### Payments \u0026 pricing: TickerLayer +70\n\n- Databento (22): No x402, MPP or L402 (0). Plans are public ($199, $1,750 and $4,500 a month) and historical data is metered per GB, but the per-dataset rates are in the portal catalogue behind a login and the pricing page's estimator shows only an example (12 of 20). $125 of credits for every new user, expiring after six months; whether a card is needed at signup was not found on the pricing, credits or billing pages (10 of 20). A person signs up in a browser and creates keys in the portal; no key API (0). Total 22.\n- TickerLayer (92): 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.\n\n### Reliability: TickerLayer +20\n\n- Databento (50): Graded as a hosted service. Atlassian Statuspage at status.databento.com with ten components, Portal, Historical, FTP and seven live feeds (20). The incident feed for the 90 days to 3 November 2026 lists a critical outage of the portal and Historical API on 6 August lasting about eight hours, critical live authentication timeouts in NY4 on 28 August for about seven hours, major batch job delays of about two days each opened on 6 and 12 October, a six-hour GLBX.MDP3 delay in the Historical API on 6 October, and a Frankfurt outage affecting XEUR and XEEE opened on 2 November and still in monitoring. Several majors (0 of 30). Per-IP limits are published with numbers (15). 429 with a Retry-After header and a code to sleep on it; streams cut off aren't billed for unsent data, batch jobs are billed once (15). No SLA found; the pricing page names none and the terms were unreadable (0). The HTTP API is at major version 0 and the docs say it is not considered stable (0 of 10). Total 50.\n- 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.\n\n### Schema \u0026 documentation: TickerLayer +13\n\n- Databento (75): No OpenAPI document was found. The contract is the per-endpoint reference with typed parameters, the DBN schemas with field tables and enums, and a .http.md variant of every page (8 of 25). llms.txt and a Markdown twin of every page with language variants (10). Endpoint pages say what each call returns and the basics pages say when to use streaming against batch (15 of 20). Typed parameters with enums for schema, encoding, symbology type and split duration (13 of 15). Code in Python, C++, Rust and curl on every page, and an error table with codes, named error identifiers and a docs link in each body (14 of 15). Semantic versioning with dated release notes per component, breaking changes and deprecations called out (15). Total 75.\n- TickerLayer (88): OpenAPI 3.1 at tickerlayer.com/openapi.json (TickerLayer Market Data API 1.0.0, about 386,000 characters), read in its first 100,000 and last 96,000 characters, with summaries, descriptions, tags and examples on the operations read and shared 400, 401, 403, 404, 429 and 503 responses. The WebSocket is described in prose only and the hosted MCP tool schemas weren't read (23 of 25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation descriptions state purpose and plan gating, and the vendor's skill says which MCP tool to use for each question and when not to, such as `get_quote` not being the tool for a price. Financial-datasets took 17 (17 of 20). Enums on `interval`, `multiplier`, `timespan` and `sort`, `format: date` on dates, bounded `limit`, required path parameters, as for massive (13 of 15). Examples on most parameters and responses, one Error schema with ten fields and documented codes, but the codes appear only as example values with no enum or table (13 of 15). A dated changelog of the last 50 changes, 8 September to 6 November 2026, but no version in the REST paths ('no /v1/') and the spec at 1.0.0. Above twelve-data's 10 for monthly updates and below massive's 15 for versioned paths (12 of 15). 23+10+17+13+13+12 = 88.\n\n### Security \u0026 auth: Databento +12\n\n- Databento (61): Named API keys, up to 100 per account, rotated or deleted in the portal, with per-member permissions, sent only as the Basic auth username; no scopes per key and no expiry (25 of 30). Every API call is a read, and a monthly historical limit caps what a leaked key can spend; live usage is not capped (14 of 20). The API returns market data and reference records, not free text from third parties (10). A data usage page in the portal and a billing page per cycle, with no per-key call log documented (8 of 15). The vendor revokes keys it finds in public and documents key hygiene; security.txt returns 404 and no bounty, SOC 2 or ISO 27001 was found on readable pages (4 of 20). Total 61.\n- 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.\n\n### Transparency \u0026 trust: Databento +11\n\n- Databento (49): A closed service whose terms could not be read, because databento.com/legal and its /terms and /privacy pages are drawn by script; the client libraries are Apache-2.0 (10 of 30). The privacy policy was unread for the same reason, and the docs say nothing about retention of account data (0 of 30, unchecked). Dated release notes carry deprecations, and the versioning policy keeps a prior major version for a year after the next (18 of 20). No subprocessor list or data location statement was found on readable pages; the architecture docs name the company's own data centres (0 of 20). Total 28.\n- 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.\n\n### Maintenance \u0026 community: Databento +5\n\n- Databento (84): Python 0.89.0 on 28 October 2026 and data release notes dated 20 October (30). Python 0.85.0 (25 August), 0.86.0 (1 September), 0.87.0 (22 September), 0.88.0 (21 October) and 0.89.0, plus Rust 0.64.0 and C++ 0.69.0 on 27 October and four dated data notes since 8 August (20). A Slack community, Intercom chat, support@databento.com, a public roadmap and a public issue tracker linked from the release notes; GitHub issue replies were not read because the GitHub API rate limit was reached (12 of 15). Official clients in Python, C++ and Rust released the same week as each other (15). The Python client is Apache-2.0 with releases on GitHub and PyPI; CI and dependency pins were not checked (7 of 10). Total 84.\n- TickerLayer (79): Read as a closed service. The newest changelog entry is 6 November 2026, a bond yield curve endpoint (30). 50 dated changelog entries from 8 September to 6 November 2026 (20). A public changelog, a consultation form, info@tickerlayer.com and a support chat, all untested, with no community channel and no issues on the plugin repository read. Massive and twelve-data took 10 (9 of 15). Official clients for JavaScript or TypeScript (npm) and Python (PyPI), both 0.1.0 from 20 October 2026, and an MCP registry entry under the verified namespace `com.tickerlayer` (15). The npm package has no dependencies or install hooks but no repository field, the clients' source isn't public and no CI is visible (5 of 10). 30+20+9+15+5 = 79.\n\n## Score by category\n\n| Category | Weight | Databento | TickerLayer | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 70 | TickerLayer +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 88 | TickerLayer +13 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 79 | Databento +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 49 | Databento +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 22 | 92 | TickerLayer +70 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 79 | Databento +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 38 | Databento +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **71.5 · BB** | |\n\n## Facts side by side\n\n| Fact | Databento | TickerLayer |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Databento, Inc. | TickerLayer |\n| Hosted endpoint | `https://hist.databento.com` | `https://mcp.tickerlayer.com/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP, websocket |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | yes, from $0.01/call |\n| Licence | Apache-2.0 (clients) | Proprietary 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 |\n| Tools exposed | none | 12 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.tickerlayer/market-data` |\n| Last release | 2026-10-28 | 2026-11-06 |\n| Terms last updated | couldn't be read | not read yet |\n| Privacy policy last updated | couldn't be read | not read yet |\n| Customer content may train models | couldn't be read | not read yet |\n| Terms restrict automated access | couldn't be read | not read yet |\n| Terms restrict benchmarking | couldn't be read | not read yet |\n| Terms or service can change without notice | couldn't be read | not read yet |\n| Arbitration or class-action waiver | couldn't be read | not read yet |\n| Popularity | 309 stars | none |\n\n## Verdicts\n\n**Databento.** Exchange-level tick and order book data metered per GB, with published per-IP rate limits, Retry-After on 429, dated release notes and clients in three languages. The HTTP API is still at major version 0, the status page lists two critical and several major incidents in 90 days, there is no OpenAPI document, and the legal pages were unreadable.\n\n**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.\n\n## Before you call either\n\n### Databento\n\n1. Call `metadata.get_cost` before `timeseries.get_range`, and set a monthly historical limit in the portal; a duplicate streaming request is charged twice\n2. Send the key as the Basic auth username (`-u $DATABENTO_API_KEY:`) to hist.databento.com/v0; never put it in the URL or source code\n3. On 429 wait for the Retry-After header; keep under 100 time series requests a second and 20 batch submissions a minute per IP\n4. Check status.databento.com before retrying a slow or 504 Historical request, since several incidents since August were API outages or batch delays\n5. Use batch download for requests over 5 GB, split by time range or `limit`, and read `schema` and `stype_in` from the dataset page before querying\n\n### TickerLayer\n\n1. Write stocks as `COUNTRY:TICKER`, such as `US:KO`, and always pass `asset_class` to the data tools.\n2. If a 429 carries `REST_QUOTA_EXCEEDED`, stop and tell the user. Waiting doesn't reset the monthly quota.\n3. Present prices as indicative TickerLayer values, never as official exchange prices.\n4. Call `get_market_status` before you report a quiet symbol as missing data.\n5. Send the key in the `x-api-key` header, never as the `apiKey` query parameter.\n\n## Questions\n\n### Which is better for AI agents, Databento or TickerLayer?\n\nTickerLayer scores 71.5 (BB) on agent readiness against Databento's 60.3 (C), and leads in 3 of 7 scored categories. Databento leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Databento and TickerLayer need an API key?\n\nDatabento needs an API key. TickerLayer takes an API key or an OAuth sign-in. An agent can also pay TickerLayer per call over x402, with no account.\n\n### Can an agent call Databento and TickerLayer without installing anything?\n\nYes. Databento has a hosted endpoint at https://hist.databento.com and TickerLayer at https://mcp.tickerlayer.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/databento-vs-tickerlayer.json, and with the fewest tokens: https://www.anchorterminal.com/compare/databento-vs-tickerlayer.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"databento\", \"b\": \"tickerlayer\"}`. From a terminal: `anchor compare databento tickerlayer`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/databento.json and https://www.anchorterminal.com/api/v1/tools/tickerlayer.json\n\n## Other comparisons with Databento or TickerLayer\n\n- [Alpha Vantage vs Databento](https://www.anchorterminal.com/compare/alpha-vantage-vs-databento.md)\n- [Alpha Vantage vs TickerLayer](https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer.md)\n- [Benzinga vs Databento](https://www.anchorterminal.com/compare/benzinga-vs-databento.md)\n- [Benzinga vs TickerLayer](https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.md)\n- [Databento vs EODHD](https://www.anchorterminal.com/compare/databento-vs-eodhd.md)\n- [Databento vs Eulerpool Financial Data API](https://www.anchorterminal.com/compare/databento-vs-eulerpool.md)\n- [Databento vs Financial Datasets](https://www.anchorterminal.com/compare/databento-vs-financial-datasets.md)\n- [Databento vs Financial Modeling Prep](https://www.anchorterminal.com/compare/databento-vs-financial-modeling-prep.md)\n- [Databento vs Finnhub](https://www.anchorterminal.com/compare/databento-vs-finnhub.md)\n- [Databento vs Intrinio](https://www.anchorterminal.com/compare/databento-vs-intrinio.md)\n- [Databento vs Massive (formerly Polygon.io)](https://www.anchorterminal.com/compare/databento-vs-massive.md)\n- [Databento vs Tiingo](https://www.anchorterminal.com/compare/databento-vs-tiingo.md)\n- [Databento vs Twelve Data](https://www.anchorterminal.com/compare/databento-vs-twelve-data.md)\n- [Finnhub vs TickerLayer](https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer.md)\n- [Intrinio vs TickerLayer](https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer.md)\n- [Massive (formerly Polygon.io) vs TickerLayer](https://www.anchorterminal.com/compare/massive-vs-tickerlayer.md)\n- [TickerLayer vs Tiingo](https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo.md)\n- [TickerLayer vs Twelve Data](https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data.md)\n- [Eulerpool Financial Data API vs TickerLayer](https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer.md)\n- [Financial Datasets vs TickerLayer](https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer.md)\n- [Financial Modeling Prep vs TickerLayer](https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer.md)\n- [EODHD vs TickerLayer](https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-11", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Databento vs TickerLayer", "url": "" } ], "description": "TickerLayer scores 71.5 (BB) to Databento's 60.3 (C) for market prices. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Databento C 60.3", "TickerLayer BB 71.5", "scores" ], "h1": "Databento vs TickerLayer", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/databento-vs-tickerlayer", "published": "2026-10-01", "section": "tools", "title": "Databento vs TickerLayer for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-11", "url": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer" }, "tokens": { "markdown": 5400, "slim": 1230 }, "version": 1 }