# Benzinga vs Tiingo (slim)

> Benzinga scores 49.2 (D) to Tiingo's 46.2 (D) for market news. Prices, MCP, x402, uptime and agent notes side by side.

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

Benzinga scores 49.2 (D) on agent readiness against Tiingo's 46.2 (D), and leads in 4 of 7 scored categories. Tiingo leads on payments & pricing and transparency & trust. Both do market news.

- Benzinga: D 49.2, rank #1043 of 1349 · https://www.anchorterminal.com/tools/benzinga.min.md
- Tiingo: D 46.2, rank #1118 of 1349 · https://www.anchorterminal.com/tools/tiingo.min.md
- Benzinga, good for A licensed firm's agent that needs Benzinga's own newswire, calendars, analyst ratings and transcripts as structured data with deltas. Ahead on Schema & documentation, 71 against 39; Agent ergonomics, 65 against 56; Maintenance & community, 56 against 50.
- 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 Payments & pricing, 30 against 0; Transparency & trust, 57 against 44.

| Category | Benzinga | Tiingo |
| --- | --- | --- |
| Reliability (16%) | 60 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 39 |
| Agent ergonomics (13%) | 65 | 56 |
| Security & auth (14%) | 36 | 32 |
| Payments & pricing (10%) | 0 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 56 | 50 |
| Transparency & trust (7%) | 44 | 57 |

| Fact (where they differ) | Benzinga | Tiingo |
| --- | --- | --- |
| Vendor | Benzinga | Tiingo Inc. |
| Hosted endpoint | `https://api.benzinga.com` | `https://api.tiingo.com` |
| Transports | HTTP | HTTP, websocket |
| Pricing | Paid | Freemium |
| Last release | 2026-11-03 | 2026-10-09 |
| Privacy policy last updated | couldn't be read | 2026-02-18 |
| Popularity | 34 stars | none |

Why the edge:
- Schema & documentation, Benzinga +32: Benzinga 71 (The docs are generated from 11 OpenAPI 3 specs in the public Benzinga/benzinga-docs repository, 80 operations, and the raw YAML is linked from the welcome page (25). llms.txt and a Markdown twin of every page (10). Operations carry a summary and a sentence or two on scope, with little on when not to use a call (12 of 20). Typed query parameters with enums on the calendar (50) and news (9) specs, and the token as a query parameter (10 of 15). Examples on most operations, but the error responses in the specs are thin, 400, 499 and 500 on news, with the 401 and 404 bodies shown only as examples (9 of 15). Versioned paths (/api/v2) and three changelog pages that are empty templates (5 of 15). Total 71.); 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.)
- Payments & pricing, Tiingo +30: Benzinga 0 (No x402, MPP or L402 (0). No prices are published anywhere we could read; the docs say to email or call licensing and the APIs page on www.benzinga.com answered 403 (0). The FAQ says a trial or sandbox is often available, with no terms, length or card condition, and the registration page was unread (0). A person registers in a browser or by email (0). Total 0, with pricing and registration recorded as unchecked.); Tiingo 30 (No x402, MPP or L402 (0). Two plan prices public without login, $0 and $30 a month, sold by requests an hour and a day rather than per call; fundamentals and commercial licences by email (10). A free Starter plan at 1,000 requests a day with no card requirement stated (20). The token comes from a browser signup, and the developer programme forbids programmatic registration (0). 0 + 10 + 20 + 0 = 30.)
- Transparency & trust, Tiingo +13: Benzinga 44 (A closed service whose terms could not be read, since www.benzinga.com answered 403; the docs footer links them (8 of 30). The privacy policy was unread for the same reason, and the docs say nothing about retention (0 of 30, unchecked). No deprecation policy or dated notices; the changelog pages are empty (0 of 20). The architecture page says the platform runs on Amazon Web Services with Kong Gateway, with no subprocessor list or data location statement (5 of 20). Total 13.); 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.)
- Agent ergonomics, Benzinga +9: Benzinga 65 (`displayOutput` of headline, abstract or full sizes a news response, and `pageSize` runs to 100 (18 of 25). `page` and `pageSize`, ticker, channel, date and `updatedSince` filters, with a 10,000-item cap per query that the docs explain how to work round (18 of 20). Error bodies carry a code, an id and a message in the examples, but an unknown node ID returns 200 with an empty array and the spec's response list doesn't match the examples (10 of 20). Every data call is a read, with no safe-retry guidance; the webhook API registers endpoints (12 of 20). Few required parameters, but the Python client is from 2021, the JavaScript client from 2023 and the docs' SDK page is template text (7 of 15). Total 65.); 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.)
- Maintenance & community, Benzinga +6: Benzinga 56 (The docs repository had commits on 2 and 3 November 2026 moving OpenAPI specs from GitLab, and the robots.txt is versioned 11 September 2026 (30). Eight commit days between 23 October and 3 November 2026, all spec transfers, with no dated changelog entry anywhere (12 of 20). Support is licensing@benzinga.com, partners@benzinga.com and a phone line, with a status page; GitHub issue responsiveness was not read (6 of 15). The Python client's last PyPI release is 1.21 of 8 February 2021 and the JavaScript client was last pushed in July 2023, so no current official SDK (5 of 15). The Python client repository was pushed in March 2026 with no release; CI not checked (3 of 10). Total 56.); 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.)