# Benzinga vs Intrinio (slim)

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

- Full: https://www.anchorterminal.com/compare/benzinga-vs-intrinio.md (~4,200 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/benzinga-vs-intrinio.json · canonical https://www.anchorterminal.com/compare/benzinga-vs-intrinio
- 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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Intrinio scores 54.2 (C) on agent readiness against Benzinga's 49.2 (D), and leads in 5 of 7 scored categories. Benzinga leads on schema & documentation. Both do market news.

- Benzinga: D 49.2, rank #1001 of 1349 · https://www.anchorterminal.com/tools/benzinga.min.md
- Intrinio: C 54.2, rank #813 of 1349 · https://www.anchorterminal.com/tools/intrinio.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 43.
- Intrinio, good for An agent doing US equity, options and fundamentals research on a paid plan that wants one vendor for prices, filings, estimates and an OAuth MCP server. Ahead on Reliability, 83 against 60; Agent ergonomics, 70 against 65; Payments & pricing, 20 against 0; Maintenance & community, 70 against 56; Transparency & trust, 51 against 44.

| Category | Benzinga | Intrinio |
| --- | --- | --- |
| Reliability (16%) | 60 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 43 |
| Agent ergonomics (13%) | 65 | 70 |
| Security & auth (14%) | 36 | 35 |
| Payments & pricing (10%) | 0 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 56 | 70 |
| Transparency & trust (7%) | 44 | 51 |

| Fact (where they differ) | Benzinga | Intrinio |
| --- | --- | --- |
| Vendor | Benzinga | Intrinio, Inc. |
| Hosted endpoint | `https://api.benzinga.com` | `https://api-v2.intrinio.com` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-05-27 |
| 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 | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 34 stars | 76 stars |

Why the edge:
- Schema & documentation, Benzinga +28: 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.); Intrinio 43 (No OpenAPI document was found. The SDKs are generated from a spec that declares API version 2.135.4, but the spec itself isn't published, and the MCP server's tool definitions aren't in any public source (5 of 25). docs.intrinio.com/llms.txt and intrinio.com/llms.txt return 404, and there are no Markdown pages (0 of 10). Each endpoint page states what it returns with its parameters, with little on when not to use a call (12 of 20). Parameters are typed, with required ones marked and allowed values in prose (9 of 15). Code samples in six languages on every endpoint, and a response codes page that lists codes without a body format (10 of 15). The v2 path is versioned, but the version history lists 2.0.0 to 2.6.2 with no dates and is out of step with the SDK's API version (7 of 15). Total 43.)
- Reliability, Intrinio +23: Benzinga 60 (Graded as a hosted service. Atlassian Statuspage at benzinga1.statuspage.io with seven API components (20). The incident feed holds 14 incidents, the newest on 14 September 2023, so the 90 days to 3 November 2026 are clean (30). No rate limit numbers are published; the FAQ says limits depend on the API and the subscription tier (0 of 15). No 429, Retry-After or backoff guidance was found in the docs or the specs (0 of 15). No SLA was found; the architecture page cites a 99.9 per cent availability figure as a claim, and the terms were unread (0). The APIs are generally available (10). Total 60.); Intrinio 83 (Graded as a hosted service. Atlassian Statuspage at status.intrinio.com with APIv2 and APIv1 components (20). The incident feed's newest entry is a delayed SIP feed for CTA on 24 June 2026, so the 90 days to 3 November are clean (30). Limits are published in part. Pages above 100 records and bulk requests are 1 a minute on free feeds and 1 a second on paid ones, free feeds are throttled at 100 requests a second, and the daily and per-minute caps for a plan are shown only on the account page (8 of 15). A 429 carries an explanation of the limit and a 503 marks throttling or the 25-second timeout, with no Retry-After or backoff guidance (5 of 15). The Enterprise plan lists an SLA (10). The REST API is generally available (10). Total 83.)
- Payments & pricing, Intrinio +20: 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.); Intrinio 20 (No x402, MPP or L402 (0). Plan prices are public without a login, $150, $333 rising to $999, and $1,250 and up, with no per-call price (10). Both self-serve plans say a free trial is available, and the trial length and card requirement were not found on the pricing, plan or terms pages, since the plan pages are drawn by script (10 of 20). A person signs up in a browser; no key API was found (0). Total 20.)
- Maintenance & community, Intrinio +14: 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.); Intrinio 70 (The six real-time websocket SDK repositories were pushed between 22 and 29 October 2026, and the MCP server is labelled New on the vendor's page (30). The last tagged release found is intrinio-sdk 7.2.0 on PyPI on 27 May 2026, following 7.0.0 on 2 March and 7.1.0 on 24 March; the October pushes have no tags or dated changelog entries, and the API version history carries no dates (10 of 20). Support is live chat through HubSpot, an AI chat and support@intrinio.com, with a status page; GitHub issue activity was not read (8 of 15). Official SDKs are current in six languages (15). The Python SDK is generated by swagger-codegen with CI not checked (7 of 10). Total 70.)
- Transparency & trust, Intrinio +7: 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.); Intrinio 51 (A closed service under terms effective 3 September 2026 that are clear on personal, internal and commercial use and name Intrinio, Inc. (15 of 30). The privacy policy is dated 30 June 2018, names no retention periods, subprocessors or DPA, and says only that connection details may be retained; the terms require deletion within 30 days of termination with an officer's certification (8 of 30). No deprecation policy, and the version history has no dates (3 of 20). Data is processed in the United States; no subprocessor list (5 of 20). Total 31.)
- Agent ergonomics, Intrinio +5: 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.); Intrinio 70 (`page_size` from 100 up to 10,000 sizes a response, and the MCP server batches ticker lists, but there is no field selection (15 of 25). `next_page` tokens, date and symbol filters on the data endpoints (18 of 20). Response codes are documented, 403 for an unsubscribed feed and 429 with a limit explanation, with no error body format or error code reference (10 of 20). Every call is a read and the vendor says the MCP server writes nothing back, but no readOnlyHint or safe-retry guidance was found (12 of 20). Few required parameters, and official SDKs in Python, C#, Java, JavaScript, R and Ruby (15). Total 70.)