# EODHD vs Twelve Data (slim)

> Twelve Data scores 70 (BB) to EODHD's 59 (C) for market history. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/eodhd-vs-twelve-data.md (~4,200 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/eodhd-vs-twelve-data.json · canonical https://www.anchorterminal.com/compare/eodhd-vs-twelve-data
- 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)

Twelve Data scores 70 (BB) on agent readiness against EODHD's 59 (C), and leads in 5 of 7 scored categories. Both do market history.

- EODHD: C 59, rank #651 of 1349 · https://www.anchorterminal.com/tools/eodhd.min.md
- Twelve Data: BB 70, rank #197 of 1349 · https://www.anchorterminal.com/tools/twelve-data.min.md
- 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.
- Twelve Data, good for Agents that need prices and time series across many exchanges and asset classes with one contract, CSV output, and a documented error table. Ahead on Reliability, 83 against 65; Schema & documentation, 83 against 70; Agent ergonomics, 84 against 76; Security & auth, 54 against 39; Transparency & trust, 67 against 52. Also Agent-ready, a grade of BB or better.

| Category | EODHD | Twelve Data |
| --- | --- | --- |
| Reliability (16%) | 65 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 83 |
| Agent ergonomics (13%) | 76 | 84 |
| Security & auth (14%) | 39 | 54 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 82 |
| Transparency & trust (7%) | 52 | 67 |

| Fact (where they differ) | EODHD | Twelve Data |
| --- | --- | --- |
| Vendor | Unicorn Data Services | Twelve Data Pte. Ltd. |
| Hosted endpoint | `https://eodhd.com/api` | `https://api.twelvedata.com` |
| Transports | HTTP, Streamable HTTP, SSE (legacy), stdio, websocket | HTTP, Streamable HTTP, stdio, websocket |
| Tools exposed | 88 | 27 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-15 | 2026-10-12 |
| Terms last updated | no date given | 2026-01-01 |
| Privacy policy last updated | no date given | 2026-09-22 |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 24 stars | 791 stars |

Why the edge:
- Reliability, Twelve Data +18: 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.); 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.)
- Security & auth, Twelve Data +15: 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.); 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.)
- Transparency & trust, Twelve Data +15: EODHD 52 (A closed, proprietary API under terms that name the entity and the personal and professional user classes but carry no date and no governing law; the MCP server and OpenAPI document are MIT (15 of 30). The privacy policy is undated, keeps data while the account is active with no periods, names Google only, and no DPA was found; the MCP server's telemetry is disclosed in its README (8 of 30). No deprecation policy; Exchange Details v1 was kept when v2 shipped, and new APIs are dated on the blog (5 of 20). No subprocessor list or data locations beyond Google as an advertising platform (2 of 20). 15 + 8 + 5 + 2 = 30.); 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.)
- Schema & documentation, Twelve Data +13: 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.); 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.)
- Agent ergonomics, Twelve Data +8: EODHD 76 (The REST API is the surface graded. `from`, `to`, `period`, `fmt`, `filter` on fundamentals and `limit` on news size responses, and the hosted MCP server lists 72 or 88 tools (15 of 25). `limit` and `offset` on news and the screener, date ranges on series, bulk per exchange (15 of 20). Error codes an agent can branch on, 402 and 403 with meanings, and the MCP server answers 403 with what the plan covers (15 of 20). Every REST call is a read; 85 of 88 MCP tools carry readOnlyHint true and the three Praams report tools are marked otherwise (16 of 20). Few required parameters and official Python and Node.js libraries, with R, C# and PHP clients (15). 15 + 15 + 15 + 16 + 15 = 76.); Twelve Data 84 (The REST API is the surface graded. `outputsize` 1 to 5,000 with a default of 30, `format=CSV`, `dp`, date ranges and batch requests size responses, and the MCP server lists 27 tools (20 of 25). Date ranges, `outputsize` and exchange, country and type filters, with no cursor pagination (15 of 20). Error codes with meanings an agent can branch on, 403 for plan limits and 429 for credits (16 of 20). Every operation is a read, and the MCP source marks tools readOnlyHint (18 of 20). Few required parameters, a demo key, and official SDKs in Python, Node.js, Go, Java and R (15). 20 + 15 + 16 + 18 + 15 = 84.)