# Fix list: Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) From Anchor Terminal's listing at https://www.anchorterminal.com/tools/coinbase-cdp-agentkit, the October 2026 research run, assessed 1 October 2026. Grade BB, 71.6 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 Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP): 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. Reliability, 49 out of 100, up to 10.2 more on the total Why it scored 49: Scored on the hosted checklist although the listing is an SDK, because every wallet action ends in a call to Coinbase's API. status.coinbase.com, where the CDP docs redirect, has a Coinbase Developer Platform group with Wallets, Payments, Stablecoins, Trading, Webhooks and Portal components (20). Its RSS feed reaches back only to 10 September 2026 and holds no CDP incident; the earlier part of the 90 days needs JavaScript and we couldn't read it (12 of 30). We found no rate-limit numbers for the wallet APIs; the OpenAPI file defines 429 responses without figures (0). An optional `X-Idempotency-Key` with a 422 `idempotency_error`, and `rate_limit_exceeded` and `operation_in_progress` error types, but no Retry-After guidance (12 of 15). No SLA found (0). Server wallets and the awal CLI are generally available; the Agentic Wallet MCP server is labelled beta (5 of 10). 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. ## 2. Security & auth, 78 out of 100, up to 3.9 more on the total Why it scored 78: CDP API keys carry scopes (changing policies needs "Non-custodial > Manage"), the SDKs mint short-lived JWTs from them, and signing also needs a separate wallet secret through `X-Wallet-Auth`. Agentic Wallet sign-in is email OTP with no key handed to the agent (30). The operator sets max per call and max per session in the wallet UI and the agent can't change them; server wallets have a default-deny policy engine on value, address and network; `x402 pay` takes `--max-amount`. AgentKit itself has no caps or approval gate, as its README says (16 of 20). AgentKit's README names direct and indirect prompt-injection surfaces and points to guardrails middleware and a human-approval example, but the fix that sanitises attacker-set token names (merged 3 September) isn't released (10 of 15). Webhooks with delivery status and retry counts; we didn't check per-call logs in the Portal (10 of 15). HackerOne bug bounty linked from SECURITY.md in AgentKit and cdp-sdk; coinbase.com's security.txt had expired per the 30 September check, and the AgentKit file-read fix went through a public PR without an advisory (12 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. ## 3. Agent ergonomics, 83 out of 100, up to 2.8 more on the total Why it scored 83: The Agentic Wallet skill is a 4,040-byte router that loads one of nine reference files on demand and every `awal` command takes `--json`; the CDP CLI's MCP mode generates a tool per endpoint with a `cdp_help` lookup, which we couldn't read because the CLI source isn't public (18 of 25). `pageSize` and `pageToken` on 20 list operations, and SQL queries with `LIMIT` (18 of 20). Typed error codes with messages that say when to retry (18 of 20). Optional idempotency keys on writes; tool annotations not checked (14 of 20). SDKs in TypeScript, Python, Go, Rust and Java, and an Agentic Wallet signs in with two commands (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. ## 4. Maintenance & community, 77 out of 100, up to 2 more on the total Why it scored 77: The CDP CLI's latest npm tag is 2.0.97, after 2.0.94 on 29 September per the 30 September check, and cdp-sdk tagged Java 1.0.0 on 2 September (30). cdp-sdk tagged TypeScript 1.52.0 to 1.55.0 between 9 July and 4 August and syncs every few days (20). AgentKit is the weak spot. npm still serves 0.10.4 from 19 December 2025, the repository has carried an unpublished 0.11.0 since 24 March 2026, and four commits landed in August and September after none from April to July; we didn't read the issue queue (12 of 25). Current SDKs in five languages, but no official Coinbase entry in the MCP registry (8 of 15). cdp-sdk runs unit and end-to-end tests per language; AgentKit's npm build still pins zod 3 while the repository moved to zod 4 (7 of 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. ## 5. Payments & pricing, 85 out of 100, up to 1.9 more on the total Why it scored 85: Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Coinbase's own CDP SQL API answers x402 at x402.cdp.coinbase.com, but the wallet API itself isn't paid per call, so the part-of-its-own-API step (30 of 40). Coinbase also runs the CDP facilitator, and Agentic Wallet pays and sells x402 services. $0.005 per wallet operation after 5,000 free a month, reads free, with units per operation published (20). The Agentic Wallet, wallet creation and gas are free, and the free operations need no card that we could find (20). An agent with its own mailbox can sign in by email OTP through `awal auth login` and `verify`, per the official skill; server wallets need a person to create a CDP Portal key (15 of 20). 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. ## 6. Transparency & trust, 80 out of 100, up to 1.8 more on the total Made of editorial 65, provenance 95. Why it scored 80: AgentKit is Apache-2.0, cdp-sdk and the OpenAPI file are MIT, awal is Apache-2.0 on npm; the wallet service is closed under the CDP terms (25 of 30). The privacy policy, updated 27 May 2026, names Coinbase, Inc. for developer services, lists processing countries and transfer mechanisms (SCCs and the Data Privacy Frameworks), and ties retention to need without numbers (18 of 30). AgentKit's changelog marks the legacy cdp-wallet deprecated, without a removal date (10 of 20). Processing in Ireland, Germany, Singapore, the UK, the US and the Philippines is stated; service providers are named by category with no full subprocessor list (12 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: published but past its Expires date (5 of 10) ## 7. Schema & documentation, 94 out of 100, up to 1 more on the total Why it scored 94: A public OpenAPI file, version 2.0.0 with 208 operations, MIT-licensed in coinbase/cdp-sdk and regenerated into every SDK (25). llms.txt with 500+ links and Markdown twins of the docs (10). 3,113 descriptions in the OpenAPI file, and the Agentic Wallet skill says when to use it and routes each task to a reference file (17 of 20). An `ErrorType` enum of 26 codes, patterns and length limits on IDs (14 of 15). Examples throughout the OpenAPI file and docs, errors with `errorType` and `errorMessage` (15). `/v2` paths, a CDP changelog and changesets in AgentKit, though AgentKit's 0.11.0 changelog entry has never reached npm (13 of 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. ## Deductions Each comes off the total. A fixed and documented problem counts for less at the next check. - AgentKit's flaunch and zora action providers read any non-URL `image` argument as a local file path and uploaded the file to a public IPFS pinning service, so an injected agent could publish arbitrary host files (present since 2025-07-25). Fixed in source on 2026-08-19 by PR #1432 and documented in a changeset, but the npm package (0.10.4, 2025-12-19) still carries the path, so we deduct less than for an open incident. Only agents that register those providers are exposed (https://github.com/coinbase/agentkit/pull/1432). ## 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. - unchecked: CDP incident history before 10 September 2026; status history needs JavaScript and the RSS feed starts there - unchecked: the CDP CLI's MCP tool definitions and annotations; the CLI source isn't public - unchecked: AgentKit's open issues and response times - Whether Coinbase will publish AgentKit 0.11.0 with the file-read fix, or retire AgentKit in favour of the CDP CLI and awal - Rate limits for the wallet APIs; we found none published ## Weaknesses - AgentKit on npm is 0.10.4 from December 2025, and its fix for a local file read and public upload path is unreleased - Agentic Wallet caps are amounts only; allowlists need server wallets and the policy engine - No published rate limits or SLA for the wallet APIs - Agentic Wallet MCP is beta and can only discover and pay - No official Coinbase entry in the MCP registry ## 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. - Run `npx awal@2.12.1 status` first and sign in with `auth login` and `auth verify` if it fails - Pass `--max-amount` on every `awal x402 pay`; 1000000 is $1.00 - Send an `X-Idempotency-Key` on server-wallet writes so a retry can't send twice - Don't register AgentKit's flaunch or zora providers on 0.10.4; they read local files - Give an agent a policy-bound server account or an Agentic Wallet, never a full CDP API key ## What the review panel asked for - Document default caps - publish AgentKit 0.11.0 - advisories for fixes ## 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.