# EODHD vs Tiingo (slim)

> EODHD scores 59 (C) to Tiingo's 46.2 (D) for market history. Prices, MCP, x402, uptime and agent notes side by side.

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

EODHD scores 59 (C) on agent readiness against Tiingo's 46.2 (D), and leads in 5 of 7 scored categories. Tiingo leads on transparency & trust. Both do market history.

- EODHD: C 59, rank #651 of 1349 · https://www.anchorterminal.com/tools/eodhd.min.md
- Tiingo: D 46.2, rank #1118 of 1349 · https://www.anchorterminal.com/tools/tiingo.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. Ahead on Reliability, 65 against 60; Schema & documentation, 70 against 39; Agent ergonomics, 76 against 56; Security & auth, 39 against 32; Maintenance & community, 82 against 50. Also Runs on your own machine; Free to start without a card.
- Tiingo, good for Agents that need clean US end-of-day composites with dividend and split adjustments, fund fees and news on a cheap plan, and anyone who values a long changelog. Ahead on Transparency & trust, 57 against 52.

| Category | EODHD | Tiingo |
| --- | --- | --- |
| Reliability (16%) | 65 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 39 |
| Agent ergonomics (13%) | 76 | 56 |
| Security & auth (14%) | 39 | 32 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 50 |
| Transparency & trust (7%) | 52 | 57 |

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

Why the edge:
- Maintenance & community, EODHD +32: EODHD 82 (Read as a closed service with open-source tooling. The MCP server's last commit is 15 October 2026 and the Claude skills repository was updated 22 October (30). Dated changes in the last 90 days include MCP commits on 8, 9 and 17 September and 9, 10 and 15 October, and the real-time feed update of 26 August 2026 (20). Pull requests on the MCP repository are merged by the vendor, support is 24/7 by email and chat per the site, and forum.eodhd.com did not resolve for us (12 of 15). Official Python and Node.js libraries; the Python package's last PyPI release is 1.0.32 of 18 December 2024, though its repository was updated in October 2026 (12 of 15). The MCP server pins fastmcp, ships tests and a security toolchain in CI (8 of 10). 30 + 20 + 12 + 12 + 8 = 82.); Tiingo 50 (Read as a closed service. The changelog's newest entry is 9 October 2026 (30). Entries dated 9 October and 8 September 2026 fall in the last 90 days, with 21 July just outside, and the status page adds a maintenance window on 28 September (12 of 20). A dated changelog, a support address and a blog, with the developer programme promising priority email support (8 of 15). No official SDK (0 of 15). No package to assess (0 of 10). 30 + 12 + 8 + 0 + 0 = 50.)
- Schema & documentation, EODHD +31: 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.); Tiingo 39 (No OpenAPI document or MCP server was found (0 of 25). llms.txt and llms-full.txt are served, with product routing and licence notes (10). Each documentation page states the endpoint's purpose and timing, such as prices after 5.30 pm ET with corrections to 8 pm, with little on when not to use it (12 of 20). Parameters and response fields are tabled with names and meanings, but types, defaults and allowed values are partly in prose (8 of 15). Examples in Python, Node and PHP on every page; no error responses documented (7 of 15). A changelog dated by entry since 2017 and a one-year support commitment after breaking changes, with no version in the path (12 of 15). 0 + 10 + 12 + 8 + 7 + 12 = 39.)
- Agent ergonomics, EODHD +20: 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.); Tiingo 56 (`startDate`, `endDate`, `resampleFreq`, `format=csv` and column selection on some endpoints size responses; no field selection on end-of-day prices (15 of 25). Date ranges throughout and limit and offset on news, no cursor (15 of 20). Errors are undocumented; a missing token answered 403 with a JSON `detail` field in our one test call (3 of 20). Every call is a read (16 of 20). Few required parameters, but no official SDK; the docs point to third-party packages (7 of 15). 15 + 15 + 3 + 16 + 7 = 56.)
- Security & auth, EODHD +7: 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.); Tiingo 32 (One token per account with no scopes, documented as `?token=` in the URL or an Authorization header, with rotation on the account page since May 2026 (20 less 10 for the query string, plus 2 for rotation, so 12). Every endpoint is a read (15 of 20). News is third-party text and no guidance was found (5 of 15). A usage page shows hourly and daily requests and bandwidth, not a per-call log (0 of 15, no log). security.txt redirects on www and is absent on api, and no disclosure policy, bug bounty or certification was found (0 of 20). 12 + 15 + 5 + 0 + 0 = 32.)
- Reliability, EODHD +5: 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.); Tiingo 60 (Read with the hosted lines. A public status page on Instatus at status.tiingo.com lists 13 components with a notice history (20). The history in the 90 days to 3 November 2026 shows a 9 hour 59 minute outage of the Blue Ocean ATS endpoints on 21 October, a WebSocket issue on 21 September and two maintenance windows, with nothing recorded before 21 September; a long outage of one niche feed rather than the core price API (15). Limits are published with numbers, 50 and 10,000 requests an hour, 1,000 and 100,000 a day and 1 GB and 40 GB a month (15). No 429, Retry-After or backoff guidance was found (0). No SLA found (0). The end-of-day, news, crypto and forex APIs are generally available, while Equity Realtime and BOATS are in beta (10). 20 + 15 + 15 + 0 + 0 + 10 = 60.)
- Transparency & trust, Tiingo +5: 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.); Tiingo 57 (A closed service whose terms sit on app.tiingo.com, which answered 403 to every request, so they were not read; the pricing and documentation pages define internal, commercial and redistribution licences (8 of 30). The privacy policy is on the same host and was not read (0 of 30). The developer programme commits to a year of continued support after a breaking change, with changes posted in the changelog and emailed to registered developers, and the changelog's 9 October 2026 entry describes a changed default for prevClose (16 of 20). Equinix hosting is named on the about page, with no processor list or data location (4 of 20). 8 + 0 + 16 + 4 = 28.)