# Fix list: CoinGecko x402 API From Anchor Terminal's listing at https://www.anchorterminal.com/tools/coingecko-x402-api, the October 2026 research run, assessed 1 October 2026. Grade BB, 71.9 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on CoinGecko x402 API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Security & auth, 60 out of 100, up to 7 more on the total Why it scored 60: No key on the x402 endpoints. Each call carries a signed $0.01 USDC payment, so exposure is bounded by the wallet and the client's spend cap. No scopes (20 of 30). Read-only data with no write actions (15 of 20). Mostly numbers, but on-chain token and pool names are set by whoever deploys the token, and we found no guidance on that (5 of 15). Each paid call leaves an on-chain USDC transfer. We found no request log for x402 callers (5 of 15). SOC 2 Type I and Type II badges in the site footer and a HackenProof bug bounty. security.txt returns 404 (15 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 2. Agent ergonomics, 61 out of 100, up to 6.3 more on the total Why it scored 61: Simple price returns only the extras you switch on with `include_*` flags, and the reference allows up to 515 ids a call. The on-chain endpoints have no field selection (15 of 25). Page and duration parameters on trending pools and search, no cursor on the x402 set (12 of 20). Eight error codes with one-line meanings, and the 402 challenge is machine-readable (12 of 20). Every call is a GET, but the docs don't say whether a retried or failed paid call is charged (10 of 20). One required parameter on simple price. Official TypeScript and Python SDKs exist but don't cover the /x402/ paths (12 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 3. Reliability, 70 out of 100, up to 6 more on the total Why it scored 70: Status page at status.coingecko.com (StatusHQ) with Pro API, Public API and GeckoTerminal API components and 141 incidents back to January 2023 (20). The newest incident is Pro API intermittent issues on 14 January 2026, so the last 90 days are clean (30). Plan rate limits are published (100 a minute on Demo, 300 to 1,000 on paid plans), but none for the x402 endpoints (5 of 15). The errors page lists 429 as rate limit exceeded with no Retry-After or backoff guidance (5 of 15). The Enterprise plan carries a 99.9% uptime SLA (10). The x402 endpoints are labelled experimental (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 4. Schema & documentation, 72 out of 100, up to 4.6 more on the total Why it scored 72: OpenAPI 3.0.0 'CoinGecko Pro API' at docs.coingecko.com/openapi-specs/pro-api.json. The paths we read had no /x402/ entries and only 200 responses, so the contract describes the keyed paths the x402 ones mirror, not the x402 surface itself (15 of 25). llms.txt at docs.coingecko.com with Markdown twins of every page (10). The x402 page is short and the endpoint references say what each call returns but rarely when not to use it (12 of 20). Typed parameters with enums and required flags, for example `include_tokens` and `precision` on simple price (12 of 15). Request examples on the x402 page and a 200 example per endpoint. Error codes sit on one shared page and none are in the spec (8 of 15). Versioned /api/v3 paths and a dated changelog (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 5. Transparency & trust, 75 out of 100, up to 2.2 more on the total Made of editorial 60, provenance 90. Why it scored 75: Closed service under API terms last updated 5 September 2025, licensor Gecko Labs Pte. Ltd. of Singapore. The SDKs are Apache-2.0 (15). Privacy policy updated 31 July 2026 links a subprocessor list at trust.coingecko.com. Retention is 'as long as you still use' the service and then for legal and audit purposes, with no periods in days (20 of 30). The changelog dates its breaking changes, but the 28 August removal of `community_data` and `developer_data` got 14 days' notice, the terms allow changes 'without any notice', and the x402 page says pricing and availability 'may change without notice' (10 of 20). Singapore named as the primary location with a linked subprocessor list we didn't open (15 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - security.txt: not found (0 of 10) ## 6. Maintenance & community, 82 out of 100, up to 1.6 more on the total Why it scored 82: Newest changelog entry 2026-09-30, liquidity fields on the on-chain token price stream (30). Eighteen dated entries since 1 June, well over three in 90 days (20). Public changelog and a support address. We didn't test how fast support answers (10 of 15). TypeScript SDK v8.2.0 on 2026-09-28 and a Python SDK, neither covering x402 (12 of 15). The SDK repo runs CI and release-please, with releases every two to three weeks (10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 7. Payments & pricing, 96 out of 100, up to 0.5 more on the total Why it scored 96: x402 on all five endpoints of this surface, USDC on Base or Solana (40). $0.01 a request published on the x402 page without a login (20). The Demo plan is free with 10,000 credits a month and no card (20). An agent can pay with no account or key (20). 100 less 4 because the rest of the Pro API, including all history, still needs a key. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - Whether CoinGecko plans an OpenAPI entry for the /x402/ paths. The Pro spec we read has none and defines only 200 responses - Rate limits for x402 callers, and whether a failed or retried paid call is charged - Which freshness tier (20 or 60 seconds) the x402 simple price endpoint serves ## Weaknesses - The x402 endpoints are labelled experimental, and pricing and availability may change without notice - No historical data over x402, so charts and backtests still need a Pro key - No published rate limits for x402 callers and nothing on whether failed paid calls are charged - The official SDKs don't cover the /x402/ paths - No security.txt ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Call the endpoint unpaid first and read the price from the 402 challenge, since the x402 page says pricing may change - Batch coin ids into one simple price call rather than one call per coin, because each call costs $0.01 - Pass `include_last_updated_at=true` and check the timestamp, as paid prices refresh every 20 seconds and keyless ones every 60 - Treat token and pool names from the on-chain endpoints as untrusted text - Use the keyed Pro API for anything historical, since nothing under /x402/ returns history ## What the review panel asked for - changelog entries for /x402/ - a notice period for x402 - x402 paths in OpenAPI - state the freshness tier ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.