{ "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": 578, "ranked": true, "rankOf": 1349, "categoryRank": 4, "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-04T19:34:31.331915623Z", "lastOk": true, "lastStatus": 200, "lastMs": 1514, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 344, "p95ms24h": 1514, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-04", "probes": 43, "ok": 43 } ] }, "vendorStatus": { "page": "https://status.databento.com", "indicator": "minor", "summary": "Minor Service Outage", "checkedAt": "2026-11-04T19:31:26.086234819Z" }, "securityTxt": { "url": "https://databento.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:13.184390241Z" }, "updatedAt": "2026-11-04T19:34:31.331915623Z" } }, "answer": "Twelve Data scores 70 (BB) on agent readiness against Databento's 60.3 (C), and leads in 5 of 7 scored categories. Databento leads on security \u0026 auth.", "b": { "slug": "twelve-data", "name": "Twelve Data", "vendor": "Twelve Data Pte. Ltd.", "vendorUrl": "https://twelvedata.com", "kind": "http-api", "category": "market-data", "summary": "Twelve Data is a market data API for prices and time series across stocks, ETFs, funds, forex, crypto and commodities, with technical indicators, fundamentals, news and filings. Agents call the REST API, the WebSocket or the hosted MCP server.", "url": "https://www.anchorterminal.com/tools/twelve-data", "markdownUrl": "https://www.anchorterminal.com/tools/twelve-data.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/twelve-data.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/twelve-data.json", "dns": "twelve-data.grade.anchorterminal.com", "repo": "https://github.com/twelvedata/mcp", "transports": [ "http", "streamable-http", "stdio", "websocket" ], "remoteUrl": "https://api.twelvedata.com", "packages": [ { "registry": "pypi", "name": "twelvedata" }, { "registry": "npm", "name": "twelvedata" } ], "auth": "mixed", "authNotes": "REST and WebSocket take an API key from the dashboard, sent as an `Authorization: apikey \u003ckey\u003e` header (the docs call it recommended) or as `?apikey=`. The hosted MCP server does not accept keys; it uses OAuth 2.1 at auth.twelvedata.com with authorisation code and PKCE, refresh tokens, Client ID Metadata Documents or dynamic client registration, one scope `twelvedata`, a required `resource` parameter and a revocation endpoint. The user signs in with a Twelve Data account. No key scopes or expiry found.", "pricing": "freemium", "pricingNotes": "Basic plan free at 8 API credits a minute and 800 a day with real-time US equities, forex and crypto, no card. Individual plans Grow from $29, Pro from $99 and Ultra from $329 a month (55, 610 and 2,584 credits a minute at the lowest tier, up to $999 for 10,946), annual billing 17 per cent less. Business plans Venture from $149 and Enterprise $1,099 a month, Enterprise+ by quote. Most endpoints cost one credit per symbol; fundamentals and analysis cost more (https://twelvedata.com/pricing.md, checked 2026-11-03).", "priceSummary": "$29 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI document, llms.txt, pricing.md, auth.md or the MCP docs (checked 2026-11-03). A call without a key returns HTTP 401 with a JSON `code`, `message` and `status`.", "endpoints": [] }, "toolCount": 27, "popularity": { "githubStars": 791, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://twelvedata.com/docs", "llmsTxt": "https://twelvedata.com/llms.txt", "openapi": "https://api.twelvedata.com/doc/swagger/openapi.json", "capabilities": [ "market.prices", "market.history", "market.fundamentals", "market.crypto", "market.indices", "market.news", "market.filings", "data.markets" ], "tags": [ "hosted", "freemium", "api-key", "oauth", "mcp", "remote-mcp", "openapi", "llms-txt", "status-page", "soc2", "sla", "no-card", "free-tier", "closed-source", "python", "typescript", "go", "java", "stocks", "forex", "crypto", "streaming", "personal-use" ], "lastRelease": "2026-10-12", "graded": true, "anchor": { "graded": true, "score": 70, "grade": "BB", "agentReady": true, "rank": 197, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 82, "payments": 30, "reliability": 83, "schema": 83, "security": 54, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "Agents that need prices and time series across many exchanges and asset classes with one contract, CSV output, and a documented error table.", "strengths": [ "OpenAPI 3.1 for 187 operations with eight documented response codes each, plus llms.txt, pricing.md and auth.md for agents", "Status page with component history, two incidents of 20 and 16 minutes in the 90 days to 3 November 2026", "Hosted MCP server on OAuth 2.1 with PKCE, resource indicators and token revocation, and 27 read-only tools in the open source", "Official SDKs for Python, Node.js, Go, Java and R, a CLI, and monthly dated product updates", "Free Basic plan at 800 credits a day with no card, and plan prices published without login" ], "weaknesses": [ "The REST docs and OpenAPI accept the key as `?apikey=` in the query string alongside the header", "No parameter in the OpenAPI document declares an enum; interval and type values are listed in Markdown only", "Free and individual plans are for internal, non-commercial use; any company, team or fund needs a business plan from $149 a month", "No Retry-After or backoff guidance on the documented 429", "The open-source MCP repository ships no licence file, and its local HTTP mode serves /mcp with no authentication by default" ], "agentNotes": [ "Send the key as `Authorization: apikey \u003ckey\u003e`, not in the URL; the hosted MCP server takes OAuth only, so never paste a key into a connector's key field", "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`", "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", "A 403 means the key's plan lacks the endpoint or symbol, not a bad key; check pricing.md before escalating", "Use trial symbols from twelvedata.com/exchanges to test premium data on the free plan" ], "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": 70 } ], "editorialScores": { "ergonomics": 84, "maintenance": 82, "payments": 30, "reliability": 83, "schema": 83, "security": 54, "transparency": 50 }, "provenanceScore": 83, "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 twelvedata", "http": "curl -H \"Authorization: apikey $TWELVE_DATA_API_KEY\" \"https://api.twelvedata.com/time_series?symbol=AAPL\u0026interval=1day\u0026outputsize=30\"", "config": { "mcpServers": { "twelvedata": { "url": "https://mcp.twelvedata.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/market.prices", "tool": "https://letme.dev/twelve-data" }, "area": "domain-data", "unitPrices": [ { "item": "Grow, 55 credits a minute", "unit": "month", "usd": 29, "note": "individual, internal use, lowest Grow tier" }, { "item": "Pro, 610 credits a minute", "unit": "month", "usd": 99, "note": "individual, lowest Pro tier" }, { "item": "Ultra, 2,584 credits a minute", "unit": "month", "usd": 329, "note": "individual, lowest Ultra tier" }, { "item": "Venture, 610 credits a minute", "unit": "month", "usd": 149, "note": "business, external display" }, { "item": "Enterprise, 10,946 credits a minute", "unit": "month", "usd": 1099, "note": "business, external distribution, 99.99 per cent SLA" } ], "provenance": { "legalEntity": "Twelve Data Pte. Ltd.", "domain": "twelvedata.com", "domainRegistered": "2019-07-11", "endpointOnVendorDomain": true, "terms": "https://twelvedata.com/terms", "privacy": "https://twelvedata.com/privacy", "statusPage": "https://twelvedata.isitup.cloud", "changelog": "https://twelvedata.com/news", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms, last updated 1 January 2026, name Twelve Data Pte. Ltd. (UEN 202006058W) under Singapore law with SIAC arbitration. Section 2.3(h) forbids automated tools used to exceed rate limits; nothing forbids reading the website.", "The privacy policy, last updated 22 September 2026, gives the Singapore address, retention of 2 years for account data, 7 years for financial records and 1 year for usage data, and names Azure, Stripe, PayPal, Cloudflare, Intercom, Segment, CookieYes, Google Analytics and Microsoft Clarity.", "twelvedata.com/robots.txt disallows /api/, /docs/search, /docs/url/convert and account paths; the docs, pricing, terms and privacy pages are allowed.", "RDAP gives twelvedata.com a registration date of 11 July 2019 at GoDaddy.", "/.well-known/security.txt and /security.txt return 404. twelvedata.com/security returns 404; the trust centre is security.twelvedata.com on SafeBase.", "The status page is hosted by Isitup at twelvedata.isitup.cloud and is linked from llms.txt. The news page carries monthly product updates and is the nearest thing to a changelog." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/twelve-data.json", "live": { "slug": "twelve-data", "probe": { "target": "https://api.twelvedata.com", "method": "get", "lastAt": "2026-11-04T19:35:17.57001935Z", "lastOk": true, "lastStatus": 404, "lastMs": 150, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 145, "p95ms24h": 219, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-04", "probes": 43, "ok": 43 } ] }, "vendorStatus": { "page": "https://twelvedata.isitup.cloud", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:39.97677279Z" }, "securityTxt": { "url": "https://twelvedata.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:50.370188865Z" }, "updatedAt": "2026-11-04T19:35:17.57001935Z" } }, "edges": [ { "by": 33, "category": "reliability", "leads": "twelve-data", "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. 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." }, "scores": { "a": 50, "b": 83 } }, { "by": 18, "category": "transparency", "leads": "twelve-data", "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": "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." }, "scores": { "a": 49, "b": 67 } }, { "by": 8, "category": "schema", "leads": "twelve-data", "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": "A public OpenAPI 3.1 document covers 187 operations, every one with a description and 200, 400, 401, 403, 404, 414, 429 and 500 responses, and the MCP tools in the source carry typed inputs and annotations (25). llms.txt on the site and in the docs link Markdown pages per section, pricing.md and auth.md (10). Descriptions state purpose, plan requirement and credit cost, with little on when not to use an endpoint (16 of 20). Required parameters are marked and the Markdown lists interval, adjust and type values, but none of the 3,091 parameters in the spec declares an enum (9 of 15). Examples with a demo key on every endpoint and an error table with codes and meanings (13 of 15). No version in the path, a spec at version 0.0.1, and monthly dated product updates on the news page rather than an API changelog (10 of 15). 25 + 10 + 16 + 9 + 13 + 10 = 83." }, "scores": { "a": 75, "b": 83 } }, { "by": 8, "category": "payments", "leads": "twelve-data", "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": "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." }, "scores": { "a": 22, "b": 30 } }, { "by": 7, "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": "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." }, "scores": { "a": 61, "b": 54 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Databento, Inc.", "b": "Twelve Data Pte. Ltd.", "name": "Vendor" }, { "a": "https://hist.databento.com", "b": "https://api.twelvedata.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio, websocket", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 (clients)", "b": "none", "name": "Licence" }, { "a": "none", "b": "27", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-28", "b": "2026-10-12", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-01-01", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-09-22", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "309 stars", "b": "791 stars", "name": "Popularity" } ], "faq": [ { "answer": "Twelve Data scores 70 (BB) on agent readiness against Databento's 60.3 (C), and leads in 5 of 7 scored categories. Databento leads on security \u0026 auth.", "question": "Which is better for AI agents, Databento or Twelve Data?" }, { "answer": "Databento needs an API key. Twelve Data takes an API key or an OAuth sign-in.", "question": "Do Databento and Twelve Data need an API key?" }, { "answer": "Yes. Databento has a hosted endpoint at https://hist.databento.com and Twelve Data at https://api.twelvedata.com.", "question": "Can an agent call Databento and Twelve Data without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 61 against 54" ], "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, 83 against 50", "Schema \u0026 documentation, 83 against 75", "Payments \u0026 pricing, 30 against 22", "Transparency \u0026 trust, 67 against 49" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "Agents that need prices and time series across many exchanges and asset classes with one contract, CSV output, and a documented error table.", "slug": "twelve-data", "watchFor": "The REST docs and OpenAPI accept the key as `?apikey=` in the query string alongside the header" } ], "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-twelve-data.json", "title": "Alpha Vantage vs Twelve Data", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-twelve-data" }, { "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/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-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/finnhub-vs-twelve-data.json", "title": "Finnhub vs Twelve Data", "url": "https://www.anchorterminal.com/compare/finnhub-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/intrinio-vs-twelve-data.json", "title": "Intrinio vs Twelve Data", "url": "https://www.anchorterminal.com/compare/intrinio-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/massive-vs-twelve-data.json", "title": "Massive (formerly Polygon.io) vs Twelve Data", "url": "https://www.anchorterminal.com/compare/massive-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/tiingo-vs-twelve-data.json", "title": "Tiingo vs Twelve Data", "url": "https://www.anchorterminal.com/compare/tiingo-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/financial-datasets-vs-twelve-data.json", "title": "Financial Datasets vs Twelve Data", "url": "https://www.anchorterminal.com/compare/financial-datasets-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-twelve-data.json", "title": "Financial Modeling Prep vs Twelve Data", "url": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/eodhd-vs-twelve-data.json", "title": "EODHD vs Twelve Data", "url": "https://www.anchorterminal.com/compare/eodhd-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-twelve-data.json", "title": "Benzinga vs Twelve Data", "url": "https://www.anchorterminal.com/compare/benzinga-vs-twelve-data" } ], "panel": null, "scores": [ { "by": 33, "databento": 50, "edge": "twelve-data", "key": "reliability", "name": "Reliability", "twelve-data": 83, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "databento": 75, "edge": "twelve-data", "key": "schema", "name": "Schema \u0026 documentation", "twelve-data": 83, "weight": 13 }, { "by": 4, "databento": 80, "edge": "twelve-data", "key": "ergonomics", "name": "Agent ergonomics", "twelve-data": 84, "weight": 13 }, { "by": 7, "databento": 61, "edge": "databento", "key": "security", "name": "Security \u0026 auth", "twelve-data": 54, "weight": 14 }, { "by": 8, "databento": 22, "edge": "twelve-data", "key": "payments", "name": "Payments \u0026 pricing", "twelve-data": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "databento": 84, "edge": "databento", "key": "maintenance", "name": "Maintenance \u0026 community", "twelve-data": 82, "weight": 7 }, { "by": 18, "databento": 49, "edge": "twelve-data", "key": "transparency", "name": "Transparency \u0026 trust", "twelve-data": 67, "weight": 7 } ], "summary": "Twelve Data scores 70 (BB) on agent readiness against Databento's 60.3 (C), and leads in 5 of 7 scored categories. Databento leads on security \u0026 auth. Both do market prices.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/databento-vs-twelve-data", "json": "https://www.anchorterminal.com/compare/databento-vs-twelve-data.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/databento-vs-twelve-data.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/databento-vs-twelve-data.min.md" }, "markdown": "Twelve Data scores 70 (BB) on agent readiness against Databento's 60.3 (C), and leads in 5 of 7 scored categories. Databento leads on security \u0026 auth. Both do market prices.\n\n- Databento: grade C, 60.3/100, rank #578 of 1349. Markdown https://www.anchorterminal.com/tools/databento.md · JSON https://www.anchorterminal.com/api/v1/tools/databento.json\n- Twelve Data: grade BB, 70/100, rank #197 of 1349. Markdown https://www.anchorterminal.com/tools/twelve-data.md · JSON https://www.anchorterminal.com/api/v1/tools/twelve-data.json\n- Best financial market data APIs for AI agents: https://www.anchorterminal.com/best/market-data/index.md\n- All 55 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 54\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### Twelve Data (BB)\n\nGood for: Agents that need prices and time series across many exchanges and asset classes with one contract, CSV output, and a documented error table.\n\nAhead on:\n- Reliability, 83 against 50\n- Schema \u0026 documentation, 83 against 75\n- Payments \u0026 pricing, 30 against 22\n- Transparency \u0026 trust, 67 against 49\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: The REST docs and OpenAPI accept the key as `?apikey=` in the query string alongside the header\n\n\n## Why the edge\n\n### Reliability: Twelve Data +33\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- 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.\n\n### Transparency \u0026 trust: Twelve Data +18\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- 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.\n\n### Schema \u0026 documentation: Twelve Data +8\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- Twelve Data (83): A public OpenAPI 3.1 document covers 187 operations, every one with a description and 200, 400, 401, 403, 404, 414, 429 and 500 responses, and the MCP tools in the source carry typed inputs and annotations (25). llms.txt on the site and in the docs link Markdown pages per section, pricing.md and auth.md (10). Descriptions state purpose, plan requirement and credit cost, with little on when not to use an endpoint (16 of 20). Required parameters are marked and the Markdown lists interval, adjust and type values, but none of the 3,091 parameters in the spec declares an enum (9 of 15). Examples with a demo key on every endpoint and an error table with codes and meanings (13 of 15). No version in the path, a spec at version 0.0.1, and monthly dated product updates on the news page rather than an API changelog (10 of 15). 25 + 10 + 16 + 9 + 13 + 10 = 83.\n\n### Payments \u0026 pricing: Twelve Data +8\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- Twelve Data (30): 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.\n\n### Security \u0026 auth: Databento +7\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- 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.\n\n## Score by category\n\n| Category | Weight | Databento | Twelve Data | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 83 | Twelve Data +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 83 | Twelve Data +8 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 84 | Twelve Data +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 54 | Databento +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 22 | 30 | Twelve Data +8 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 82 | Databento +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 67 | Twelve Data +18 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **70 · BB** | |\n\n## Facts side by side\n\n| Fact | Databento | Twelve Data |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Databento, Inc. | Twelve Data Pte. Ltd. |\n| Hosted endpoint | `https://hist.databento.com` | `https://api.twelvedata.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio, websocket |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 (clients) | none |\n| Tools exposed | none | 27 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-28 | 2026-10-12 |\n| Terms last updated | couldn't be read | 2026-01-01 |\n| Privacy policy last updated | couldn't be read | 2026-09-22 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 309 stars | 791 stars |\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**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.\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### Twelve Data\n\n1. Send the key as `Authorization: apikey \u003ckey\u003e`, not in the URL; the hosted MCP server takes OAuth only, so never paste a key into a connector's key field\n2. 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`\n3. 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\n4. A 403 means the key's plan lacks the endpoint or symbol, not a bad key; check pricing.md before escalating\n5. Use trial symbols from twelvedata.com/exchanges to test premium data on the free plan\n\n## Questions\n\n### Which is better for AI agents, Databento or Twelve Data?\n\nTwelve Data scores 70 (BB) on agent readiness against Databento's 60.3 (C), and leads in 5 of 7 scored categories. Databento leads on security \u0026 auth.\n\n### Do Databento and Twelve Data need an API key?\n\nDatabento needs an API key. Twelve Data takes an API key or an OAuth sign-in.\n\n### Can an agent call Databento and Twelve Data without installing anything?\n\nYes. Databento has a hosted endpoint at https://hist.databento.com and Twelve Data at https://api.twelvedata.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/databento-vs-twelve-data.json, and with the fewest tokens: https://www.anchorterminal.com/compare/databento-vs-twelve-data.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"databento\", \"b\": \"twelve-data\"}`. From a terminal: `anchor compare databento twelve-data`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/databento.json and https://www.anchorterminal.com/api/v1/tools/twelve-data.json\n\n## Other comparisons with Databento or Twelve Data\n\n- [Alpha Vantage vs Databento](https://www.anchorterminal.com/compare/alpha-vantage-vs-databento.md)\n- [Alpha Vantage vs Twelve Data](https://www.anchorterminal.com/compare/alpha-vantage-vs-twelve-data.md)\n- [Benzinga vs Databento](https://www.anchorterminal.com/compare/benzinga-vs-databento.md)\n- [Databento vs EODHD](https://www.anchorterminal.com/compare/databento-vs-eodhd.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- [Finnhub vs Twelve Data](https://www.anchorterminal.com/compare/finnhub-vs-twelve-data.md)\n- [Intrinio vs Twelve Data](https://www.anchorterminal.com/compare/intrinio-vs-twelve-data.md)\n- [Massive (formerly Polygon.io) vs Twelve Data](https://www.anchorterminal.com/compare/massive-vs-twelve-data.md)\n- [Tiingo vs Twelve Data](https://www.anchorterminal.com/compare/tiingo-vs-twelve-data.md)\n- [Financial Datasets vs Twelve Data](https://www.anchorterminal.com/compare/financial-datasets-vs-twelve-data.md)\n- [Financial Modeling Prep vs Twelve Data](https://www.anchorterminal.com/compare/financial-modeling-prep-vs-twelve-data.md)\n- [EODHD vs Twelve Data](https://www.anchorterminal.com/compare/eodhd-vs-twelve-data.md)\n- [Benzinga vs Twelve Data](https://www.anchorterminal.com/compare/benzinga-vs-twelve-data.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-04", "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 Twelve Data", "url": "" } ], "description": "Twelve Data scores 70 (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", "Twelve Data BB 70", "scores" ], "h1": "Databento vs Twelve Data", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/databento-vs-twelve-data", "published": "2026-10-01", "section": "tools", "title": "Databento vs Twelve Data for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/databento-vs-twelve-data" }, "tokens": { "markdown": 4200, "slim": 2530 }, "version": 1 }