Coinbase Payments (CDP) vs MoonPay

Agent access

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

   weight 2 · round drawn
   Coinbase Payments (CDP)✓fullprobed9/10

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

   proof ↗⚑ flag

   MoonPay✓fullprobed9/10

   MoonPay has a confirmed llms.txt (probe returned HTTP 200 with descriptive content) and dedicated docs on using AI agents, including an official MCP server for searching/retrieving docs. missing for 10: independent third-party confirmation of agent usage beyond MoonPay's own docs/probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://dev.moonpay.com/llms.txt # MoonPay Developer Docs > Integrate MoonPay's on-ramp, off-ramp, and swap pro…”
   • [claimed-docs] “Let new customers buy crypto with Apple Pay or Google Pay without a MoonPay account.”
   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialprobed6/10

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

   proof ↗⚑ flag

   MoonPay~partialclaimed4/10

   MoonPay offers headless APIs/SDKs (build-your-own on-ramp, quote and session endpoints) and a dedicated test mode with testnets/simulated payments that could be scripted in a CI pipeline, but there is no evidence of a CLI, automation-first tooling, or documentation describing running MoonPay flows unattended in CI. Missing for 10: explicit CI/automation guidance, evidence of non-interactive KYC/payment flows, and independent confirmation of headless test-mode usage in pipelines.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ flag

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

   weight 3 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed8/10

   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”

   proof ↗⚑ flag

   MoonPay✓fullprobed7/10

   MoonPay documents an official MCP server for its developer docs that gives AI agents direct access to search and retrieve content, corroborated by a probe confirming the page exists. Missing for 10: independent hands-on verification of the MCP server actually working with an agent, and details on scope/capabilities beyond docs search/retrieval.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed8/10

   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”

   proof ↗⚑ flag

   MoonPay—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

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

   weight 3 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed8/10

   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”

   proof ↗⚑ flag

   MoonPay~partialprobed7/10

   MoonPay publishes detailed API reference docs (quotes, sessions, webhooks, test mode) letting developers programmatically drive on/off-ramp flows, and even documents an MCP server for AI agents to browse docs. However, a probe for standard machine-readable API specs (OpenAPI/Swagger) returned 404s across all candidate paths, suggesting no formal machine-consumable spec exists, which limits fully autonomous/agentic API discovery. missing for 10: a discoverable OpenAPI/Swagger spec, independent/hands-on confirmation that an AI agent can successfully call the API end-to-end.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

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

   ⚑ flag

   MoonPay—none0/10

   Evidence shows API keys and session tokens for general integration (moonpay-docs-15) and a documentation MCP server for search/retrieval (moonpay-docs-6), but nothing about issuing scoped or least-privilege credentials specifically for AI agents acting on a user's behalf. No permissions model, credential scoping, or agent-specific access controls are documented.

   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed8/10

   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”

   proof ↗⚑ flag

   MoonPay~partialprobed5/10

   MoonPay's docs explicitly mention building on 'APIs and SDKs' (moonpay-docs-3) and provide a demo integrations repo (moonpay-docs-7) and API reference endpoints (moonpay-docs-14, moonpay-docs-15), indicating some SDK/dev-tooling support. However, there's no direct evidence of language-specific SDK packages, an OpenAPI spec (probe shows 404s for standard OpenAPI paths, moonpay-probe-2), or independent developer corroboration of SDK quality/coverage. Missing for 10: concrete SDK package listings (npm, PyPI, etc.), OpenAPI/spec-driven tooling, and independent hands-on confirmation of SDK usability.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullclaimed8/10

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

   proof ↗⚑ flag

   MoonPay✓fullclaimed7/10

   MoonPay documents webhook events that notify applications of account activity, with specific examples like sell_transaction_requote_required, giving developers a concrete subscription mechanism for events. This directly satisfies the story's core need for event-driven notifications. Missing for 10: a full list/catalog of all webhook event types, subscription management API/UI documentation, and independent third-party confirmation of webhook reliability.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed6/10

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

   proof ↗⚑ flag

   MoonPay—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

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

   weight 3 · round drawn
   Coinbase Payments (CDP)—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

   MoonPay—none0/10

   MoonPay's evidence only describes an MCP server that lets external AI agents search/retrieve documentation content (moonpay-docs-6, moonpay-probe-3) — this is a developer-docs tool, not a built-in AI assistant inside the product that end-users can delegate purchase/sell/swap tasks to. No evidence of any in-product assistant, chat interface, or agentic task delegation for users.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialprobed6/10

   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”

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's evidence only shows an MCP server for searching/retrieving documentation content, not for operating the actual on-ramp/off-ramp transactions via natural language; there is no evidence of a chat/agent interface that lets a user issue commands like 'buy $50 of ETH' through natural language.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to MoonPay
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay~partialprobed4/10

   MoonPay's dev docs include structured API reference pages (e.g., quotes/get, sessions/create) and a separate GitHub repo of clone-able demo integrations, but there's no evidence of an interactive, in-browser 'try it now' console — a probe for standard OpenAPI/swagger endpoints returned 404s, suggesting no exposed spec powering live runnable examples. Missing for 10: in-docs interactive request builder/console, publicly exposed OpenAPI spec, and confirmation that example code snippets are directly executable from the reference pages.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   No evidence of a downloadable OpenAPI/Swagger spec; a direct probe of common OpenAPI paths (openapi.json, swagger.json, etc.) returned 404 across the board, and docs only mention API reference pages and an MCP server for agent content retrieval, not a machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ flag

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

   weight 1 · round to MoonPay
   Coinbase Payments (CDP)~partialclaimed6/10

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

   proof ↗⚑ flag

   MoonPay✓fullclaimed7/10

   MoonPay explicitly documents a test mode using testnet blockchains and simulated payments so no real assets are transferred, directly matching the sandbox story, and this is reinforced by clone-able demo integrations for testing before production use. Missing for 10: independent/hands-on confirmation that the sandbox fully mirrors production behavior and more detail on how test-mode credentials/environments are provisioned.

   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; openapi spec probe 404s, and no changelog/versioning page is cited. missing for 10: versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.

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

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed3/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   No evidence of bulk/batch operations across many items (e.g., batch quotes, bulk transaction processing) in MoonPay's API or docs; endpoints shown are single-item (single quote, single session).

   ⚑ flag

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

   weight 3 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay~partialclaimed4/10

   MoonPay exposes webhook events (e.g., transaction status, requote-required) that notify an application when activity occurs, which developers can use to build their own automated actions, but there is no evidence of a built-in rules/automation engine where users define conditional triggers within MoonPay itself. missing for 10: a native rule-builder or automation configuration UI/API, evidence of conditional logic or multi-step workflows tied to events, independent confirmation of automation use in production.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

   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 MoonPay
   Coinbase Payments (CDP)—none0/10

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

   ⚑ flag

   MoonPay~partialprobed5/10

   MoonPay's docs describe KYC as a built-in, hosted part of its on-/off-ramp widget and API flow (session creation, quotes, webhooks) and note that returning users can skip re-onboarding, but there is no documented standalone KYC/KYB endpoint or explicit 'counterparty cleared' status API that an ops team could call programmatically before initiating a transfer — KYC is embedded in the transaction flow rather than exposed as an independent compliance-check service. missing for 10: explicit KYC/KYB API/endpoint documentation, a way to query verification/clearance status independent of a transaction, and any B2B/KYB (business) onboarding flow.

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Connect existing MoonPay usersSkip re-onboarding. Plug into the existing MoonPay account base.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   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
   Coinbase Payments (CDP)—none0/10

   No evidence pack item discloses the specific licensed/registered legal entities behind Coinbase Payments products or the jurisdictions/licenses they operate under; all evidence is product/API documentation with no legal-entity or licensing disclosure page cited.

   ⚑ flag

   MoonPay—none0/10

   No evidence pack item names MoonPay's licensed/registered legal entities, regulatory licenses, or jurisdictional coverage; documentation is entirely product/API focused, and community items concern fee transparency and an unrelated scam-fund allegation, not entity/licensing disclosure.

   ⚑ 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 drawn
   Coinbase Payments (CDP)—none0/10

   The evidence pack lists payment, wallet, onramp, and MCP features but never names sanctions screening, wallet risk scoring, or travel-rule handling as documented compliance machinery; these terms simply do not appear anywhere in the pack.

   ⚑ flag

   MoonPay—none0/10

   MoonPay's docs mention generic 'KYC and compliance' and 'payments' but never name specific machinery like sanctions screening, wallet risk scoring, or travel-rule data sharing — the exact named-not-waved-at requirement of this story. Missing for 10: any documentation naming sanctions/OFAC screening process, wallet address risk-scoring methodology, or travel-rule protocol implementation (e.g., Notabene/Sygna/TRISA integration).

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”

   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 drawn
   Coinbase Payments (CDP)~partialprobed6/10

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

   proof ↗⚑ flag

   MoonPay~partialprobed6/10

   MoonPay's docs show a conventional REST API (quotes, sessions, webhooks) and widgets/SDKs that abstract on-chain mechanics like fees and rate-locking, letting developers build fiat-to-crypto flows without running nodes (moonpay-docs-3, moonpay-docs-14, moonpay-docs-15, moonpay-docs-11). However, there's no evidence of concrete multi-language client libraries or a public OpenAPI spec (probe found 404s at all candidate spec URLs), so the 'client libraries in my language' part of the story is unsupported. Missing for 10: enumerated SDK languages/repos, published OpenAPI/swagger spec, independent confirmation of ease-of-use across languages.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   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 to MoonPay
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay✓fullclaimed7/10

   MoonPay documents a dedicated test mode using testnet blockchains and simulated payments where no real assets are transferred, directly matching the sandbox/testnet rehearsal story for buy/sell/conversion flows. Missing for 10: explicit documentation of deterministic test values (e.g., specific test card numbers or fixed exchange rates) and independent/hands-on confirmation that payouts and conversions behave predictably in test mode.

   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   proof ↗⚑ 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 drawn
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay~partialclaimed5/10

   MoonPay docs confirm a webhook system that notifies apps of account activity and give an example event (sell_transaction_requote_required), supporting event-driven state tracking. However, there is no evidence of cryptographic signing/verification of webhooks, nor documentation of specific 'payment confirmed', 'payout settled', or 'conversion executed' event types the story describes. missing for 10: signature verification details, full enumerated list of transaction lifecycle events (buy/sell/swap completion, payout settlement), independent confirmation of webhook reliability.

   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”

   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 MoonPay
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay~partialclaimed6/10

   MoonPay documents a Quotes endpoint returning locked rate, fees, and a signature for fiat-to-crypto buys, plus off-ramp requote webhooks for sell price changes, giving developers programmatic access to rates/fees for fiat↔stablecoin conversion. However, stablecoin-to-stablecoin 'swap' conversion is only mentioned as a marketing feature (docs-18) without a documented quotes/fees API for that path, and no settlement-time documentation appears anywhere in the pack. missing for 10: documented quote/fee API for stablecoin-to-stablecoin swaps, explicit settlement-time guarantees, independent confirmation of rate accuracy.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
   • [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”

   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 drawn
   Coinbase Payments (CDP)✓fullclaimed8/10

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

   proof ↗⚑ flag

   MoonPay✓fullclaimed8/10

   MoonPay documents a widget and API/SDK approach for embedding fiat-to-stablecoin (and crypto) onramp flows, supporting card, Apple Pay, Google Pay and bank transfers, with customization, prefill, webhooks, quotes and session tokens, plus test mode for development. missing for 10: no independent/hands-on developer corroboration of the integration experience, and no explicit confirmation of stablecoin-specific (vs generic crypto) purchase support in the widget docs.

   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “You can customize the widget to feel like a native part of your site or application by adjusting button and background colors. You can also …”
   • [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”

   proof ↗⚑ flag

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

   weight 2 · round to Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed8/10

   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”

   proof ↗⚑ flag

   MoonPay~partialprobed6/10

   MoonPay documents a full build-your-own API/SDK path (quotes, sessions, webhooks, prefill, wallet creation, requote handling) that mirrors much of what the hosted widget UI offers, suggesting broad but not explicitly total parity. However, no OpenAPI/swagger spec was found (404s on all probed paths), and there's no explicit documentation stating 100% feature parity between API and UI, with a community question even asking if the API/webhook list is public at all. Missing for 10: explicit statement of full UI/API parity, a published OpenAPI spec, and independent developer confirmation that all UI features are API-accessible.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
   • [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
   • [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Coinbase Payments (CDP)—none0/10

   No evidence of data export/portability features or account-closure/data-takeout tooling in open formats; evidence covers payments, wallets, MCP/CLI integration but nothing about exporting user data or leaving the platform with it.

   ⚑ flag

   MoonPay—none0/10

   MoonPay stores user KYC and transaction data (moonpay-docs-20) but the evidence pack contains no mention of any data export feature, open-format download, or account portability/deletion tooling for end users.

   ⚑ 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
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's docs describe single-transaction on-ramp/off-ramp flows (quotes, sessions, webhooks) for individual end-user purchases/sells, but there is no evidence of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”

   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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed6/10

   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”

   proof ↗⚑ flag

   MoonPay~partialclaimed5/10

   MoonPay documents off-ramp (sell) rails paying out to bank account or card, with build-your-own or hosted options and sell-specific webhooks (requote), showing the payout mechanism exists and is documented for developers. However, there is no evidence of a published, itemized list of supported fiat currencies or countries for the off-ramp, which the story specifically requires. Missing for 10: published currency/country coverage table for off-ramp, independent confirmation of payout rails working across those markets.

   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”

   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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialprobed6/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's docs describe on-ramp/off-ramp widgets and APIs for individual users buying/selling crypto (quotes, sessions, webhooks for sell/requote), but there is no evidence of a payouts API that lets a developer programmatically disburse stablecoins to a wallet address or stored recipient list with settlement status tracking — that is a distinct payouts/disbursement capability not shown in the pack.

   • [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

   No evidence in the pack mentions data residency, regional storage options, or data locality controls for Coinbase Payments/CDP; the docs focus entirely on payment rails, wallets, and AI-agent commerce features.

   ⚑ flag

   MoonPay—none0/10

   No evidence in the pack addresses data residency, regional data storage options, or user/developer control over where data is stored; MoonPay's docs cover payment/KYC integration but never mention data locality choices.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

   No evidence pack items address data retention policies, data deletion controls, or privacy/data-lifecycle settings for AI-native users; all documentation covers payments, wallets, and MCP/CLI integration rather than data governance.

   ⚑ flag

   MoonPay—none0/10

   No evidence pack content addresses data retention policies, user data deletion requests, or privacy controls for AI-native users; docs focus on payments, KYC integration, and widget customization. Missing for 10: any documentation of data retention policy, user-initiated deletion/erasure mechanism, or privacy control API/settings.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Coinbase Payments (CDP)—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for CDP Payments; the documentation covers payment features, wallets, and AI/MCP integration but is silent on data collection controls.

   ⚑ flag

   MoonPay—none0/10

   No evidence of any telemetry/usage-tracking opt-out mechanism or privacy controls for AI-native users; documentation covers payments, KYC, and integration features only.

   ⚑ 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
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   The evidence pack shows webhooks, quotes with locked rates/fees, and test mode, but nothing documents settlement timing (payment to available balance), a published fee schedule per rail, or accounting-consumable statements/reports. A community comment even asks whether MoonPay's fee structure/API is publicly available, suggesting no clear published fee documentation exists. Missing for 10: settlement timing documentation, per-rail fee schedules, downloadable statements/reports for accounting.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”

   proof ↗⚑ 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 to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed6/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's documented capabilities are consumer-facing on-ramp/off-ramp/swap widgets and APIs (buy, sell, quote, webhooks) for end users converting fiat to crypto and back — there is no evidence of an internal treasury/balance system, account-to-account transfers, or rebalancing API/dashboard aimed at a finance lead managing platform-held fiat and stablecoin balances. Missing for 10: any documentation of internal ledger/balance accounts, transfer-between-balances API, or treasury dashboard for rebalancing fiat vs stablecoin holdings.

   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”

   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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed7/10

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

   proof ↗⚑ flag

   MoonPay—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

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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed4/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   The evidence pack shows general on-ramp/off-ramp and cross-chain swap capabilities but contains no documentation listing specific supported stablecoins (USDC, USDT, etc.) or named blockchain networks. Missing for 10: an explicit supported-assets/networks list, stablecoin-specific documentation, and named chain coverage.

   ⚑ 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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullclaimed8/10

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

   proof ↗⚑ flag

   MoonPay~partialclaimed4/10

   MoonPay's off-ramp product (docs-17, docs-3) lets crypto be converted to cash paid to a bank account or card, and this can be built into a business's own flow via APIs/webhooks (docs-11, docs-14). However, this is framed as a consumer/end-user cash-out feature, not a documented merchant treasury/settlement product for automatically converting incoming stablecoin payments into a fiat balance so a business's books never hold crypto. Missing for 10: explicit merchant/business settlement documentation, stablecoin-specific auto-conversion mechanics, fiat balance/ledger concept, and accounting-oriented guarantees that crypto is never held.

   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
   • [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”

   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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's MCP server (moonpay-docs-6, moonpay-probe-3) only gives agents access to search/retrieve documentation content, not to initiate payments. There is no evidence of an agent payment flow with human-configured spend controls, scoped authority, or delegated transaction limits — the API docs describe quotes/sessions for human-driven checkout flows, not autonomous agent-initiated payouts.

   • [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
   • [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
   • [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
   • [claimed-docs] “Create a session token to initialize a connection”

   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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed5/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   Evidence covers MoonPay's on/off-ramp widget, API, and MCP docs-server for content retrieval, but there is no mention of programmatic wallet issuance for AI agents, scoped API keys, policy controls, or documented spend limits governing what an agent can move. The comm-1 item is off-topic (fraud allegation, not agent wallet controls) and ignored.

   ⚑ 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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)✓fullprobed9/10

   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”

   proof ↗⚑ flag

   MoonPay—none0/10

   Evidence shows MoonPay has an MCP server for docs search and standard fiat on/off-ramp APIs, but no mention of named machine-payment protocols like x402, ACP, MPP, or AP2 anywhere in the docs, endpoints, or SDKs.

   ⚑ 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 to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed6/10

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

   proof ↗⚑ flag

   MoonPay—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

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
   Coinbase Payments (CDP)—none0/10

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

   proof ↗⚑ flag

   MoonPay—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

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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed4/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   Evidence describes MoonPay purely as an on-ramp/off-ramp/swap payment rail (buy/sell/bridge crypto, webhooks, quotes, session tokens) with no documented custodial account product for holding a business stablecoin balance, nor any stated availability, geography, or gating for such a balance. This is a plausible axis for a crypto payments platform to address, but no supporting evidence exists.

   • [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
   • [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
   • [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
   • [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”

   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 to Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed6/10

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

   proof ↗⚑ flag

   MoonPay—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

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 Coinbase Payments (CDP)
   Coinbase Payments (CDP)~partialclaimed7/10

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

   proof ↗⚑ flag

   MoonPay—none0/10

   MoonPay's docs mention it can auto-create a wallet for users via email during the on-ramp purchase flow, but this is a widget-embedded convenience feature, not a documented developer API for programmatically provisioning per-customer/purpose wallets or deposit addresses, and there is no documentation of key custody semantics.

   • [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”

   proof ↗⚑ flag