Polygon.io
polygon.io · Developer / Data APIs modeIntegrated
Last probed 2026-08-10 00:39 UTC · Verified (Partial)
Polygon.io — Self-serve financial market data API.
Verdict: An agent can discover, activate, and operate on its own. Manage isn't assessed yet.
- DiscoverEasy
- ActivateEasy
- OperateEasy
- ManageNot assessed
Capability parity
Each stage answers one question about what an agent can do unattended. Stages are ordered by the credential-gateway dependency: Activate issues the keys that unlock Operate and Manage.
Discover
Can an agent find and read it, no account?
- Be found by a retrieval agentEasy
Retrieval access present.
Evidence
- Path tried
- robots.txt / sitemap / discovery headers
- Where it stalled
- completed
- Evidence tier
- Tier 2 (live attempt)
- Verification
- Evidence-only — graded from passive signal, not live-verified.
- Backing checks
retrieval_bot_access, sitemap_xml
- Read what it does and how to use itEasy
Machine-readable docs present.
Evidence
- Path tried
- llms.txt / AGENTS.md / schema.org / docs
- Where it stalled
- completed
- Evidence tier
- Tier 1 (unauth probe)
- Verification
- Evidence-only — graded from passive signal, not live-verified.
- Backing checks
llms_txt, llms_full_txt
- Read pricing & limits without loginNot assessed
Activate
Can an agent sign up and walk away with the keys it needs?
- Create an account self-serveEasy
Signup inspected — no blocker found.
Evidence
- Path tried
- signup flow
- Where it stalled
- completed
- Evidence tier
- Tier 1 (unauth probe)
- Verification
- Evidence-only — graded from passive signal, not live-verified.
- Obtain an API / MCP access credentialNot assessed
- Obtain a management / admin keyNot assessed
- Accept the terms without a bot-banEasy
No bot-prohibition signal found.
Evidence
- Path tried
- ToS / policy scan
- Where it stalled
- completed
- Evidence tier
- Tier 0 (passive scan)
- Verification
- Evidence-only — graded from passive signal, not live-verified.
Operate
Can an agent do the service's actual jobs — call, transact, pay?
- Call the primary service over MCP / APIEasy
Verified by a live call.
Evidence
- Path tried
- API / MCP / browser
- Where it stalled
- completed
- Evidence tier
- Tier 2 (live attempt)
- Verification
- Verified — a live attempt completed.
- Complete a transaction / checkoutNot applicable
Integrated tool — the API call is the transaction, no separate checkout.
- Pay via an agent rail (x402 / ACP / AP2)Not assessed
Manage
Can an agent administer the account and provision resources?
- Provision / scale / tear down a serviceNot assessed
- Change account details / set budget / rotate keysNot assessed
- View usage & billingNot assessed
- Cancel / export / delete (offboard)Not assessed
Findings
How scoring works →Interrupt tier: Moderate-Interrupt — derived from 2 findings; interrupt score 60 / 100 — the badge-driving metric. (range 28.8–78.8 · 8 unassessed)
Every tool starts at 100. Each interrupt found subtracts a penalty of base weight × timing × hardness × evidence — the multiplier values below come from the same rubric tables the score is computed with. New snapshots also provisionally subtract 50% of the full worst-case tax for each unassessed property and 25% for evidence-graded successes not live-verified by Tier 2.
Property coverage
A check only counts as clean when a probe tier capable of detecting that interrupt actually ran and found nothing. Not tested ≠ clean.
| Property | Stage | State | Evidence | Required |
|---|---|---|---|---|
| Mandatory redirect to vendor’s own site | operate | failed | Active finding — itemized in the penalty matrix below. Tier 1 assesses this property. | no |
| No Machine Interface | operate | failed | Active finding — itemized in the penalty matrix below. Tier 1 assesses this property. | yes |
| SSO-only signup, no API-key issuance | activate | partial | Some coverage exists, but the available evidence is incomplete. Tier 1 assesses this property. | no |
| Mandatory phone verification call | activate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| Mailed physical code (postal) | activate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| “Contact sales” wall (no self-serve path) | activate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| Manual approval queue | activate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| Rate-limit-triggered manual review | manage | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| One-time account / payment-method provisioning | manage | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| Identity / KYC verification | activate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| Crypto wallet / key-custody setup | operate | unassessed | Tier 2 (live attempt) ran but did not gather enough evidence to claim clean. Tier 2 assesses this property. | no |
| CAPTCHA / bot-challenge | activate | success | None found — checked at Tier 0 (passive scan) + Tier 1 (unauth probe) + Tier 2 (live attempt) (evidence-graded; not yet live-verified by a Tier 2 probe) Tier 0 assesses this property. | no |
| Email OTP verification | activate | success | None found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt) (evidence-graded; not yet live-verified by a Tier 2 probe) Tier 1 assesses this property. | no |
| SMS / phone OTP verification | activate | success | None found — checked at Tier 1 (unauth probe) + Tier 2 (live attempt) (evidence-graded; not yet live-verified by a Tier 2 probe) Tier 1 assesses this property. | no |
| ToS clause banning automated/bot access | discover | success | None found — checked at Tier 0 (passive scan) (evidence-graded; not yet live-verified by a Tier 2 probe) Tier 0 assesses this property. | no |
| Interrupt found | Base weight | × Timing | × Hardness | × Evidence | = Penalty |
|---|---|---|---|---|---|
| Starting score | 100 | ||||
| No Machine InterfaceoperateNeither an MCP server nor a usable API machine interface was found after Tier 0 and Tier 1 candidate checks. | 9 | ×1one-time setup | ×2.5hard | ×0.8Tier 1 (unauth probe) | −18 |
| Mandatory redirect to vendor’s own siteSignupSignup mandatorily redirects off-domain to https://massive.com/dashboard/signup?redirect=%2Fdashboard%2Fkeys. | 4 | ×1one-time setup | ×1soft | ×0.8Tier 1 (unauth probe) | −3.2 |
| Total penalty | −21.2 | ||||
| Full unknown tax 105 — capped at 25 (point score uses 50% of the capped value) | −105 | ||||
| Evidence-graded tax (successes not live-verified by a Tier 2 probe) 130.2 — capped at 25 (point score uses 25% of the capped value) | −130.2 | ||||
| Raw score = 100 − 21.2 = 78.8 Point score = 78.8 − 50% × 25 − 25% × 25 = 60.0 → 60 | 60 | ||||
What would make this Easy
One concrete change per blocker found. These are the diffs between this listing's current parity and an unattended agent path.
- Operate — Mandatory redirect to vendor’s own siteExpose the transaction over an API / MCP so checkout doesn't require a browser redirect.
How we scored this
- Confidence: Verified (Partial) (0.75) — A live Tier-2 session ran but stopped early at a detected hard blocker — verified up to that point, unknown beyond it.
- Machine-Readability sub-score: 43 / 100 (a separate integration-ease signal — it never enters the Interrupt Score or badge).
- Some capability stages are not yet assessed — shown plainly in the spine above, never as a pass.
- Rubric, tiers, confidence model, and badge thresholds →
Machine-readability checks 43 / 100
Four check groups, equal weight: machine interfaces, browsing efficiency, element discoverability, and discovery/agent access. Each check carries an evidence grade (proven / plausible / emerging) — an honesty label that never weights the score. What these mean →
- llms.txtemergingFound — polygon.io/llms.txt (42.1 KB, 211 links)
- llms-full.txtemergingFound — polygon.io/llms-full.txt (956.4 KB, 94 links)
- AGENTS.mdemergingNot provided
- A2A agent cardemergingNot provided
- MCP server (well-known or official registry)plausibleNot provided
- OpenAPI/Swagger specplausibleNot provided
- Rate-limit headersplausibleNot provided
- Structured JSON error responsesplausibleNot provided
- OAuth authorization-server metadata (RFC 8414)provenNot provided
- API catalog (RFC 9727) (emerging)emergingNot provided
- Agent-payment discovery (x402 / UCP) (emerging)emergingNot provided
- Lean HTML transfer sizeplausible361 KB raw HTML (threshold 488 KB)
- Manageable DOM sizeplausible937 DOM nodes (threshold 1500)
- High content-to-markup densityplausibleNot provided
- Content readable without JS executionprovenraw HTML holds 96% of rendered text (7336 vs 7612 chars; threshold 40%)
- Clean-content alternate (RSS/Atom/feed/markdown)plausibleNot provided
- Serves markdown on Accept: text/markdownplausibleNot provided
- Interactive elements are semanticplausible67/67 semantic (100%); 0 div/span click targets
- Form fields have accessible namesplausibleNot checked — no form fields on the representative page
- Inputs carry autocomplete hintsplausibleNot checked — no autocomplete-eligible inputs
- WebMCP tools (modelContext API)emergingNot provided
- AI retrieval/search fetchers allowed (robots.txt)provenno retrieval-fetcher blocks in robots.txt
- Sitemap (indexability)plausibleFound — massive.com/sitemap.xml
- schema.org JSON-LD in raw HTMLplausibleNot provided
- Content-Signal directives (robots.txt)emergingNot provided
- Web Bot Auth key directory (emerging)emergingNot provided
- Discovery Link headers on homepage (emerging)emergingNot provided
- robots.txt AI-crawler accessplausibleno AI-crawler blocks in robots.txt
- Unauthenticated API error is structured JSONplausibleNot provided
- Unauthenticated API returns auth guidance (401/403 or documented)plausibleNot provided
- API exposes rate-limit headersplausibleNot provided
- API key obtainable without human interactionplausibleNot checked — no OpenAPI spec found; self-serve API-key path indeterminate from Tier 1
Evidence & history
Last probed 2026-08-10 00:39 UTC. The raw JSON is the archival record.
| Date | Score | Badge | Rubric version |
|---|---|---|---|
| 2026-08-10 00:39 UTC | 60 | Moderate-Interrupt (current) | [email protected] |
| 2026-08-10 00:23 UTC | 60 | Moderate-Interrupt | [email protected] |
| 2026-08-09 23:48 UTC | 45 | High-Interrupt | [email protected] |
| 2026-08-09 23:48 UTC | 60 | Moderate-Interrupt | [email protected] |
| 2026-08-09 23:48 UTC | 60 | Moderate-Interrupt | [email protected] |
| 2026-08-09 17:13 UTC | 60 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:25 UTC | 66 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:25 UTC | 66 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:17 UTC | 66 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:17 UTC | 66 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:14 UTC | 66 | Moderate-Interrupt | [email protected] |
| 2026-08-09 05:14 UTC | 88 | Low-Interrupt | [email protected] |
| 2026-08-09 03:14 UTC | 88 | Low-Interrupt | [email protected] |
| 2026-08-09 01:48 UTC | 88 | Low-Interrupt | [email protected] |
| 2026-08-09 01:45 UTC | 88 | Low-Interrupt | [email protected] |
| 2026-07-10 07:16 UTC | 100 | Low-Interrupt | [email protected] |
Alternatives in Developer / Data APIs
Other Developer / Data APIs tools in the same mode (integrated), ranked by Overall LLM-Friendliness (the mean of Interrupt Score and Machine-Readability) — comparable to this listing because they share its usage mode.