# Databento vs EODHD (slim)

> Databento scores 60.3 (C) to EODHD's 59 (C) for market prices. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/databento-vs-eodhd.md (~3,800 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/databento-vs-eodhd.json · canonical https://www.anchorterminal.com/compare/databento-vs-eodhd
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Databento scores 60.3 (C) on agent readiness against EODHD's 59 (C), and leads in 4 of 7 scored categories. EODHD leads on reliability and payments & pricing. Both do market prices.

- Databento: C 60.3, rank #578 of 1349 · https://www.anchorterminal.com/tools/databento.min.md
- EODHD: C 59, rank #651 of 1349 · https://www.anchorterminal.com/tools/eodhd.min.md
- Databento, good 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. Ahead on Schema & documentation, 75 against 70; Security & auth, 61 against 39.
- EODHD, good for Agents that need long end-of-day history, dividends and splits and fundamentals across 60 exchanges at a low monthly price, with weighted calls to budget. Ahead on Reliability, 65 against 50; Payments & pricing, 30 against 22. Also Runs on your own machine; Free to start without a card.

| Category | Databento | EODHD |
| --- | --- | --- |
| Reliability (16%) | 50 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 70 |
| Agent ergonomics (13%) | 80 | 76 |
| Security & auth (14%) | 61 | 39 |
| Payments & pricing (10%) | 22 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 82 |
| Transparency & trust (7%) | 49 | 52 |

| Fact (where they differ) | Databento | EODHD |
| --- | --- | --- |
| Vendor | Databento, Inc. | Unicorn Data Services |
| Hosted endpoint | `https://hist.databento.com` | `https://eodhd.com/api` |
| Transports | HTTP | HTTP, Streamable HTTP, SSE (legacy), stdio, websocket |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Licence | Apache-2.0 (clients) | none |
| Tools exposed | none | 88 |
| Last release | 2026-10-28 | 2026-10-15 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 309 stars | 24 stars |

Why the edge:
- Security & auth, Databento +22: 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.); EODHD 39 (One token per account with no scopes, shown as `api_token=` in the query string on every docs page, with a Bearer header allowed per llms.txt; the MCP v1 address embeds the token and v2 uses OAuth 2.1 with one scope, full-access (20 less 10 for the query string, so 10). All REST calls read; three MCP report tools trigger provider-side report generation and email (14 of 20). News and sentiment are third-party text and no guidance was found (5 of 15). A usage endpoint and dashboard show calls spent, not a per-call log (6 of 15). No security.txt, disclosure policy, bug bounty or certification found; the MCP server's CI runs Bandit, Semgrep and pip-audit (4 of 20). 10 + 14 + 5 + 6 + 4 = 39.)
- Reliability, EODHD +15: 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.); EODHD 65 (Read with the hosted lines. A public status page exists at uptime.eodhistoricaldata.com, an UptimeRobot page announced on the blog on 27 March 2020 (20), but its figures load by script and our reader got an error, so no incident history could be read (5). Limits are published with numbers, 20 calls a day free, 100,000 a day on paid plans, 1,000 requests a minute, with call weights per endpoint (15). 429 carries Retry-After, X-RateLimit headers report the ceiling, and 402 marks an exhausted allowance; reads only (15). The terms promise commercially reasonable efforts and no SLA, with SLAs sold by sales (0). The core API is generally available, with several newer APIs marked beta (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.)
- Payments & pricing, EODHD +8: 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.); EODHD 30 (No x402, MPP or L402 (0). Plan prices are public without login, personal and commercial, sold by the month with daily call allowances and per-endpoint call weights rather than per call (10). A free plan at 20 calls a day with no card (20). The token comes from a browser signup and no key API was found (0). 0 + 10 + 20 + 0 = 30.)
- Schema & documentation, Databento +5: 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.); EODHD 70 (An OpenAPI 3.1 document in a public repository covers 74 endpoints, last updated 18 February 2026, and the MCP server's 88 tools carry typed inputs and annotations in the source (22 of 25). llms.txt of 32 KB and an llms-full.txt, plus documentation resources inside the MCP server (10). Each API page states its purpose and plan, and tool titles name the dataset, with little on when not to use one (14 of 20). Parameters are documented with formats and the symbol convention is spelled out, but allowed values sit in prose (8 of 15). Examples on every API page and the demo token, with 401, 402, 403, 404, 422 and 429 documented in llms.txt and the limits article (11 of 15). Exchange Details v2 shipped in May 2026 with v1 kept, MCP has v1 and v2, and new APIs are announced on a dated blog, but there is no changelog page (5 of 15). 22 + 10 + 14 + 8 + 11 + 5 = 70.)