Stripe Crypto & Stablecoins vs Circle

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Stripe's docs.stripe.com exposes an llms.txt file (HTTP 200) and per-page .md agent-readable docs (e.g. crypto.md, stablecoin-payments.md, machine.md), confirmed by direct probes, so an agent can be pointed at llms.txt or markdown docs directly. Missing for 10: no independent/community confirmation of an agent actually consuming llms.txt successfully, and no dedicated agent-oriented documentation index beyond the generic llms.txt.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”

   proof ↗⚑ flag

   Circle✓fullprobed8/10

   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”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe provides a documented CLI (stripe-cli) and API-based integration for crypto/stablecoin payments, which enables headless/automated/CI usage of the broader Stripe platform, and a machine-payment protocol (x402) suited for agentic/automated payment flows. However, there's no crypto-specific evidence of CI/test-mode tooling, fixtures, or automation examples tailored to the crypto product beyond generic docs. Missing for 10: crypto-specific CI/test examples, sandbox/test-mode automation docs, and independent confirmation of headless workflows for stablecoin features.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Circle~partialprobed6/10

   Circle 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.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Circle
   Stripe Crypto & Stablecoins✓fullprobed6/10

   Stripe publishes an official MCP server (docs.stripe.com/mcp) that lets AI agents connect to Stripe capabilities, and Stripe itself is a service/platform (not an agent), so the axis applies and is satisfied. missing for 10: no detail on which crypto/stablecoin tools are exposed via MCP, no independent/hands-on corroboration of the MCP server's functionality.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Circle✓fullprobed8/10

   Circle 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”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins✓fullprobed7/10

   Stripe documents an official CLI (stripe-cli) as part of its platform, which applies to the Crypto & Stablecoins product since it's built on the same Stripe API/tooling. missing for 10: X, Y - no crypto-specific CLI command examples, no independent/hands-on confirmation of CLI use for crypto endpoints.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Circle✓fullprobed8/10

   Circle 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”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Circle
   Stripe Crypto & Stablecoins~partialprobed6/10

   Stripe Crypto is part of the broader Stripe API/platform, which is documented and programmatically drivable (docs.stripe.com, CLI, MCP server referenced), and x402 protocol support suggests machine-native payment flows. However, the evidence pack lacks crypto-specific API reference/OpenAPI spec (openapi probe returned 404s) or SDK examples for driving crypto/stablecoin features specifically via API. missing for 10: crypto-specific API reference or OpenAPI schema, explicit SDK/code examples for stablecoin endpoints, independent confirmation of agentic/API-driven crypto workflows beyond x402 mention.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Circle✓fullprobed8/10

   Circle'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”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Circle~partialclaimed4/10

   Circle'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…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe's crypto/stablecoin docs are exposed as machine-readable markdown, an llms.txt index, an official CLI, and a documented MCP server, suggesting the crypto APIs are reachable via Stripe's standard official SDKs, but the evidence never explicitly names or links official language SDKs (e.g., stripe-node/python/ruby) covering crypto/stablecoin endpoints. Missing for 10: explicit SDK documentation/examples for crypto features, independent corroboration of SDK usage in agentic/AI workflows, and confirmation the OpenAPI spec (needed for SDK generation) is accessible (probe found it 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”

   proof ↗⚑ flag

   Circle—none0/10

   Evidence 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…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment features, onramp, payouts, financial accounts, and even x402 protocol support, but contains no mention of webhooks or event subscription mechanisms for the crypto/stablecoin product. Webhooks are a plausible and expected capability for a payments API, so the axis applies, but no evidence supports it here.

   ⚑ flag

   Circle✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment features (onramp, payouts, financial accounts) but contains no mention of automation setup, scheduling, workflows, or autonomous background agent execution tied to this product. missing for 10: any evidence of automation/workflow builder, scheduling or triggers, autonomous agent execution, or background task orchestration.

   ⚑ flag

   Circle~partialprobed5/10

   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”

   proof ↗⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Circle—none0/10

   Circle 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…”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe documents an official MCP server (docs.stripe.com/mcp) that would let AI agents/LLMs invoke Stripe functionality via natural-language-driven tool calls, and the crypto/stablecoin docs describe machine-native payment support over the x402 protocol for agentic/automated transactions. However, there is no direct evidence of a natural-language command interface specifically for the crypto/stablecoin product surface (onramp, financial accounts, payouts), and no hands-on confirmation of AI-native operation. Missing for 10: crypto-specific natural-language command examples, hands-on/independent verification of MCP or x402 usage for stablecoin flows, and documentation tying the MCP server to crypto-specific actions.

   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Circle~partialprobed5/10

   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”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence shows Stripe docs, an llms.txt file, and a CLI/MCP server, but there is no mention of an interactive API reference with runnable examples (e.g., API explorer, try-it console). OpenAPI probe returned 404s, and no docs cite an interactive playground for crypto/stablecoin endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Circle—none0/10

   Circle'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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack explicitly shows a probe that checked common OpenAPI spec locations (openapi.json, swagger.json, etc.) and all returned 404, and no other citation confirms a downloadable machine-readable API spec for Stripe Crypto & Stablecoins. Only llms.txt and markdown docs are shown as available, not a structured OpenAPI/JSON schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”

   proof ↗⚑ flag

   Circle—none0/10

   The 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…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack for Stripe Crypto & Stablecoins covers wallets, onramp, payouts, refunds, and cards, but nowhere mentions a test/sandbox mode or non-production environment for crypto/stablecoin flows. Since sandbox testing is a plausible and expected capability for an API-based payments product, its absence here is a gap rather than an inapplicable axis.

   ⚑ flag

   Circle—none0/10

   The 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.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence in the pack discusses API versioning practices or a documented deprecation policy for Stripe's crypto/stablecoin APIs; the OpenAPI probe even returned 404s. missing for 10: any mention of API version headers, changelog, or deprecation policy documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Circle—none0/10

   No 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…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence of bulk/batch operations across many items (e.g., batch payouts, bulk API calls, batch job endpoints) for the crypto/stablecoin product; docs describe single-transaction flows (onramp, payouts, refunds).

   ⚑ flag

   Circle—none0/10

   The 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”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Circle
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack covers crypto/stablecoin payment rails, onramp, payouts, and financial accounts, but contains no mention of user-definable event-triggered rules or automation/workflow logic. Webhooks or event-based automation are not referenced anywhere in the pack. missing for 10: rule-definition mechanism, event-trigger automation framework, evidence of conditional action execution.

   ⚑ flag

   Circle~partialclaimed5/10

   Circle 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.”

   proof ↗⚑ flag

Kyc

1. 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 to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialcommunity3/10

   Stripe states it internally handles KYC verifications and sanctions screening for onramp transactions, and community evidence shows recipient-type restrictions (individuals/sole proprietors only) implying some vetting occurs — but there are no documented KYC/KYB endpoints, verification statuses, or flows that an ops lead can programmatically invoke to clear a counterparty before sending/receiving. missing for 10: documented KYC/KYB API endpoints, verification status objects, or ops-controllable onboarding flow for senders/recipients.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Circle—none0/10

   Evidence 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…”

   proof ↗⚑ flag

Licensing

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence pack item discloses which licensed/registered legal entities operate Stripe's crypto/stablecoin products or lists jurisdictional coverage of those entities; docs describe features and networks, not corporate/regulatory entity structure. Community threads even highlight regulatory murkiness ('the regulatory details are complex') without clarifying entity/jurisdiction transparency.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [community] “Stripe employee: 'Until very recently, we weren't able to support businesses selling crypto. (The regulatory details are complex.) We're now…”

   proof ↗⚑ flag

   Circle—none0/10

   The 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.

   ⚑ flag

Screening

1. ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at

   weight 2 · round to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Docs mention Stripe handles 'regulatory requirements, KYC verifications, and sanctions screening' for onramp transactions (stripe-crypto-docs-15), but this is a single generic line, not a detailed compliance framework. There is no mention of wallet risk-scoring/checks or travel-rule handling anywhere in the pack. Missing for 10: named wallet risk-check mechanism, travel-rule compliance documentation, detail on sanctions screening process/providers.

   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”

   proof ↗⚑ flag

   Circle—none0/10

   The 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.”

   proof ↗⚑ flag

Abstraction

1. 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 Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialprobed6/10

   Stripe's crypto/stablecoin docs present a conventional REST-style API (via standard Stripe API, Financial Accounts, onramp, x402) abstracting settlement, custody, and payouts without requiring developers to run nodes or manage gas directly, and Stripe's general SDKs cover multiple languages. However, the evidence pack doesn't explicitly confirm crypto-specific client libraries or SDK coverage for these crypto endpoints, and community comments raise confusion over how crypto payouts/checkout actually work in practice. missing for 10: explicit confirmation of crypto-specific client library support across languages, clearer docs on gas/chain abstraction mechanics, and independent developer confirmation that no chain-level operations leak into the integration.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Authorize recurring stablecoin withdrawals from your customers’ crypto wallets.”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Circle~partialprobed5/10

   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…”

   proof ↗⚑ flag

Sandbox

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   No evidence pack item mentions a sandbox, testnet, or deterministic test values for crypto/stablecoin payments, payouts, or conversions; Stripe's general test-mode is not documented here for this crypto product. Missing for 10: documented testnet/sandbox mode, test API keys or test wallet addresses for crypto flows, deterministic test value behavior for payments/payouts/conversions.

   ⚑ flag

   Circle—none0/10

   No 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.

   ⚑ flag

Webhooks

1. developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards

   weight 2 · round to Circle
   Stripe Crypto & Stablecoins—none0/10

   The evidence pack documents Stripe Crypto's onramp, stablecoin payments, financial accounts, and payouts, but contains no mention of webhooks, event types, or signed notifications for crypto-specific state changes (payment confirmed, payout settled, conversion executed). Since this is an applicable axis for a payments platform but no supporting evidence exists in the pack, it must be judged 'none' rather than 'na'.

   ⚑ flag

   Circle~partialclaimed5/10

   Circle'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.”

   proof ↗⚑ flag

Conversion

1. 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 to Circle
   Stripe Crypto & Stablecoins~partialclaimed4/10

   Stripe offers onramp (fiat-to-crypto) and stablecoin payments/payouts, but there is no documented quote/conversion-rate API exposing exchange rates, fees, or settlement times for conversions between fiat and stablecoins or between stablecoins — pricing and rate details are absent from the evidence pack. missing for 10: a dedicated conversion/quote endpoint, documented FX rate and fee schedule for stablecoin conversions, documented settlement-time SLAs, and stablecoin-to-stablecoin conversion support.

   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”

   proof ↗⚑ flag

   Circle~partialprobed5/10

   Circle 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…”

   proof ↗⚑ flag

Onramp

1. 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 Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins✓fullclaimed8/10

   Stripe documents a fiat-to-crypto onramp with hosted, embedded (web), and embedded components (mobile SDK) options for buying stablecoins via cards/bank transfers, with Stripe as merchant of record handling KYC/fraud (stripe-crypto-docs-11 through 15). This directly matches the story of a documented widget/API for in-product onramp embedding. Missing for 10: independent hands-on developer confirmation of the embedded widget integration experience and no code-sample evidence in the pack.

   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [claimed-docs] “Stripe acts as the merchant of record for these onramp transactions and assumes full liability for all fraud and disputes. We also handle al…”

   proof ↗⚑ flag

   Circle—none0/10

   Evidence 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…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Stripe Crypto & Stablecoins~partialprobed5/10

   Stripe's crypto/stablecoin docs describe everything as API/SDK-driven integrations (Payment Intents, Financial Accounts, onramp embedded/API components, payouts), suggesting an API-first design typical of Stripe, but the evidence never explicitly confirms that every UI-exposed action (e.g., wallet linking in the Express Dashboard, card issuance flows) has a documented equivalent API call, nor is there any AI-agent-specific tooling cited beyond the general Stripe MCP/CLI probes which aren't crypto-specific. missing for 10: explicit statement or example that all Dashboard/Express UI crypto actions map 1:1 to API endpoints, and independent verification of full API/UI parity for this specific crypto product.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”
   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Circle~partialprobed5/10

   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”

   proof ↗⚑ flag

Batch

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence shows Stripe can pay out stablecoins to individual connected accounts and issue cards, but there is no documentation of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.

   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “Issue virtual or physical prepaid cards for connected accounts, backed by stablecoin balances.”

   proof ↗⚑ flag

   Circle—none0/10

   The 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.”

   proof ↗⚑ flag

Offramp

1. 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 Circle
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Docs describe crypto payments settling as fiat in the merchant's Stripe balance and stablecoin payouts to connected accounts/financial accounts, but there is no documented dedicated 'off-ramp' feature converting stablecoin balances into bank transfers with a published list of supported currencies/countries — in fact docs note stablecoin balances exist precisely in markets where fiat Treasury isn't available, implying no guaranteed bank conversion there. Missing for 10: explicit off-ramp/conversion mechanism from stablecoin to bank transfer, a published country/currency coverage list, and independent confirmation it works as described.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”

   proof ↗⚑ flag

   Circle~partialclaimed5/10

   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.”

   proof ↗⚑ flag

Payouts

1. developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement

   weight 3 · round to Circle
   Stripe Crypto & Stablecoins~partialcommunity5/10

   Stripe documents stablecoin payouts to connected accounts (platforms/marketplaces) and wallet-linking via Express Dashboard, implying an API-driven payout path, but the evidence never shows a generic 'pay any wallet address or stored recipient' API call, nor documented status-tracking fields through to final settlement. Community reports also note real constraints (recipients must be individuals/sole proprietors, confusion about payout flow), and a Connect-only payout model is narrower than the story's general wallet-payout claim. Missing for 10: explicit API reference/status object for tracking payout progress to settlement, confirmation that arbitrary external wallet addresses (not just linked connected accounts) can be paid, and resolution of community confusion about how payouts actually work.

   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”
   • [community] “Confusion over Stripe Crypto Payouts: 'Can you checkout with USDC? ... Then I can pay myself out with USD or USDC? I feel like I have this w…”

   proof ↗⚑ flag

   Circle~partialclaimed6/10

   Circle'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.”

   proof ↗⚑ flag

Settlement

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   Docs confirm crypto payments settle as fiat into the Stripe balance and mention refunds support, but there is no evidence of documented settlement timing (e.g., T+n days), no published fee schedule per rail/network, and no mention of statements or accounting-ready reports for crypto/stablecoin transactions.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”

   proof ↗⚑ flag

   Circle—none0/10

   Evidence 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.

   ⚑ flag

Treasury

1. 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 drawn
   Stripe Crypto & Stablecoins~partialclaimed5/10

   Stripe documents stablecoin Financial Accounts that let businesses hold, receive, and send stablecoin balances alongside fiat Treasury, plus card issuance backed by those balances, but there is no explicit documentation of a finance-lead-facing internal transfer/rebalancing flow moving value between fiat and stablecoin balances via API or dashboard — the onramp/payout docs are customer- or payout-facing, not treasury rebalancing tools. missing for 10: dedicated API/dashboard endpoint or flow for converting/rebalancing between fiat and stablecoin balances, end-to-end docs for finance-lead treasury operations, independent confirmation of this workflow.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “Create a virtual or physical card to spend funds”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Pay out in stablecoins to connected accounts from platforms and marketplaces.”

   proof ↗⚑ flag

   Circle~partialclaimed5/10

   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…”

   proof ↗⚑ flag

Acceptance

1. 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 Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins✓fullclaimed7/10

   Stripe documents a stablecoin payments API supporting USDC/USDP/USDG across multiple networks, with refunds/partial refunds, checkout/onramp flows (hosted, embedded, mobile SDK), and even machine-to-machine stablecoin payments via x402 — covering the create-payment-present-flow-confirm-settlement lifecycle described in the story. Missing for 10: explicit code-level API reference (e.g., PaymentIntent creation with stablecoin payment method, webhook/settlement confirmation snippet) and independent hands-on developer confirmation that programmatic settlement works as documented.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”
   • [claimed-docs] “The Stripe fiat-to-crypto onramp lets your customers securely purchase and exchange cryptocurrencies directly from your platform or decentra…”
   • [claimed-docs] “Use the Stripe-hosted onramp to redirect your customer to check out in the standalone page.”
   • [claimed-docs] “Use the Embedded onramp to let your customers check out directly in your website.”
   • [claimed-docs] “Use the Embedded components onramp (mobile SDK) to let your customers check out directly in your application.”
   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Circle~partialclaimed4/10

   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”

   proof ↗⚑ flag

Chains

1. 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 to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Docs explicitly enumerate supported stablecoins (USDC, USDP, USDG) and specific chains per coin (Tempo, Ethereum, Solana, Polygon, Base), letting developers match customer holdings to supported networks. Community commentary raises ethical/centralization concerns about Solana but does not dispute the accuracy of the documented coverage. Missing for 10: independent verification of full USDT support (not mentioned in evidence) and confirmation the list is exhaustive/up to date.

   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Circle~partialprobed4/10

   Docs 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…”

   proof ↗⚑ flag

Fiat settlement

1. 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 Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins✓fullprobed8/10

   Stripe's documented crypto product explicitly states customers can pay with crypto that settles as fiat in the merchant's Stripe balance, directly matching the finance-lead need to accept stablecoins without holding crypto on the books, and this is backed by first-party docs on stablecoin payments, refunds, and settlement mechanics. missing for 10: no independent/hands-on accounting confirmation that settlement is always fiat-only (vs. optional stablecoin balance retention), and no explicit mention of bank payout timing/documentation for finance reconciliation.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Refunds / Partial refunds [Yes / Yes](https://docs.stripe.com/payments/stablecoin-payments.md#refunds)”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/crypto.md # Stripe Crypto Integrate one of the Stripe crypto products. ## Build crypto …”

   proof ↗⚑ flag

   Circle~partialclaimed6/10

   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…”

   proof ↗⚑ flag

Agent payments

1. 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 Circle
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Stripe documents machine/agent stablecoin payments via the x402 protocol (docs-16, docs-17) and recurring stablecoin withdrawal authorization (docs-4), showing some agent-payment-adjacent capability, but there is no documentation of a human configuring spend controls/limits that scope an agent's authority to move funds. missing for 10: explicit spend-control/authorization-limit configuration by a human, documented agent payout workflow with scoped permissions, and any hands-on or third-party confirmation of this flow working.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [claimed-docs] “Authorize recurring stablecoin withdrawals from your customers’ crypto wallets.”

   proof ↗⚑ flag

   Circle~partialprobed6/10

   Circle 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”

   proof ↗⚑ flag

Agent wallets

1. 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 Circle
   Stripe Crypto & Stablecoins~partialclaimed3/10

   Stripe documents stablecoin financial accounts, cards, and support for the x402 machine-payment protocol, hinting at agent/programmatic payment flows, but there is no documentation of agent-specific wallet issuance, scoped API keys, policy controls, or explicit spend limits for autonomous agents. missing for 10: agent-scoped key issuance, policy/permission controls, documented spend limits for agents, independent corroboration of agentic wallet safety.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”

   proof ↗⚑ flag

   Circle~partialprobed6/10

   Circle 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”

   proof ↗⚑ flag

Protocols

1. 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 Circle
   Stripe Crypto & Stablecoins~partialclaimed6/10

   Stripe docs explicitly name and document x402 protocol support for stablecoin payments, including a technical detail (0.01 USDC minimum), which goes beyond blog-level aspiration. However, there is no documented support for ACP, MPP, or AP2 protocols in the evidence pack, so the 'speaks the machine-payment protocols by name' story is only partially fulfilled. Missing for 10: ACP support/endpoints, MPP support/endpoints, AP2 support/endpoints, and independent corroboration of x402 usage in production.

   • [claimed-docs] “Stripe also supports stablecoin payments over the x402 protocol.”
   • [claimed-docs] “For stablecoin payments, the minimum amount is 0.01 USDC.”

   proof ↗⚑ flag

   Circle~partialprobed7/10

   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…”

   proof ↗⚑ flag

Issuance

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   Stripe's crypto offerings cover payments, onramp, payouts, and stablecoin financial accounts — but there is no evidence of a stablecoin issuance product (minting a branded coin, redemption mechanics, reserve management/attestation). This is a distinct product category (e.g., Bridge/Paxos-style issuance-as-a-service) that Stripe's evidence pack never mentions.

   ⚑ flag

   Circle—none0/10

   Evidence 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.”

   proof ↗⚑ flag

Yield

1. 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 drawn
   Stripe Crypto & Stablecoins—none0/10

   Evidence covers stablecoin payment/payout mechanics and financial account features but contains no documentation of reserve composition, attestations, or a yield/rewards program with eligibility and regulatory caveats for held stablecoin balances.

   ⚑ flag

   Circle—none0/10

   The 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…”

   proof ↗⚑ flag

Balances

1. 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 to Stripe Crypto & Stablecoins
   Stripe Crypto & Stablecoins~partialcommunity6/10

   Stripe's docs describe Stablecoin Financial Accounts letting eligible businesses hold a stablecoin balance, with explicit gating language ('eligible businesses', 'countries where it's available') and honest disclosure that it's not universally available, plus card issuance against the balance. However, the docs do not enumerate the specific list of supported geographies/countries, and community evidence shows historical exclusion of crypto businesses and confusion over payout mechanics, suggesting real-world gating is stricter/less transparent than the docs alone convey. missing for 10: an explicit published list of eligible countries/geographies, independent confirmation of account availability, and clarity on gating criteria beyond 'eligible businesses'.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “Create a virtual or physical card to spend funds”
   • [community] “Just last year Stripe wouldn't even allow any crypto business to be their customers. You could not use Stripe if your business was crypto re…”
   • [community] “Stripe employee: 'Until very recently, we weren't able to support businesses selling crypto. (The regulatory details are complex.) We're now…”
   • [community] “Recipients paid in crypto must be individuals or sole proprietors. Paying companies and non-profits in crypto is not currently supported. 'O…”

   proof ↗⚑ flag

   Circle~partialclaimed4/10

   Circle 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.”

   proof ↗⚑ flag

Virtual accounts

1. developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching

   weight 2 · round drawn
   Stripe Crypto & Stablecoins—none0/10

   The evidence describes Stripe's crypto payment acceptance, onramp, stablecoin financial accounts, and payouts, but nowhere mentions per-customer dedicated deposit addresses or named virtual accounts for automatic reconciliation of incoming crypto/stablecoin payments. Payments appear tied to Stripe's standard Checkout/PaymentIntent flow rather than unique wallet addresses per customer.

   • [claimed-docs] “Let your customers pay with crypto that settles as fiat in your Stripe balance.”
   • [claimed-docs] “USDC (Tempo, Ethereum, Solana, Polygon, and Base networks), USDP (Ethereum and Solana, US-only), USDG (Ethereum, US-only)”
   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”

   proof ↗⚑ flag

   Circle—none0/10

   No 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.

   ⚑ flag

Wallets

1. 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 Circle
   Stripe Crypto & Stablecoins—none0/10

   Evidence covers stablecoin payments, onramp, financial accounts, and payouts to connected accounts, but there is no documented API for programmatically creating per-customer or per-purpose wallets/deposit addresses with custody semantics; wallet linking is described as user-driven (Express Dashboard) not developer-provisioned.

   • [claimed-docs] “Receive, store, and send funds globally with stablecoins in your Stripe Financial Account.”
   • [claimed-docs] “Eligible businesses can hold a stablecoin balance in the countries where it’s available, including markets where fiat Treasury isn’t availab…”
   • [claimed-docs] “After a user links a crypto wallet in the Express Dashboard, they immediately see a new USDC balance on their connected account.”

   proof ↗⚑ flag

   Circle~partialprobed6/10

   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…”

   proof ↗⚑ flag