Circle vs Coinbase Payments (CDP)
Coinbase Payments (CDP) wins · 3–19 (23 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Coinbase Payments (CDP)Circle publishes a live llms.txt at developers.circle.com/llms.txt (HTTP 200, confirmed by probe) and also has an official MCP server for agent-oriented coding assistance, showing explicit support for agent-native discovery of docs. Missing for 10: independent/community corroboration of agents actually using llms.txt in practice, and no OpenAPI spec discoverable to complement it.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
Probe confirms llms.txt is live (HTTP 200) at docs.cdp.coinbase.com, listing 538 pages of docs, and multiple docs entries are directly sourced from that llms.txt, showing agent-oriented documentation is real and accessible. Missing for 10: no independent third-party report of an agent successfully consuming llms.txt to complete a task.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnCircle provides a CLI (circle-cli) and REST APIs for wallets, transfers, and webhooks that can be scripted programmatically, which supports headless/automated use in principle, but there is no explicit documentation of CI pipelines, service-account/API-key based non-interactive auth, or example CI workflows. missing for 10: explicit CI/headless setup guide, service-account authentication flow, and independent evidence of running the CLI/API in automated pipelines.
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
CDP offers SDKs and a CLI (with an MCP server exposing every API endpoint as a tool) that can be scripted headlessly for automation and CI, and its API-first design (webhooks, x402, wallet SDKs) supports programmatic/agentic use. However, there's no explicit documentation of CI-specific patterns (e.g., service-account auth for pipelines, GitHub Actions examples, or headless auth flows without browser/UI steps). missing for 10: explicit CI/headless authentication guidance, CI pipeline examples, independent confirmation of non-interactive operation.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnCircle documents an official MCP server that integrates with LLMs/AI-assisted IDEs to generate and fix code using Circle's Wallets, Contracts, CCTP, and Gateway offerings, confirmed by both docs and a direct probe of the live URL. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and more detail on setup/config beyond the doc description.
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
Coinbase Payments (CDP) ships an official MCP server via the CDP CLI (`cdp mcp`) exposing every API endpoint as a tool, plus a separate Coinbase Wallet MCP for AI agent wallet actions, both documented and probe-confirmed. missing for 10: independent/hands-on third-party corroboration beyond first-party docs and probes.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
ai-native userUse an official CLI
weight 2 · round drawnCircle documents an official CLI (circle-cli) explicitly built for agentic workflows—creating/managing wallets, transferring/swapping/bridging USDC, executing smart contracts, and discovering/paying for services 'through a single command interface,' confirmed via docs and a probe. Missing for 10: independent/hands-on verification of the CLI's real-world usage or community adoption beyond first-party docs.
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP ships an official CLI that also includes an MCP server (`cdp mcp`) exposing every API endpoint as a tool, and docs explicitly reference using the CDP CLI for treasury/payout workflows, directly supporting AI-native/agentic use. Missing for 10: independent hands-on verification of CLI usage and richer documentation of CLI command coverage beyond MCP exposure.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userDrive the product through a documented public API
weight 3 · round drawnCircle's developer platform (developers.circle.com) documents extensive public APIs covering wallets, CCTP cross-chain transfers, webhooks for event-driven integration, and a CLI/MCP server that wrap the same API, all confirmed live via llms.txt probe and doc excerpts. This clearly supports AI-native users driving the product programmatically. Missing for 10: a directly reachable OpenAPI/swagger spec (probe returned 404 on all standard paths) and independent third-party confirmation of API usability.
- [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”
- [claimed-docs] “Let users pay gas fees with USDC instead of native tokens using Circle's permissionless ERC-4337 paymaster contracts.”
- [claimed-docs] “CCTP natively transfers USDC across blockchains using burn-and-mint, and extends to EURC and registered third-party assets... all without tr…”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP exposes a documented public API/SDK covering wallets, payments, onramp, x402, and webhooks, with client libraries (cdp-sdk) and an explicit CLI/MCP server (`cdp mcp`) exposing every API endpoint as a tool for AI-native workflows. missing for 10: a discoverable OpenAPI/swagger spec (probe found all candidate paths 404), and independent third-party corroboration beyond vendor docs.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to CircleCircle's Agent Stack docs mention 'Agent wallets... with customizable spending controls and built-in compliance guardrails' (circle-docs-6), which implies some least-privilege control over what an agent can spend, but there is no documentation of scoped API keys, permission tiers, or credential issuance specifically for API access. Missing for 10: explicit API key/token scoping mechanism, documented permission levels for agent credentials, and any independent verification of these controls in practice.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
Coinbase Payments (CDP)none0/10The evidence pack describes CDP's payment features, wallets, webhooks, and an MCP/CLI surface for agents, but nowhere documents scoped or least-privilege API key/credential issuance (e.g., permission-limited API keys, role-based scopes, or agent-specific credential restrictions). Missing for 10: any mention of API key scopes/permissions, credential restriction mechanisms, or least-privilege agent authentication documentation.
ai-native userBuild against official SDKs
weight 2 · round to Coinbase Payments (CDP)Circlenone0/10Evidence describes Circle's APIs, CLI, MCP server, and webhooks, but no item mentions official language SDKs (e.g., Node/Python/Java client libraries) for building against Circle's platform; the OpenAPI spec probe even returned 404s, suggesting no evidence of SDK generation or distribution.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
Coinbase Payments provides official client SDKs (cdp-sdk on GitHub for EVM/Solana wallets), plus CLI and MCP server tooling explicitly aimed at AI-native/agentic use (x402 payments, MCP for AI assistants, wallet-per-agent support), all documented first-party. Missing for 10: independent/third-party corroboration of SDK quality and a public OpenAPI spec (probe found openapi.json 404s), which would strengthen developer trust.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userSubscribe to events via webhooks
weight 2 · round to Coinbase Payments (CDP)Circle documents webhooks that POST to a configured endpoint when resource state changes, enabling event-driven/agentic reactions to platform events. Missing for 10: details on event/topic subscription management, payload schema/signature verification docs, and independent/hands-on confirmation of reliability.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
Docs explicitly describe webhooks for real-time HTTP notifications on CDP integration events, including multi-address wallet activity subscriptions, which fits the ai-native agenticness theme of event-driven automation. Missing for 10: independent/hands-on confirmation of webhook reliability and no explicit event-type catalog or signature-verification detail in evidence.
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Coinbase Payments (CDP)Circle offers building blocks for autonomous background behavior—webhooks that react to state changes, CCTP triggers for automated actions after cross-chain transfers, and Agent wallets with spending controls—but there's no explicit documentation of a scheduler, persistent background job runner, or end-to-end 'set up and forget' automation workflow. Missing for 10: dedicated automation/scheduling API or dashboard, evidence of long-running autonomous agent execution, and independent confirmation these triggers work reliably in production.
- [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
CDP provides building blocks for autonomous background automation—webhooks for event-driven triggers, auto-liquidation/auto-convert on incoming payments, x402 for agent-to-agent programmatic payments, and an MCP server exposing all API endpoints as tools for AI agents to call—which together let developers wire up unattended, background-running payment flows. However, this is a set of APIs/SDKs and integration primitives rather than a hosted, first-party autonomous automation/orchestration runtime that runs itself; the user must build and host the actual automation logic. Missing for 10: evidence of a native scheduler or persistent agent-runtime service, and independent/hands-on confirmation that these pieces compose into a working autonomous background automation.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnCirclenone0/10Circle documents an 'Agent Stack' (agent wallets, x402 payments, CLI, MCP server) for building AI agents that consume Circle's crypto rails, but this is infrastructure for third-party agents to interact with Circle—not a built-in AI assistant inside Circle's own product that a user can delegate tasks to.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
ai-native userOperate the product with natural-language commands
weight 2 · round to Coinbase Payments (CDP)Circle offers an official MCP server (circle-docs-9, circle-probe-3) that lets LLMs/AI-IDEs interact with Circle's wallet/CCTP/contract APIs, and an 'agent-stack' with agent wallets and a CLI for programmatic control (circle-docs-6, circle-docs-8), suggesting some natural-language/agent-driven operability. However the MCP server is scoped to code generation/fixing rather than live natural-language command execution of transactions, and the CLI is explicitly a structured command interface, not NL-based. Missing for 10: evidence of an actual chat/NL interface for executing live operations (transfers, swaps) rather than just code generation, and independent confirmation of NL command usage in production.
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP exposes an MCP server (`cdp mcp`) that surfaces every API endpoint as a tool, and Coinbase Wallet MCP lets an AI assistant check balances, send funds, swap tokens, and pay with x402 — enabling natural-language operation via an MCP-compatible AI client. However, this requires a separate AI client/agent host to interpret NL commands; there's no evidence of a built-in chat/NL interface within CDP itself, no independent hands-on validation of the MCP tool coverage, and no examples of complex NL command sequences being executed reliably. missing for 10: first-party or independent demonstration of end-to-end natural-language command execution, evidence of NL interface beyond MCP tool exposure, and confirmation of reliability/robustness of the MCP tool-calling across the full API surface.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnCirclenone0/10Circle's developer docs are markdown-based (llms.txt) and reference APIs, but there's no evidence of an interactive API reference with runnable examples; probes for OpenAPI/Swagger specs that would power such a reference all returned 404.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
Coinbase Payments (CDP)none0/10There is no evidence of an interactive API reference with runnable examples; the OpenAPI spec probe returned 404s on all candidate paths, and no docs mention interactive playgrounds or executable code snippets. Missing for 10: interactive API reference UI, runnable/executable examples, OpenAPI/Swagger spec availability.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnCirclenone0/10The probe explicitly checked common OpenAPI spec paths (openapi.json, swagger.json, etc.) and all returned 404, indicating no downloadable machine-readable API spec is available, despite Circle having extensive API documentation. missing for 10: an actual OpenAPI/Swagger spec file accessible at a discoverable URL.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
Coinbase Payments (CDP)none0/10A direct probe for common OpenAPI spec paths returned 404s, and no evidence pack item links to a downloadable machine-readable API spec; only an llms.txt docs index and MCP/CLI tooling are documented, which are not equivalent to an OpenAPI spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to Coinbase Payments (CDP)Circlenone0/10The evidence pack contains no mention of a sandbox/testnet environment, test API keys, or any way to develop against non-production data; all docs describe production wallet, CCTP, CLI, and MCP features without noting a separate test mode. Missing for 10: any mention of sandbox/testnet endpoints, test credentials, or documentation distinguishing sandbox vs production usage.
Docs explicitly describe a Sandbox as 'a fully isolated testing environment for custodial features without connecting real funds,' directly matching the story. However, evidence doesn't clarify sandbox coverage for non-custodial/onchain, x402, or webhook features, nor provide hands-on confirmation of the isolation guarantee. Missing for 10: independent/hands-on verification of sandbox isolation, detail on which product areas are sandbox-covered vs not, and any test-data seeding or reset tooling.
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnCirclenone0/10No evidence of API versioning scheme or a documented deprecation policy; the openapi.json/swagger probes all 404, and no docs mention version numbers or deprecation timelines. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog or migration guide.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
Coinbase Payments (CDP)none0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes 404'd and none of the docs mention version numbers, sunset timelines, or deprecation notices.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Coinbase Payments (CDP)Circlenone0/10The evidence describes individual operations (wallet creation, single transfers, CCTP transfers, webhooks) via API/CLI/MCP, but no documentation mentions batch or bulk endpoints, bulk payout processing, or multi-item operations in one call. Missing for 10: batch API endpoints, bulk transfer/payout documentation, any bulk wallet or bulk transaction management feature.
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
The only concrete bulk-scale capability is watching up to 100 wallet addresses under one webhook subscription (`wallet.activity.multi`); all other documented operations (send payouts, provision addresses, checkout, onramp) are described as single-item flows with no batch/bulk endpoints shown. Missing for 10: bulk payout/disbursement APIs, batch transaction submission, bulk provisioning of addresses, and any explicit multi-item automation beyond webhook address watching.
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnCircle supports event-driven automation via webhooks that POST to your endpoint on state changes, CCTP's ability to trigger actions on the destination chain after assets arrive, and Agent wallets with customizable spending controls/policies — but these are developer-configured integrations, not a user-facing rules engine for defining arbitrary if/then automation. Missing for 10: a dedicated no-code/low-code rules builder, conditional logic across multiple event types, and evidence of AI-native users authoring rules themselves rather than developers wiring webhooks/paymaster policies.
- [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
CDP offers event-driven building blocks — webhooks for real-time notifications on wallet/payment activity, and built-in auto-liquidation/auto-convert triggered on fund receipt — that let a developer wire up automation, but there is no documented user-facing rules engine where an AI-native user declaratively defines 'if event X then action Y' logic; the developer must write the handling logic themselves. missing for 10: a declarative rules/automation engine, conditional logic support, or evidence of no-code rule definitions tied to webhook events.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnCirclenone0/10No evidence of any scheduling, cron-like, or recurring workflow/job capability in Circle's docs, CLI, MCP server, or webhooks — webhooks (circle-docs-10) are event-triggered, not scheduled, and no automation-scheduling feature is documented. Missing for 10: any scheduler/cron API, recurring job configuration, or workflow automation timing controls.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
Compliance risk — stories about compliance risk in this arenaCompliance risk
Stories about compliance risk in this arena
Kyc
ops leadCustomer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves
weight 2 · round drawnCirclenone0/10Evidence covers wallets, gas sponsorship, CCTP, agent wallets, CLI/MCP, and Circle Mint onboarding, but nowhere documents KYC/KYB endpoints or programmatic counterparty clearance flows before money moves. 'Qualified businesses can apply for a Circle Mint account' implies manual vetting, not a documented API-driven onboarding flow. missing for 10: documented KYC/KYB API endpoints, programmatic counterparty verification/clearance flow, any compliance-status check before transfer.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
Coinbase Payments (CDP)none0/10No evidence pack items mention KYC/KYB endpoints, counterparty verification, or onboarding flows to clear senders/recipients before funds move; docs cover payment rails, wallets, checkouts, webhooks, and stablecoins but nothing about identity/compliance verification APIs.
Licensing
founderSee who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried
weight 2 · round drawnCirclenone0/10The evidence pack contains no published list of Circle's licensed/registered entities or the jurisdictions they cover — only product/API docs and community commentary on SVB reserve issues, none of which addresses corporate/legal entity transparency.
Screening
ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at
weight 2 · round drawnCirclenone0/10The evidence pack contains only a generic mention of 'built-in compliance guardrails' for agent wallets, with no naming of sanctions screening, wallet risk checks, or travel-rule handling as specific mechanisms. As a regulated stablecoin/payments platform, this axis clearly applies, but no documentation evidence names these specific compliance processes.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Abstraction
developerI never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
weight 3 · round to Coinbase Payments (CDP)Circle's docs clearly show infrastructure abstraction — no raw key management, gas sponsorship via credit card, USDC-based gas payment, and automated cross-chain triggers — meaning developers don't operate blockchain nodes or handle gas directly (circle-docs-1, circle-docs-2, circle-docs-3, circle-docs-5). However, there's no direct evidence of a conventional REST API description or client libraries in specific languages, and a probe for a discoverable OpenAPI spec returned 404s across all candidate paths, weakening confidence in a standard REST/SDK developer experience. Missing for 10: explicit REST API documentation with endpoint/method examples, evidence of client libraries (SDKs) in specific languages, and a working OpenAPI/swagger spec.
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
- [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”
- [claimed-docs] “Let users pay gas fees with USDC instead of native tokens using Circle's permissionless ERC-4337 paymaster contracts.”
- [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
CDP provides a REST API plus client SDKs (cdp-sdk on GitHub for EVM/Solana wallets) that abstract key management, signing, and broadcasting, and custodial payment features (stable addresses, payouts, checkout) explicitly avoid onchain complexity for the developer. However, some flows (non-custodial send, wallet management) still expose wallet/chain concepts like signing and gas isn't fully hidden everywhere, and no OpenAPI spec was found (probe 404s) suggesting API conventionality is asserted but not independently verifiable, and multi-language client library breadth is unconfirmed beyond the single GitHub SDK repo. Missing for 10: verifiable OpenAPI/REST spec, evidence of multiple language SDKs, and confirmation gas/chain mechanics are fully invisible across all product surfaces.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Sandbox
developerRehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically
weight 3 · round to Coinbase Payments (CDP)Circlenone0/10No evidence pack item documents a sandbox/testnet mode, test values, or deterministic test environments for payments, payouts, or conversions; the docs describe live features (CCTP, wallets, payouts, Circle Mint) without mentioning any test/sandbox mode. missing for 10: documented sandbox or testnet environment, test API keys/values, deterministic test behavior for payments/payouts/conversions.
Coinbase documents a dedicated Sandbox as a fully isolated testing environment for custodial features without real funds, which covers payments-type scenarios. However, evidence doesn't confirm sandbox/testnet coverage extends deterministically to payouts and conversions specifically, nor describe deterministic test values/behaviors. Missing for 10: explicit documentation of testnet/sandbox coverage for payouts and conversions flows, description of deterministic test value behavior, and independent/hands-on confirmation of sandbox reliability.
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
Webhooks
developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
weight 2 · round drawnCircle's docs confirm a webhook system that POSTs to a configured endpoint when a resource changes state, which supports async state tracking without polling — but the evidence never mentions signing/signature verification of webhooks, nor explicitly lists event types like 'payment confirmed', 'payout settled', or 'conversion executed'. missing for 10: documentation of webhook signature/verification mechanism, explicit enumeration of event types matching payments/payouts/conversions, and any independent confirmation of webhook reliability in production.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
CDP docs confirm a webhooks system delivering 'real-time HTTP notifications when things happen across your CDP integration' and wallet-activity subscriptions, which supports state-tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed, nor does it enumerate the specific events named in the story (payment confirmed, payout settled, conversion executed) — it only shows generic notification and wallet-activity events. Missing for 10: explicit signature/verification mechanism documentation, and confirmation of payment/payout/conversion-specific event types.
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
Onramp conversion — stories about onramp conversion in this arenaOnramp conversion
Stories about onramp conversion in this arena
Conversion
developerConversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
weight 2 · round drawnCircle documents fiat↔USDC conversion via Circle Mint 'at no additional cost' and cross-border fiat payouts through CPN with 'real-time FX quotes' and settlement in USDC onchain, showing conversion is a core capability, but neither doc gives concrete rate/fee schedules or settlement-time SLAs, and no OpenAPI spec was found to confirm a dedicated conversion/quote endpoint (circle-probe-2 shows 404s). Missing for 10: documented fee tables, settlement-time guarantees, and a discoverable quotes/conversion API reference or independent verification of accuracy.
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
CDP docs show real conversion capabilities (auto-liquidation of onchain funds to fiat, USDC-to-USD auto-conversion into treasury, and converting crypto earnings to fiat) via docs-1, docs-14, docs-19, docs-20, indicating conversion is treated as a core, documented capability rather than a side effect. However, there's no evidence of a distinct quote endpoint, or documented exchange rates, fee schedules, or settlement-time SLAs for these conversions. Missing for 10: explicit quote API, documented conversion fee tables, documented settlement-time guarantees, stablecoin-to-stablecoin conversion documentation.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Onramp
developerEmbed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
weight 2 · round to Coinbase Payments (CDP)Circlenone0/10Evidence shows Circle Mint lets qualified businesses convert USD↔USDC directly (not an embeddable end-user onramp) and CPN handles cross-border fiat payouts, but no documented widget or API exists for embedding a card/bank-transfer fiat-to-stablecoin purchase flow for end users inside a third-party product.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
Coinbase Payments docs explicitly describe an Onramp letting end users buy crypto/stablecoins with card, Apple Pay, Google Pay, or Coinbase account delivered to a wallet, plus a Sandbox for isolated testing — matching the embedded fiat-to-stablecoin onramp story. Missing for 10: no widget code sample or explicit UI-embedding snippet shown, and no independent/hands-on corroboration beyond first-party docs.
- [claimed-docs] “Let users buy crypto with a card, Apple Pay, Google Pay, or a Coinbase account, delivered directly to their wallet”
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Coinbase Payments (CDP)Circle's docs show extensive API surface (Wallets, CCTP, Agent Wallets, CPN, webhooks) and even a CLI/MCP server built atop that API, suggesting API-first design, but no evidence explicitly confirms full UI/console parity, and the openapi spec probe returned 404s in all attempted locations, undermining verifiable completeness. missing for 10: explicit statement of API/UI feature parity, a discoverable OpenAPI spec, and independent confirmation that console-only features (e.g., dashboard settings) are also API-accessible.
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP's docs show extensive API/SDK/CLI coverage across virtually all payment features (onramp, offramp, checkout, payouts, custom stablecoins, x402, webhooks, treasury), and the CDP CLI even ships an MCP server exposing every API endpoint as a tool, indicating near-total API/CLI parity with any dashboard UI. Missing for 10: no explicit UI-vs-API feature parity statement and no discoverable OpenAPI spec (probe returned 404s for common spec paths), so full completeness/discoverability can't be fully confirmed.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userRead the product's source under an open license
weight 2 · round drawnCirclenone0/10No evidence of Circle publishing source code under an open license; Circle is a closed commercial platform with docs, APIs, CLI, and MCP server, but nothing indicates open-source availability of its core product source.
Coinbase Payments (CDP)none0/10Coinbase Payments (CDP) is a closed commercial API/SDK platform; there is a GitHub repo for client SDKs but no evidence of the core product/service source being available under an open license, and no license information is cited. Evidence only shows client library repos and docs, not the underlying platform source.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
Payouts offramp — stories about payouts offramp in this arenaPayouts offramp
Stories about payouts offramp in this arena
Batch
ops leadRun mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status
weight 2 · round drawnCirclenone0/10The evidence describes individual payout rails (CPN cross-border fiat payouts, Circle Mint USD/USDC conversion) but nowhere documents a batch or bulk payout API that processes many payouts in one call with per-item status tracking. Missing for 10: any mention of batch/bulk endpoint, multi-item payout request format, or per-item status/webhook reporting for mass disbursement runs.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
Coinbase Payments (CDP)none0/10Evidence confirms CDP supports sending fiat/crypto payouts from a custodial account and paying USDC onchain to any wallet, but nothing in the pack documents a batch or bulk payout API, a single-call multi-payee operation, or per-item status reporting for mass disbursements.
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Offramp
ops leadRecipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
weight 2 · round to Coinbase Payments (CDP)Circle's docs describe Cross-Chain Payments Network (CPN) enabling cross-border fiat payouts via partner network with real-time FX quotes and local fiat delivery, and Circle Mint for USD↔USDC conversion, matching the off-ramp story's core mechanism. However, no evidence lists a published set of specific supported currencies or countries, nor does it detail settlement timelines or bank-transfer specifics that an ops lead would need to plan payouts. Missing for 10: a published currency/country coverage list, settlement SLAs, and independent confirmation of real-world payout success.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
Docs confirm off-ramp functionality — converting stablecoins/USDC to fiat and depositing to bank accounts via ACH, Fedwire, Swift, and SEPA rails (docs-2, docs-14, docs-19) — implying multi-currency support (USD, EUR, GBP) across supported regions. However, no evidence provides a published, explicit list of supported currencies or countries, which the story specifically asks for. Missing for 10: an explicit published table/list of supported countries and currencies, and independent confirmation of real-world payout coverage.
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
Payouts
developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
weight 3 · round drawnCircle's docs show programmatic USDC transfers via Wallets APIs, cross-border fiat payouts through CPN with real-time FX quotes and onchain USDC settlement, and webhook-based state-change notifications that could serve as status tracking. However, there's no explicit documentation of a 'stored recipient' object/API or a full payout status lifecycle (e.g., enumerated states from initiated to settled), and no independent/hands-on corroboration of payout completion. Missing for 10: stored-recipient management API, explicit payout status enumeration/lifecycle docs, and third-party verification of end-to-end payout settlement.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
- [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”
Docs confirm programmatic stablecoin payouts to wallet addresses (fund a USD treasury and pay out USDC onchain to any wallet, or send payouts/disbursements in fiat or crypto from a custodial account) plus webhook-based status notifications for tracking events. However, there's no evidence of a 'stored recipient' concept, no detailed settlement-status API docs (e.g., payout lifecycle states), and no OpenAPI spec was found (probe-2 returned 404s) to confirm the full request/response tracking flow. Missing for 10: stored-recipient/beneficiary management, explicit payout status/settlement lifecycle documentation, and independent corroboration of end-to-end settlement tracking.
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnCirclenone0/10No evidence in the pack addresses data retention or deletion controls for AI-native users—no docs on data export, deletion policies, or retention settings; the community items concern reserve/treasury management, not data privacy.
Settlement treasury — stories about settlement treasury in this arenaSettlement treasury
Stories about settlement treasury in this arena
Settlement
finance leadSettlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume
weight 2 · round drawnCirclenone0/10Evidence shows Circle Mint conversion and CPN payouts exist, and webhooks notify on state changes, but there is no documented timing from payment to available balance, no published fee schedule per rail, and no mention of statements or accounting-consumable reports. The SVB/reserve community items are off-topic to settlement legibility and are excluded.
Coinbase Payments (CDP)none0/10Evidence covers payment rails, payouts, checkouts, and treasury flows, but there is no documented settlement-timing SLA per rail, no published fee schedule, and no mention of accounting-consumable statements or reports. The only 'settlement details' reference is a vague migration note with no actual content shown.
- [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
Treasury
finance leadMove value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
weight 2 · round to Coinbase Payments (CDP)Circle Mint lets qualified businesses convert USD to/from USDC (circle-docs-13), and CPN documents cross-border fiat payouts settled in USDC (circle-docs-12), showing fiat↔stablecoin movement is supported. However, evidence lacks concrete API reference detail or dashboard walkthrough for internal transfers/rebalancing as a documented end-to-end flow — missing for 10: explicit API endpoints/parameters for fiat-stablecoin conversion, dashboard UI documentation, and independent confirmation of the rebalancing workflow.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
CDP docs describe multiple building blocks for fiat↔stablecoin movement: auto-liquidation of onchain funds into a custodial account, fiat payouts via ACH/Fedwire/Swift/SEPA, converting crypto earnings to fiat, and treasury funding/payout flows (fund USD treasury, pay out USDC onchain) via CLI/SDK. This covers most of the 'rebalancing' story but is spread across separate features rather than a single documented end-to-end internal transfer/rebalancing workflow, and there is no dashboard evidence for these treasury operations (only API/CLI/SDK). Missing for 10: a unified internal transfer ledger view, dashboard-based rebalancing UI, and independent/hands-on confirmation of the full fiat↔stablecoin loop.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance
Stories about stablecoin acceptance in this arena
Acceptance
developerAccept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically
weight 3 · round to Coinbase Payments (CDP)Circle provides underlying primitives (wallets to receive USDC, webhooks to react to settlement state changes, CPN payout rails) that a developer could assemble into a payment acceptance flow, but the evidence pack shows no single documented 'create a payment / checkout' API object or flow analogous to a payment-intent API — CPN docs describe cross-border payout/self-managed lifecycle rather than a customer-facing checkout. Missing for 10: a dedicated payment/checkout creation endpoint, documented example of presenting an address+confirming settlement end-to-end, and independent confirmation this works in practice.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
Docs describe a full checkout/payment-acceptance flow: provisioning stable onchain addresses that auto-credit a custodial account, a two-step auth/capture checkout API with developer control over auth timing, partial captures and voids, plus migration guidance from the older Commerce Charge API to the newer Checkouts API with settlement details. This covers create-payment, present-address/flow, and confirm-settlement programmatically. Missing for 10: no independent/hands-on developer confirmation of the checkout flow working end-to-end, and no concrete code sample or OpenAPI spec (probe found openapi.json 404) showing the settlement confirmation call.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
- [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
- [claimed-docs] “You control auth, capture timing, partial captures, voids”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Chains
developerThe platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold
weight 2 · round drawnDocs confirm USDC (and EURC via CCTP) support and mention cross-chain transfers, but the evidence pack never lists specific named chains/networks or explicitly names USDT or other peer stablecoins as supported. missing for 10: an explicit supported-chains matrix, explicit USDT/other stablecoin support confirmation, and a consolidated asset-network compatibility table.
- [claimed-docs] “CCTP natively transfers USDC across blockchains using burn-and-mint, and extends to EURC and registered third-party assets... all without tr…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
Docs repeatedly reference USDC support (auto-convert customer USDC, USD treasury payouts in USDC, custom stablecoins backed by USDC) and mention EVM/Solana wallet support, but there is no explicit enumeration of USDT or other stablecoins, nor a clear list of supported chains/networks a developer could match against customer holdings. Missing for 10: explicit multi-stablecoin coverage (USDT, DAI, etc.), a documented list of supported blockchain networks, and any independent confirmation of chain/stablecoin breadth.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
Fiat settlement
finance leadTake crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto
weight 3 · round to Coinbase Payments (CDP)Circle documents both a direct USD↔USDC conversion mechanism (Circle Mint, at par, no fee) and a cross-border payments network (CPN) where partners deliver local fiat after USDC settlement, which together support a finance lead settling stablecoin receipts in fiat rather than holding crypto. However, there's no single documented 'auto-convert on receipt' checkout/payout feature purpose-built for merchants, and no independent confirmation of how seamlessly this flows into standard accounting so books never touch crypto. Missing for 10: an explicit automatic-conversion-on-payment-receipt feature, accounting/bookkeeping integration details, and independent/hands-on verification of the payout flow.
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
Docs explicitly describe auto-crediting custodial accounts with optional auto-liquidation, accepting USDC and auto-converting to USD into a treasury, and sending fiat payouts via ACH/Fedwire/Swift/SEPA — directly matching the finance-lead's request to settle crypto receipts in fiat and avoid holding crypto on the books. Missing for 10: independent/hands-on verification of the auto-liquidation flow in production, and clearer accounting/reconciliation documentation for finance teams.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access
Stories about stablecoin agent access in this arena
Agent payments
ai-native userAn agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured
weight 3 · round to CircleCircle documents Agent wallets explicitly built to 'hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails,' plus an agent-stack CLI and x402 pay-per-request flow that support agent-initiated payments under human-configured limits (circle-docs-6, circle-docs-7, circle-docs-8). However, the evidence lacks a concrete end-to-end documented example of an agent actually initiating a payout with a specific spend-control policy set by a human, or details on how those controls are configured/enforced. Missing for 10: a worked example/tutorial showing a human setting spend limits and an agent executing a constrained payment, independent/hands-on verification of the guardrails working in practice.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP documents agent-native payment flows: x402 lets agents pay for or charge APIs programmatically, and the Wallet MCP lets an AI assistant check balances, send funds and pay via a connected Coinbase Wallet, backed by CDP-managed key custody. However, the pack shows no explicit documentation of human-configured spend limits, allowances, or scoped permission policies constraining what an agent can autonomously spend — the closest control language ('you control auth, capture timing, partial captures, voids') applies to merchant checkout capture, not agent wallet spend caps. missing for 10: documented spend-limit/allowance configuration APIs, explicit human-set policy controls for agent wallets, and independent/hands-on confirmation of scoped-authority enforcement.
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
Agent wallets
ai-native userAgents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move
weight 2 · round to CircleCircle documents dedicated Agent wallets with spending controls and compliance guardrails, MPC/passkey key management (no raw private key handling), and an agent CLI/MCP stack for programmatic wallet use, which directly supports the story. However, evidence lacks specifics on scoped-key issuance granularity, concrete documented limits/spend caps, or independent/hands-on validation of policy enforcement in practice. missing for 10: detailed scoped-key/permission model docs, concrete numeric spend-limit examples, independent verification that policy controls hold up in real agent usage.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
CDP provides SDK-based wallet issuance where Coinbase secures private keys (coinbase-payments-gh-1) and exposes wallets to AI agents via MCP (coinbase-payments-docs-18) and x402 payments (coinbase-payments-docs-12/13), showing agents can hold and use funds programmatically. However, the evidence never documents scoped keys, granular policy controls, or explicit spend/limit enforcement mechanisms for agent-held wallets—only general custody and signing features. Missing for 10: explicit policy/permission engine docs, documented per-agent spend limits, and independent verification that agents cannot exceed defined bounds.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
Protocols
ai-native userThe platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration
weight 2 · round to Coinbase Payments (CDP)Circle explicitly documents x402 support ('Search x402-compatible APIs and pay per request, without subscriptions or API keys') as part of its Agent Stack, with SDK/CLI and MCP server tooling for agents to discover and pay for services. However, ACP, MPP, and AP2 are not mentioned anywhere in the evidence, and no dedicated x402 endpoint/OpenAPI spec is exposed (openapi probe 404s), leaving the protocol claim documented only at a feature-description level rather than full technical spec. Missing for 10: explicit ACP/MPP/AP2 support or endpoints, and a concrete x402 API reference/OpenAPI schema beyond prose description.
- [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
CDP has dedicated x402 docs with SDK/endpoints for both paying ("Pay for an API or resource with x402 and the CDP SDK") and charging ("Charge for your endpoints with x402 and the CDP SDK"), plus a Coinbase Wallet MCP server enabling agents to pay with x402, and an official CDP CLI/MCP exposing API endpoints as tools — this is concrete named-protocol support with SDKs/endpoints, not just aspirational blog content. Missing for 10: no explicit ACP/MPP/AP2 protocol mentions, so coverage is limited to x402 among the named protocols.
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance
Stories about stablecoin issuance in this arena
Issuance
founderIssue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly
weight 2 · round to Coinbase Payments (CDP)Circlenone0/10Evidence shows Circle Mint (converting USD↔existing USDC) and CPN (a self-managed model where the founder—not Circle—handles custody, payouts, and compliance for their own stablecoin lifecycle), but nothing documents a Circle-hosted white-label issuance product covering minting, redemption, and reserve management for a founder's own branded coin, nor any honest disclosure of eligibility gating for such a product.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
Coinbase's docs explicitly describe a custom-stablecoin issuance product ('Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves'), directly matching the story's core ask. However, the evidence pack contains no detail on eligibility/gating requirements, application process, minimum volume, or any independent corroboration of how the program actually works in practice. Missing for 10: honest disclosure of gating/eligibility requirements, independent/hands-on corroboration, and technical detail on minting/redemption mechanics beyond the single overview line.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
Yield
finance leadThe economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly
weight 2 · round drawnCirclenone0/10The evidence pack contains no documentation of USDC reserve composition, attestation reports, or any yield/rewards program with eligibility and regulatory caveats — the docs items only cover developer platform features (wallets, CCTP, agent stack, Circle Mint conversion). Community items discuss a 2023 SVB reserve incident but do not constitute or corroborate ongoing published reserve/attestation documentation.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [community] “Circle said $3.3bn of USDC's cash reserves remained with SVB and had initiated transfers before the bank failed, then argued the FDIC should…”
- [community] “Of USDC's ~23% cash reserves, roughly a third ($3.3bn of $9.7bn) was stuck at SVB while the rest was with other banks not facing the same is…”
Coinbase Payments (CDP)none0/10Evidence covers custom stablecoin issuance backed 1:1 by USDC with Coinbase managing issuance/redemption/reserves, but no documentation of reserve composition, attestations, or yield/rewards eligibility and regulatory caveats for finance leads is present.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
Wallets balances — stories about wallets balances in this arenaWallets balances
Stories about wallets balances in this arena
Balances
finance leadMy business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
weight 3 · round drawnCircle Mint is documented as a custodial USD↔USDC conversion account for 'qualified businesses' at no additional cost, which honestly signals gating, but the evidence never specifies which geographies are supported, what qualification criteria entail, or SLAs/availability guarantees. Missing for 10: stated geographic coverage, explicit eligibility/KYC requirements, and any independent or hands-on corroboration of account onboarding.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
Docs confirm custodial accounts that hold stablecoin balances (auto-credited addresses, auto-conversion to USD, treasury funding/payout in USDC) — docs-1, docs-19, docs-20 — but nothing in the evidence pack states availability constraints, supported geographies, or KYC/eligibility gating for opening such an account. Missing for 10: documented geographic availability/restrictions, explicit KYC/onboarding gating disclosure, and any stated balance limits or custody terms.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Virtual accounts
developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
weight 2 · round to Coinbase Payments (CDP)Circlenone0/10No evidence pack items describe named virtual accounts or dedicated per-customer deposit addresses for automated payment attribution/reconciliation; docs cover wallets, gas sponsorship, CCTP, webhooks, and payouts but nothing about per-customer deposit address issuance or account matching. Missing for 10: documentation of per-customer virtual account/deposit address creation, evidence of automatic incoming-payment-to-customer matching, and any reconciliation tooling tied to those addresses.
CDP docs explicitly describe provisioning 'stable onchain addresses' that auto-credit a custodial account (dedicated deposit addresses), and webhooks can watch up to 100 wallet addresses per subscription, which supports per-customer address-based reconciliation. However, there's no explicit documentation of named virtual accounts for fiat, nor clear guidance on mapping addresses to specific customer IDs for reconciliation workflows. Missing for 10: explicit per-customer/customer-ID tagging or named virtual account docs, fiat-side dedicated account numbers, and independent/hands-on confirmation of reconciliation accuracy at scale.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
Wallets
developerCreate wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
weight 2 · round to Coinbase Payments (CDP)Circle's docs confirm programmatic wallet creation with MPC/passkey-based key custody (no raw private key management for developers), and Agent wallets for per-purpose/per-customer use cases with spending controls, plus webhooks for wallet state changes. However, there's no direct documentation snippet showing explicit API endpoints for deposit address provisioning per customer, and the openapi/API reference spec itself is not accessible (404s), limiting verification of exact wallet-creation API semantics. Missing for 10: explicit API reference for wallet/deposit-address creation endpoints, clearer documentation of per-customer wallet architecture, and independent/hands-on corroboration of custody claims.
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
CDP SDK docs confirm programmatic wallet creation for EVM/Solana with CDP securing private keys, plus provisioning of custodial onchain deposit addresses that auto-credit accounts, and a sandbox for testing wallet features without real funds. However, the pack lacks explicit detail on per-customer/multi-tenant wallet architecture or deeper key-custody semantics beyond high-level statements. missing for 10: detailed per-customer wallet provisioning patterns, explicit key custody/security model documentation (MPC, backups, exportability)
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableCirclen/aCircle is a stablecoin/payments infrastructure platform (wallets, CCTP, CLI, agent-stack) that itself PUBLISHES an MCP server so external LLMs/IDEs can use Circle's tools — the reverse relationship. There is no evidence Circle functions as an agent runtime or host into which a user would plug external MCP servers for Circle to consume; this axis does not fit Circle's product category.
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
Coinbase Payments (CDP)n/aCoinbase Payments (CDP) is a payments/API infrastructure platform, not an AI agent or assistant that consumes external tools; the evidence shows it operates in the opposite direction — CDP exposes itself AS an MCP server (cdp mcp, Wallet MCP) for other AI agents to use its payment tools, not the reverse. The story asks whether this product can plug in and use others' MCP servers, which is a client/agent-role capability that doesn't fit a payments backend's category.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableCirclen/aCircle is a stablecoin/payments infrastructure and wallet platform, not a data analytics or insights product; the evidence covers wallets, CCTP, MCP for coding, and treasury/reserve issues, with nothing about generating AI insights or suggestions from a user's own data within the product. This axis is a category error for this type of product.
Coinbase Payments (CDP)n/aCoinbase Payments (CDP) is a payments/wallet infrastructure platform, not a data analytics or insights product; the evidence covers payment rails, MCP/AI-agent connectivity, and webhooks but nothing about surfacing AI-generated insights or suggestions from a user's own data inside the product. This story is a category error for this type of product.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC, CCTP, payments); it has no concept of user-authored 'automations' with version control, review, and rollback like a workflow/automation builder. This story targets a category of product Circle is not.
ai-native userExport all of my data in open formats and leave
weight 3 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC transfers, payments rails), not a data-storage or productivity product where 'exporting all my data in open formats and leaving' is a meaningful axis; there's no user data corpus to export in this sense.
ai-native userSelf-host the core product
weight 3 · not comparableCirclen/aCircle is a hosted infrastructure/API platform for stablecoins and wallets, not open-source software meant to be self-hosted; self-hosting the 'core product' is a category error for this type of managed financial service.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableCirclen/aCircle is a crypto/stablecoin infrastructure and agent-wallet platform, not a data-storage or hosting service; data residency/region choice is not an applicable axis for this product category, and no evidence pack content addresses storage location controls.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC, CCTP, payments); AI-model-training data usage controls are not a relevant axis for this product category, and no evidence pack content pertains to it.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableCirclen/aCircle is a stablecoin/blockchain infrastructure platform (wallets, USDC transfers, agent payment rails), not a developer tool or AI agent product with local telemetry collection; opting out of telemetry/usage tracking is not a relevant axis for this kind of product based on the evidence provided.