Head to head · Market prices · October 2026 research run

Finnhub vs Intrinio

Intrinio scores 54.2 (C) on agent readiness against Finnhub's 45.1 (E), and leads in 5 of 7 scored categories. Finnhub leads on schema & documentation and payments & pricing. Both do market prices.

Best financial market data APIs for AI agents · All 55 markets comparisons

Which one, for what

Finnhub E

Best for Agents that need one key across quotes, fundamentals, estimates, filings and transcripts with official libraries, and a free key for prototypes.

Ahead on

  • Schema & documentation, 58 against 43
  • Payments & pricing, 30 against 20

Also in its favour

  • Free to start without a card

Watch for

The Swagger document declares the key only as a token query parameter, and the examples carry it in the URL

Intrinio C

Best 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 48
  • Agent ergonomics, 70 against 56
  • Maintenance & community, 70 against 60
  • Transparency & trust, 51 against 27

Watch for

The API key is documented as api_key in the query string as the first option, with no scopes, rotation or expiry found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Intrinio +35

Finnhub 48

Read with the hosted lines. No status page was found on the site, in the docs document or on the MCP page (0), so no incident history could be read (5). Limits are published with numbers, 60 calls a minute on the free key, 150 to 900 a minute by plan, and 30 calls a second on top of every plan (15). The docs say the limit answers 429 and the MCP page says to wait a minute, with no Retry-After or backoff guidance (8 of 15). The home page says 99.99 per cent uptime with an SLA available for enterprise clients (10). The API is generally available (10). 0 + 5 + 15 + 8 + 10 + 10 = 48.

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.

Transparency & trust Intrinio +24

Finnhub 27

A closed service whose terms exist at a page that robots.txt disallows, so they were not read; the pricing page says every self-serve plan is personal use, and no legal entity or governing law was found (8 of 30). No privacy policy was found, /privacy redirecting to the home page (0 of 30). No deprecation policy or dated notices found (0 of 20). Stripe and Braintree scripts load on the site, but no processor list or data location is disclosed (0 of 20). 8 + 0 + 0 + 0 = 8.

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.

Schema & documentation Finnhub +15

Finnhub 58

A public Swagger 2.0 document covers 116 paths with a description on every operation, declaring the key as a query parameter and a 200 response only; the MCP tools were not read (20 of 25). /llms.txt returns the site's HTML shell and no Markdown docs exist (0 of 10). Each operation states its purpose, a premium marker and, on quote, advice against polling, with little on when not to use it (14 of 20). Required flags and types are set on 248 parameters, but allowed values such as news categories sit in description text and no enum is declared (8 of 15). Every operation has example URLs and sample code in five languages, while the only documented error is the 429 (9 of 15). The path carries v1 and no changelog or dated change notes were found (7 of 15). 20 + 0 + 14 + 8 + 9 + 7 = 58.

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.

Agent ergonomics Intrinio +14

Finnhub 56

The REST API is the surface graded. from and to on candles and news, and symbol-scoped calls, size responses; no field selection, and the MCP server lists 70 tools (12 of 25). Date filters but no pagination on most lists (10 of 20). Only the 429 is documented; a missing key answered 401 with a JSON error field in our one test call (5 of 20). All but one operation are GET reads; the MCP annotations were not read (14 of 20). Few required parameters and official libraries in six languages (15). 12 + 10 + 5 + 14 + 15 = 56.

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.

Payments & pricing Finnhub +10

Finnhub 30

No x402, MPP or L402 (0). Plan prices are public without login, read from the pricing page's script data, sold per dataset by the month with calls a minute rather than per call (10). A free key at 60 calls a minute with no card, which the pricing FAQ says can be used forever (20). The key comes from a browser signup and no key API was found (0). 0 + 10 + 20 + 0 = 30.

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 +10

Finnhub 60

Read as a closed service. The newest dated change is 2 November 2026, when finnhub-go, finnhub-ruby and finnhub-php gained a price target history endpoint; the MCP page is dated 6 August 2026 (30). Only that one dated change falls in the last 90 days, the previous library commits being 22 June 2026 (5 of 20). Support by email, with no public changelog or community channel found (5 of 15). Six official client libraries, finnhub-python at 2.4.29 of 24 June 2026 (15). The libraries are generated from the API document; no CI run was visible and the Python README names an older version than PyPI (5 of 10). 30 + 5 + 5 + 15 + 5 = 60.

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.

Score by category

CategoryWeight this runFinnhubIntrinioEdge
Reliability16%204883Intrinio +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25843Finnhub +15
Agent ergonomics13%16.25670Intrinio +14
Security & auth14%17.53235Intrinio +3
Payments & pricing10%12.53020Finnhub +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86070Intrinio +10
Transparency & trust7%8.82751Intrinio +24
Negative events≤1500
TotalE 45.1/100C 54.2/100

Facts side by side

FactFinnhubIntrinio
KindHTTP APIHTTP API
VendorFinnhubIntrinio, Inc.
Hosted endpointhttps://finnhub.io/api/v1https://api-v2.intrinio.com
TransportsHTTP, Streamable HTTP, websocketHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
Tools exposed70none
Read-only variant documentednoyes
llms.txtnono
Last release2026-11-022026-05-27
Terms last updatedcouldn't be readno date given
Privacy policy last updatedno document linkedno date given
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes
Popularity1.1k stars76 stars

Verdicts

Finnhub

A public Swagger document covers 116 endpoints, six official client libraries exist, and a free key gives 60 calls a minute with no card. The key is documented in the query string, no status page, changelog, error reference or privacy policy was found, and robots.txt kept the terms from our reader.

Intrinio

A read-only US equities, options and fundamentals API with a clean status history, SDKs in six languages, paging up to 10,000 records and an OAuth MCP server included in every plan. The REST key is documented in the query string, no OpenAPI document or llms.txt was found, the version history is undated, and plans start at $150 a month.

Before you call either

Finnhub

  1. Send the key as the X-Finnhub-Token header, not as token= in the URL, and keep under 30 calls a second on top of the plan's per-minute limit
  2. Check the premium marker before calling; a free key reaches 29 operations and the rest answer with an error
  3. Poll /quote sparingly; the docs say constant polling is not recommended and point to the websocket for real-time updates
  4. Expect 401 {"error":"Please use an API key."} without a key and 429 over the limit; wait a minute before retrying, as the MCP page advises
  5. Self-serve plans are personal use; anything commercial needs the enterprise contact route

Intrinio

  1. Send the key as Authorization: Bearer, not ?api_key=, so it stays out of logs
  2. Expect 403 for a data feed the account isn't subscribed to, 429 with an explanation when a limit is hit, and 503 when a request passes 25 seconds; shrink the query rather than retry at once
  3. Keep page_size at 100 or below unless the plan is paid, since larger pages are limited to one request a minute on free feeds
  4. Confirm the plan before displaying or passing Intrinio data to anyone else; the Individual plan forbids it
  5. The MCP server returns a message naming the product that unlocks data outside the plan; don't retry the same call

Questions

Which is better for AI agents, Finnhub or Intrinio?

Intrinio scores 54.2 (C) on agent readiness against Finnhub's 45.1 (E), and leads in 5 of 7 scored categories. Finnhub leads on schema & documentation and payments & pricing.

Do Finnhub and Intrinio need an API key?

Finnhub takes an API key or an OAuth sign-in. Intrinio needs an API key.

Can an agent call Finnhub and Intrinio without installing anything?

Yes. Finnhub has a hosted endpoint at https://finnhub.io/api/v1 and Intrinio at https://api-v2.intrinio.com.

Other comparisons with Finnhub or Intrinio

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.