Coinbase Payments (CDP) vs Paxos

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

   Paxos✓fullprobed9/10

   Paxos hosts an llms.txt at docs.paxos.com/llms.txt, confirmed live by a direct probe returning HTTP 200 with structured documentation links, and the docs also advertise AI-assistance built into the documentation for contextual help. missing for 10: independent third-party confirmation of an agent successfully consuming the llms.txt beyond the first-party probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.paxos.com/llms.txt # Paxos Documentation - [Build with Paxos](https://docs.paxos.com/welcome.md): …”
   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Paxos~partialclaimed6/10

   Paxos is API-first with client credentials, auth tokens, and a Sandbox environment explicitly designed for automated end-to-end integration testing (faucets, mock flows, transfers), which supports headless/CI-style automation. However, there is no explicit mention of CI/CD pipeline examples, SDKs, or automation tooling tailored for AI-native/headless workflows. Missing for 10: explicit CI/CD integration guides, official SDK/CLI support for headless automation, and independent confirmation of running in CI.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   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

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

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

   Paxos—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 drawn
   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

   Paxos✓fullprobed8/10

   Paxos provides extensive documented public APIs covering authentication (Client ID/Secret, tokens), sandbox testing, identity onboarding, payments, conversions, crypto brokerage (REST v2.0, FIX, WebSocket), and webhooks — clearly enabling programmatic/agentic control of the platform. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe found only 404s) and evidence of official SDKs, which would strengthen AI-native automation.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [claimed-docs] “Leverage the Paxos FIX API to trade crypto.”
   • [claimed-docs] “Stream order book updates and executions in real time using the Smart Order Routing WebSocket API”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.paxos.com/llms.txt # Paxos Documentation - [Build with Paxos](https://docs.paxos.com/welcome.md): …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round to Paxos
   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

   Paxos~partialclaimed5/10

   Paxos supports API credentials (Client ID/Secret) with configurable allowed scopes to restrict access to specific endpoints, which supports least-privilege credential issuance [paxos-docs-2]. However, there is no explicit documentation of an 'agent' use case, dynamic/programmatic credential issuance for AI agents, or fine-grained per-action scoping beyond endpoint-level access. Missing for 10: agent-specific credential provisioning workflow, evidence of granular per-resource scopes beyond endpoint-level, and independent/hands-on confirmation of scope enforcement.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”

   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

   Paxos—none0/10

   The evidence pack details Paxos's REST/FIX/WebSocket APIs, sandbox, webhooks, and docs, but never mentions official client SDKs or libraries in any language; the openapi.json probe also 404s, suggesting no even machine-readable spec is exposed for SDK generation.

   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [claimed-docs] “Leverage the Paxos FIX API to trade crypto.”
   • [claimed-docs] “Stream order book updates and executions in real time using the Smart Order Routing WebSocket API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos✓fullclaimed7/10

   Paxos documents a dedicated Webhooks feature allowing registration of endpoints to receive asynchronous platform events, with configurable event types, auth, and RPS via the Dashboard. Missing for 10: independent/hands-on corroboration of webhook reliability, payload schema examples, and no OpenAPI spec confirming event types programmatically.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

   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

   Paxos—none0/10

   Paxos evidence covers APIs, webhooks, orchestrations (mint/redeem) and sandbox testing, but none of it describes a mechanism for setting up automations or agents that run autonomously in the background (e.g., scheduling, workflow triggers executed by Paxos itself, or an automation builder). Webhooks are reactive event notifications requiring external systems to act, not autonomous background execution.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   proof ↗⚑ flag

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

   weight 3 · round to Paxos
   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

   Paxos~partialclaimed3/10

   Paxos docs mention only a documentation-embedded AI assistant for contextual API help (paxos-docs-18), not a built-in assistant capable of executing platform tasks like payments, conversions, or identity onboarding on the user's behalf. Missing for 10: evidence of an in-product AI agent that can perform actions (transfers, KYC, order execution) rather than just answer doc questions, and any first-party or independent confirmation of agentic task delegation.

   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”

   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

   Paxos—none0/10

   Paxos is a financial/stablecoin API platform with developer docs, REST/FIX APIs, and an AI-assisted docs search helper, but there is no evidence of natural-language command operation of the product itself (e.g., no chat-driven transaction execution or NL-to-API interface). The 'AI assistance built into our documentation' (paxos-docs-18) is a doc-search helper, not a way to operate the product via NL commands.

   ⚑ flag

Api quality

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

   weight 2 · round drawn
   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

   Paxos—none0/10

   The evidence pack shows Paxos has a Sandbox environment, docs with AI assistance, and various API guides, but nothing describing an interactive API reference (e.g., Swagger/OpenAPI explorer or 'try it' console) with runnable code examples; the probe for standard OpenAPI spec paths returned 404 across all checked locations, reinforcing the absence of such a feature.

   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [claimed-docs] “Get contextual help with Paxos APIs using AI assistance built into our documentation.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   Direct probing of common OpenAPI/Swagger paths returned 404s, and the docs pack contains no link to a downloadable machine-readable spec despite extensive API documentation.

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

   proof ↗⚑ flag

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

   weight 1 · round to Paxos
   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

   Paxos✓fullclaimed8/10

   Paxos provides a dedicated Sandbox environment with signup, credentials, test crypto asset faucets, and explicit guidance to mock flows, execute transfers, and test integrations without touching production data. missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on data isolation guarantees between sandbox and production.

   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   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

   Paxos—none0/10

   Evidence only shows a passing reference to 'Paxos API v2.0' (paxos-docs-19) with no changelog, versioning scheme, or deprecation/sunset policy documented anywhere in the pack; the OpenAPI/spec probes also returned 404s, suggesting no discoverable machine-readable API version metadata either.

   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   The evidence pack shows individual API operations (single mint/redeem, single identity creation, single transfers) but no batch or bulk endpoints for processing many items in one call. Bulk operations across many items are a fair ask for a financial API platform, but no documentation mentions batch processing, bulk uploads, or multi-item transactions.

   ⚑ 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

   Paxos~partialclaimed4/10

   Paxos offers webhooks that push asynchronous platform events to a user-defined endpoint (paxos-docs-16, paxos-docs-17), which lets a developer build custom automation externally, but there's no evidence of a built-in rules/automation engine where actions are defined and triggered directly within Paxos itself. Missing for 10: native rule-definition UI/API, conditional action triggers, and any AI-native automation tooling beyond raw webhook events.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

   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 Paxos
   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

   Paxos✓fullprobed7/10

   Paxos docs explicitly describe programmatic KYC/KYB flows: creating a person identity and handling onboarding decisions, creating an institution identity with required members and onboarding decisions, and collecting/transmitting beneficiary info for above-threshold transfers — directly matching counterparty clearance before money moves. missing for 10: X, Y — no visible OpenAPI/endpoint spec (openapi probe 404) and no independent/hands-on corroboration of these onboarding APIs.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   The evidence pack is entirely API/developer documentation about sandbox, onboarding, payments, and webhooks; none of it addresses the legal/regulatory entities behind Paxos, their licensing status, or jurisdictional coverage. No trust/compliance/licensing page, entity disclosure, or regulatory registration info is cited anywhere.

   ⚑ 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 Paxos
   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

   Paxos~partialclaimed4/10

   Travel-rule handling is explicitly documented ('Collect and transmit beneficiary information for above-threshold crypto transfers') and identity onboarding decisions are named, but sanctions screening and wallet risk checks are never named as distinct compliance mechanisms — only vague 'onboarding decision' language. missing for 10: explicit sanctions screening documentation, explicit wallet/address risk-scoring documentation, and independent corroboration of these compliance mechanisms.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”

   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

   Paxos~partialprobed6/10

   Docs show Paxos exposes stablecoin mint/redeem, transfers, and conversions via REST-style orchestration endpoints with sandbox/auth, effectively hiding chain mechanics and gas from developers (paxos-docs-8, paxos-docs-9, paxos-docs-10, paxos-docs-22). However, there's no mention of official client libraries/SDKs in specific languages, and the probe found no discoverable OpenAPI spec, so the 'client libraries in my language' part of the story is unevidenced. missing for 10: language-specific SDKs/client libraries, published OpenAPI/swagger spec, independent confirmation of no direct chain exposure.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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 Paxos
   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

   Paxos~partialclaimed6/10

   Docs confirm a dedicated Sandbox environment with test credentials, faucets for test crypto assets, and ability to 'mock flows, execute transfers and test integrations' (paxos-docs-1,4,22), which covers the general intent of rehearsing without real funds. However, there is no explicit documentation tying the sandbox to deterministic test values, nor confirmation that payouts/conversions (mint/redeem orchestrations) are specifically testable in sandbox mode rather than just payments. Missing for 10: explicit deterministic test-value behavior, sandbox coverage confirmation for conversions/payouts orchestrations, and independent/hands-on corroboration.

   • [claimed-docs] “Sign Up for access to the Sandbox environment.”
   • [claimed-docs] “Source test crypto assets from faucets and deposit them into your Sandbox account for end-to-end integration testing.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   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 to Paxos
   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

   Paxos~partialclaimed6/10

   Docs confirm Paxos Webhooks deliver asynchronous events for platform activity (configurable endpoint, event types, auth type of API Key or OAuth) which covers state tracking without polling, but there is no explicit mention of cryptographic signing/signature verification for webhook payloads, nor specific event-type names like 'payment confirmed' or 'payout settled'. Missing for 10: explicit payload-signing/signature-verification mechanism, and confirmation of exact event types matching payment/payout/conversion lifecycle.

   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”

   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 Paxos
   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

   Paxos~partialclaimed6/10

   Paxos documents concrete conversion orchestrations (USD→stablecoin mint, stablecoin→USD redeem, and 'execute conversions between supported assets') plus held-rate quote execution in its crypto-brokerage API, showing conversion is a first-class, callable API surface. However, the evidence pack lacks explicit documentation of fee schedules or settlement-time SLAs tied to these conversion endpoints. missing for 10: documented fee tables/rate-spread disclosure, explicit settlement-time guarantees, and confirmation that quote/held-rate functionality extends to fiat↔stablecoin (not just crypto-brokerage trading pairs).

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”

   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 Coinbase Payments (CDP)
   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

   Paxos~partialclaimed5/10

   Paxos provides APIs to convert USD to stablecoins and back (mint/redeem orchestrations) and identity onboarding flows, which are the backend building blocks for a fiat-to-stablecoin onramp, but the evidence describes a backend API/orchestration platform rather than a documented pre-built embeddable widget or turnkey onramp UI for end users to buy stablecoins via card/bank transfer. missing for 10: an explicit end-user-facing widget/UI component, card payment support (evidence only shows wire/CUBIX bank transfers, not card rails), and independent confirmation of a ready-to-embed onramp product.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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

   Paxos~partialprobed6/10

   Paxos exposes a broad API surface (identity onboarding, transfers, conversions, payments, brokerage, webhooks) that mirrors most Dashboard functionality, suggesting strong API/UI parity for core workflows. However, evidence explicitly notes account/user management ('manage your platform and users') is documented as a Dashboard-only guide, webhook configuration is described as done via Dashboard login rather than API, and no OpenAPI spec was discoverable to verify full API coverage. missing for 10: confirmed API equivalents for Dashboard-only admin/user-management tasks, API-based webhook configuration, discoverable OpenAPI/swagger spec proving full endpoint parity, independent verification beyond vendor docs.

   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [claimed-docs] “Learn how to use the Paxos Dashboard to manage your platform and users.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”

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

   Paxos—none0/10

   Evidence shows single-operation APIs (mint, redeem, convert, transfer) and payment acceptance flows, but nothing describing a batch/bulk payout endpoint that processes many payouts in one call with per-item status reporting. missing for 10: batch/bulk disbursement endpoint docs, per-item status/response schema, evidence of multi-recipient payout support.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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

   Paxos~partialclaimed5/10

   Paxos documents converting stablecoins to USD and settling directly to a bank account (redeem, settle-to-bank, auto-convert-to-fiat), which covers the core off-ramp-to-bank-transfer mechanic, but all evidence is USD/wire-transfer specific with no published list of supported fiat currencies or countries for payouts. missing for 10: published multi-currency/country coverage list, evidence of non-USD bank rails, independent confirmation of international payout reach.

   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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 drawn
   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

   Paxos~partialprobed6/10

   Paxos docs show programmatic stablecoin transfer/conversion orchestrations (mint/redeem, asset transfers), beneficiary/recipient handling for crypto transfers, and webhooks for asynchronous event tracking that could support payout status monitoring. However, there is no explicit documentation of a dedicated 'pay to wallet address or stored recipient' payout endpoint with full status-to-settlement tracking, and the OpenAPI spec probe failed (404), limiting confirmation of endpoint-level detail. Missing for 10: explicit payout-to-wallet/stored-recipient API reference, confirmed OpenAPI schema, and independent/hands-on verification of settlement status tracking.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Collect and transmit beneficiary information for above-threshold crypto transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Get market data, create orders, execute held-rate quotes, and transfer assets with Paxos API v2.0.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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

   Paxos—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geographic data controls for Paxos; the docs focus on API onboarding, payments, and trading flows only.

   ⚑ 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

   Paxos—none0/10

   Paxos is a financial/stablecoin platform whose documentation covers identity onboarding, payments, brokerage, and webhooks, but there is no mention of data retention policies, user-controlled deletion, or export/erasure mechanisms for an AI-native user.

   ⚑ 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

   Paxos—none0/10

   Docs describe settlement mechanics (mint/redeem orchestrations, wire transfer/CUBIX, direct bank settlement) but nowhere document payment-to-available-balance timing, publish a fee schedule per rail, or provide statements/reports formatted for accounting consumption.

   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Settle USD directly to your bank account.”

   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 Paxos
   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

   Paxos✓fullclaimed7/10

   Paxos docs describe end-to-end orchestrations for converting USD↔stablecoins in one API call (mint/redeem), moving USD on/off platform via wire/CUBIX, and general conversions between supported assets, plus a Dashboard for platform management, giving a finance lead both API and dashboard paths for treasury operations. Missing for 10: explicit dashboard UI screenshots/steps for initiating a fiat/stablecoin transfer or rebalancing (dashboard docs are generic), and independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Learn how to use the Paxos Dashboard to manage your platform and users.”
   • [claimed-docs] “Use the Sandbox environment to mock flows, execute transfers and test integrations.”

   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 drawn
   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

   Paxos✓fullprobed7/10

   Paxos has a dedicated Payments API documented to accept PYUSD/USDC/USDP on-chain transfers, auto-convert to fiat or hold in stablecoin, settle to bank, issue refunds, and receive async settlement confirmation via webhooks — covering create/present/confirm end-to-end. Missing for 10: no independent hands-on developer integration report, no OpenAPI spec exposed (404s), and no explicit example of presenting a checkout address/UI flow to an end customer.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Issue refunds to the original Buyer via stablecoin on-chain transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”
   • [claimed-docs] “Log in to your Dashboard account and navigate to the Webhooks section under the Developer tab. Configure your webhook with the relevant name…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.paxos.com/openapi.json, https://docs.paxos.com/swagger.json, https://docs.paxos.com/api…”

   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 Paxos
   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

   Paxos~partialclaimed5/10

   Docs explicitly list supported stablecoins for payments (PYUSD, USDC, USDP) and mention conversions between 'supported assets,' showing some named-coin documentation, but USDT is not mentioned anywhere, and no specific blockchain networks (e.g., Ethereum, Solana) are named in the evidence pack. missing for 10: USDT support, explicit multi-chain network list, and a consolidated supported-assets/chains reference page.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Execute conversions between supported assets.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   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 drawn
   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

   Paxos✓fullclaimed8/10

   Docs explicitly describe accepting PYUSD/USDC/USDP payments with an option to automatically convert stablecoin to fiat or settle USD directly to a bank account, matching the finance-lead's no-crypto-on-books requirement, plus a redeem orchestration to convert stablecoins to USD and withdraw to bank in one call. Missing for 10: independent/hands-on confirmation of the auto-convert toggle in production and clearer accounting/reporting detail on how converted balances appear in books.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Settle USD directly to your bank account.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”

   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

   Paxos—none0/10

   Evidence shows generic API credentialing with scopes (paxos-docs-2) and various payment/transfer/orchestration endpoints, but nothing documents an agent-specific payment flow, delegated spend limits, or scoped authority configured by a human for an autonomous agent to initiate stablecoin payments. Missing for 10: any mention of AI agents, agent-specific spend controls, or delegated payment authority workflows.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   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

   Paxos—none0/10

   Paxos docs show API credentials with configurable scopes (paxos-docs-2), sandbox testing, and identity onboarding, but there is no evidence of agent-specific wallet issuance, scoped keys tied to autonomous agents, or documented spending/policy limits governing what an agent can move.

   • [claimed-docs] “API credentials using Client ID and Secret. Set allowed scopes to access specific API endpoints.”
   • [claimed-docs] “Generate an authentication token.”
   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”

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

   Paxos—none0/10

   No evidence names or documents x402, ACP, MPP, or AP2 protocols; Paxos documentation covers stablecoin issuance, payments, brokerage, and webhooks but never references these specific machine-payment protocols by name with 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

   Paxos—none0/10

   The evidence pack shows Paxos APIs for minting/redeeming existing stablecoins (mint.md, redeem.md) and payment flows, but nothing documenting a distinct 'issue your own branded stablecoin' program, its reserve-management practices, or the eligibility/gating requirements (e.g., minimum volume, regulatory vetting) stated honestly. Missing for 10: dedicated issuance-product docs, reserve/attestation disclosure, and explicit gating/eligibility criteria for founders wanting a new branded coin.

   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

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

   Paxos—none0/10

   The evidence pack covers API/developer documentation for minting, redeeming, payments, and sandbox testing, but contains no mention of reserve composition, attestation reports, or any yield/rewards program with eligibility or regulatory caveats for held stablecoins.

   ⚑ 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 Paxos
   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

   Paxos~partialclaimed5/10

   Docs describe custodial-style flows (person/institution identity onboarding, USD-to-stablecoin conversion, holding balances, wire/CUBIX movement) implying an account structure for holding stablecoin balances, but nowhere do they state specific geographies served, eligibility/gating criteria, or availability constraints as the story requires. Missing for 10: explicit geographic availability list, stated eligibility/gating (e.g., institutional-only, jurisdictional restrictions), and independent confirmation of custodial account terms.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Convert USD to Stablecoins and transfer all in one call.”
   • [claimed-docs] “Convert stablecoins to USD and withdraw to your bank in one call.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”

   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

   Paxos—none0/10

   Paxos docs describe payment acceptance (PYUSD/USDC/USDP on-chain transfers), auto-conversion to fiat, and webhooks for event notifications, but nowhere mention per-customer virtual accounts or dedicated deposit addresses for automatic reconciliation of incoming funds. missing for 10: any documentation of per-customer/dedicated deposit addresses or virtual account assignment, reconciliation tooling tying incoming transfers to specific customers.

   • [claimed-docs] “Accept PYUSD, USDC and USDP payments via on-chain transfers.”
   • [claimed-docs] “Automatically convert the stablecoin to fiat, or opt to hold balances in stablecoin.”
   • [claimed-docs] “Issue refunds to the original Buyer via stablecoin on-chain transfers.”
   • [claimed-docs] “Paxos Webhooks allow you to register your own endpoints to receive asynchronous events driven by the Paxos Platform.”

   proof ↗⚑ 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

   Paxos—none0/10

   The evidence pack covers identity onboarding, fiat/crypto conversions, payments, webhooks, and brokerage trading, but contains no mention of programmatic wallet creation, per-customer deposit address provisioning, or documented custody/key-management semantics. Missing for 10: wallet/deposit-address creation API docs, custody model documentation, evidence of per-customer wallet provisioning.

   • [claimed-docs] “Create a person identity and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Create an institution identity with required members and handle the onboarding decision on the Paxos Platform.”
   • [claimed-docs] “Move USD on and off the Paxos Platform via wire transfer or CUBIX.”

   proof ↗⚑ flag