# Databento vs EODHD

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

- Canonical: https://www.anchorterminal.com/compare/databento-vs-eodhd
- Markdown: https://www.anchorterminal.com/compare/databento-vs-eodhd.md (~3,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-03

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: 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
- EODHD: grade C, 59/100, rank #651 of 1349. Markdown https://www.anchorterminal.com/tools/eodhd.md · JSON https://www.anchorterminal.com/api/v1/tools/eodhd.json
- Best financial market data APIs for AI agents: https://www.anchorterminal.com/best/market-data/index.md
- All 55 markets comparisons: https://www.anchorterminal.com/compare/market-data/index.md

## Which one, for what

### Databento (C)

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

Watch 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

### EODHD (C)

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 in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: Every docs page shows the token as `api_token=` in the query string, and the MCP v1 address carries it in the URL


## 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.

## Score by category

| Category | Weight | Databento | EODHD | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 65 | EODHD +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 70 | Databento +5 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 76 | Databento +4 |
| Security & auth | 14% (17.5 this run) | 61 | 39 | Databento +22 |
| Payments & pricing | 10% (12.5 this run) | 22 | 30 | EODHD +8 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 84 | 82 | Databento +2 |
| Transparency & trust | 7% (8.8 this run) | 49 | 52 | EODHD +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **60.3 · C** | **59 · C** | |

## Facts side by side

| Fact | Databento | EODHD |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| 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 |
| x402 | no | no |
| Licence | Apache-2.0 (clients) | none |
| Tools exposed | none | 88 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| 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 |

## 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.

**EODHD.** Limits, call weights, rate-limit headers, 429 with Retry-After and 402 on an exhausted allowance are documented, with an OpenAPI document and an open-source MCP server of 88 read-only tools. The token is documented in the query string, the MCP v1 address embeds it, the status page could not be read, and the terms carry no date, SLA or governing law.

## Before you call either

### Databento

1. Call `metadata.get_cost` before `timeseries.get_range`, and set a monthly historical limit in the portal; a duplicate streaming request is charged twice
2. 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
3. On 429 wait for the Retry-After header; keep under 100 time series requests a second and 20 batch submissions a minute per IP
4. Check status.databento.com before retrying a slow or 504 Historical request, since several incidents since August were API outages or batch delays
5. 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

### EODHD

1. Send the token as `Authorization: Bearer`, which llms.txt allows, rather than `api_token=` in the URL, and prefer the v2 OAuth MCP address over v1
2. Budget calls, not requests; fundamentals cost 10, intraday and news 5, bulk 100 or more, and a 404 for a bad ticker is still charged, so resolve tickers with the search endpoint first
3. Read `X-RateLimit-Remaining` and honour Retry-After on 429; a 402 means the daily allowance is gone until midnight GMT and no retry will help
4. Use `{TICKER}.{EXCHANGE}` symbols in upper case, such as AAPL.US or EURUSD.FOREX, and `BTC-USD.CC` for crypto
5. Expect 20 calls a day and one year of history on the free plan; a 403 means the plan lacks the endpoint, not a bad key

## Questions

### Which is better for AI agents, Databento or EODHD?

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.

### Do Databento and EODHD need an API key?

Databento needs an API key. EODHD takes an API key or an OAuth sign-in.

### Can an agent call Databento and EODHD without installing anything?

Yes. Databento has a hosted endpoint at https://hist.databento.com and EODHD at https://eodhd.com/api.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/databento-vs-eodhd.json, and with the fewest tokens: https://www.anchorterminal.com/compare/databento-vs-eodhd.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "databento", "b": "eodhd"}`. From a terminal: `anchor compare databento eodhd`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/databento.json and https://www.anchorterminal.com/api/v1/tools/eodhd.json

## Other comparisons with Databento or EODHD

- [Alpha Vantage vs Databento](https://www.anchorterminal.com/compare/alpha-vantage-vs-databento.md)
- [Alpha Vantage vs EODHD](https://www.anchorterminal.com/compare/alpha-vantage-vs-eodhd.md)
- [Benzinga vs Databento](https://www.anchorterminal.com/compare/benzinga-vs-databento.md)
- [Databento vs Financial Datasets](https://www.anchorterminal.com/compare/databento-vs-financial-datasets.md)
- [Databento vs Financial Modeling Prep](https://www.anchorterminal.com/compare/databento-vs-financial-modeling-prep.md)
- [Databento vs Finnhub](https://www.anchorterminal.com/compare/databento-vs-finnhub.md)
- [Databento vs Intrinio](https://www.anchorterminal.com/compare/databento-vs-intrinio.md)
- [Databento vs Massive (formerly Polygon.io)](https://www.anchorterminal.com/compare/databento-vs-massive.md)
- [Databento vs Tiingo](https://www.anchorterminal.com/compare/databento-vs-tiingo.md)
- [Databento vs Twelve Data](https://www.anchorterminal.com/compare/databento-vs-twelve-data.md)
- [EODHD vs Financial Datasets](https://www.anchorterminal.com/compare/eodhd-vs-financial-datasets.md)
- [EODHD vs Financial Modeling Prep](https://www.anchorterminal.com/compare/eodhd-vs-financial-modeling-prep.md)
- [EODHD vs Finnhub](https://www.anchorterminal.com/compare/eodhd-vs-finnhub.md)
- [EODHD vs Intrinio](https://www.anchorterminal.com/compare/eodhd-vs-intrinio.md)
- [EODHD vs Massive (formerly Polygon.io)](https://www.anchorterminal.com/compare/eodhd-vs-massive.md)
- [EODHD vs Tiingo](https://www.anchorterminal.com/compare/eodhd-vs-tiingo.md)
- [EODHD vs Twelve Data](https://www.anchorterminal.com/compare/eodhd-vs-twelve-data.md)
- [Benzinga vs EODHD](https://www.anchorterminal.com/compare/benzinga-vs-eodhd.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp