Circle vs Paxos

Agent access

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

   weight 2 · round to Paxos
   Circle✓fullprobed8/10

   Circle publishes a live llms.txt at developers.circle.com/llms.txt (HTTP 200, confirmed by probe) and also has an official MCP server for agent-oriented coding assistance, showing explicit support for agent-native discovery of docs. Missing for 10: independent/community corroboration of agents actually using llms.txt in practice, and no OpenAPI spec discoverable to complement it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”

   proof ↗⚑ flag

   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
   Circle~partialprobed6/10

   Circle provides a CLI (circle-cli) and REST APIs for wallets, transfers, and webhooks that can be scripted programmatically, which supports headless/automated use in principle, but there is no explicit documentation of CI pipelines, service-account/API-key based non-interactive auth, or example CI workflows. missing for 10: explicit CI/headless setup guide, service-account authentication flow, and independent evidence of running the CLI/API in automated pipelines.

   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”

   proof ↗⚑ flag

   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 Circle
   Circle✓fullprobed8/10

   Circle documents an official MCP server that integrates with LLMs/AI-assisted IDEs to generate and fix code using Circle's Wallets, Contracts, CCTP, and Gateway offerings, confirmed by both docs and a direct probe of the live URL. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and more detail on setup/config beyond the doc description.

   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”

   proof ↗⚑ flag

   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 Circle
   Circle✓fullprobed8/10

   Circle documents an official CLI (circle-cli) explicitly built for agentic workflows—creating/managing wallets, transferring/swapping/bridging USDC, executing smart contracts, and discovering/paying for services 'through a single command interface,' confirmed via docs and a probe. Missing for 10: independent/hands-on verification of the CLI's real-world usage or community adoption beyond first-party docs.

   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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
   Circle✓fullprobed8/10

   Circle's developer platform (developers.circle.com) documents extensive public APIs covering wallets, CCTP cross-chain transfers, webhooks for event-driven integration, and a CLI/MCP server that wrap the same API, all confirmed live via llms.txt probe and doc excerpts. This clearly supports AI-native users driving the product programmatically. Missing for 10: a directly reachable OpenAPI/swagger spec (probe returned 404 on all standard paths) and independent third-party confirmation of API usability.

   • [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”
   • [claimed-docs] “Let users pay gas fees with USDC instead of native tokens using Circle's permissionless ERC-4337 paymaster contracts.”
   • [claimed-docs] “CCTP natively transfers USDC across blockchains using burn-and-mint, and extends to EURC and registered third-party assets... all without tr…”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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
   Circle~partialclaimed4/10

   Circle's Agent Stack docs mention 'Agent wallets... with customizable spending controls and built-in compliance guardrails' (circle-docs-6), which implies some least-privilege control over what an agent can spend, but there is no documentation of scoped API keys, permission tiers, or credential issuance specifically for API access. Missing for 10: explicit API key/token scoping mechanism, documented permission levels for agent credentials, and any independent verification of these controls in practice.

   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”

   proof ↗⚑ flag

   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 drawn
   Circle—none0/10

   Evidence describes Circle's APIs, CLI, MCP server, and webhooks, but no item mentions official language SDKs (e.g., Node/Python/Java client libraries) for building against Circle's platform; the OpenAPI spec probe even returned 404s, suggesting no evidence of SDK generation or distribution.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”

   proof ↗⚑ flag

   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 drawn
   Circle✓fullclaimed7/10

   Circle documents webhooks that POST to a configured endpoint when resource state changes, enabling event-driven/agentic reactions to platform events. Missing for 10: details on event/topic subscription management, payload schema/signature verification docs, and independent/hands-on confirmation of reliability.

   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”

   proof ↗⚑ flag

   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 Circle
   Circle~partialprobed5/10

   Circle offers building blocks for autonomous background behavior—webhooks that react to state changes, CCTP triggers for automated actions after cross-chain transfers, and Agent wallets with spending controls—but there's no explicit documentation of a scheduler, persistent background job runner, or end-to-end 'set up and forget' automation workflow. Missing for 10: dedicated automation/scheduling API or dashboard, evidence of long-running autonomous agent execution, and independent confirmation these triggers work reliably in production.

   • [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”

   proof ↗⚑ flag

   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
   Circle—none0/10

   Circle documents an 'Agent Stack' (agent wallets, x402 payments, CLI, MCP server) for building AI agents that consume Circle's crypto rails, but this is infrastructure for third-party agents to interact with Circle—not a built-in AI assistant inside Circle's own product that a user can delegate tasks to.

   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”

   proof ↗⚑ flag

   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 Circle
   Circle~partialprobed5/10

   Circle offers an official MCP server (circle-docs-9, circle-probe-3) that lets LLMs/AI-IDEs interact with Circle's wallet/CCTP/contract APIs, and an 'agent-stack' with agent wallets and a CLI for programmatic control (circle-docs-6, circle-docs-8), suggesting some natural-language/agent-driven operability. However the MCP server is scoped to code generation/fixing rather than live natural-language command execution of transactions, and the CLI is explicitly a structured command interface, not NL-based. Missing for 10: evidence of an actual chat/NL interface for executing live operations (transfers, swaps) rather than just code generation, and independent confirmation of NL command usage in production.

   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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
   Circle—none0/10

   Circle's developer docs are markdown-based (llms.txt) and reference APIs, but there's no evidence of an interactive API reference with runnable examples; probes for OpenAPI/Swagger specs that would power such a reference all returned 404.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   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
   Circle—none0/10

   The probe explicitly checked common OpenAPI spec paths (openapi.json, swagger.json, etc.) and all returned 404, indicating no downloadable machine-readable API spec is available, despite Circle having extensive API documentation. missing for 10: an actual OpenAPI/Swagger spec file accessible at a discoverable URL.

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

   proof ↗⚑ flag

   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
   Circle—none0/10

   The evidence pack contains no mention of a sandbox/testnet environment, test API keys, or any way to develop against non-production data; all docs describe production wallet, CCTP, CLI, and MCP features without noting a separate test mode. Missing for 10: any mention of sandbox/testnet endpoints, test credentials, or documentation distinguishing sandbox vs production usage.

   ⚑ flag

   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
   Circle—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the openapi.json/swagger probes all 404, and no docs mention version numbers or deprecation timelines. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog or migration guide.

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

   proof ↗⚑ flag

   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 drawn
   Circle—none0/10

   The evidence describes individual operations (wallet creation, single transfers, CCTP transfers, webhooks) via API/CLI/MCP, but no documentation mentions batch or bulk endpoints, bulk payout processing, or multi-item operations in one call. Missing for 10: batch API endpoints, bulk transfer/payout documentation, any bulk wallet or bulk transaction management feature.

   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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 Circle
   Circle~partialclaimed5/10

   Circle supports event-driven automation via webhooks that POST to your endpoint on state changes, CCTP's ability to trigger actions on the destination chain after assets arrive, and Agent wallets with customizable spending controls/policies — but these are developer-configured integrations, not a user-facing rules engine for defining arbitrary if/then automation. Missing for 10: a dedicated no-code/low-code rules builder, conditional logic across multiple event types, and evidence of AI-native users authoring rules themselves rather than developers wiring webhooks/paymaster policies.

   • [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”

   proof ↗⚑ flag

   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
   Circle—none0/10

   Evidence covers wallets, gas sponsorship, CCTP, agent wallets, CLI/MCP, and Circle Mint onboarding, but nowhere documents KYC/KYB endpoints or programmatic counterparty clearance flows before money moves. 'Qualified businesses can apply for a Circle Mint account' implies manual vetting, not a documented API-driven onboarding flow. missing for 10: documented KYC/KYB API endpoints, programmatic counterparty verification/clearance flow, any compliance-status check before transfer.

   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”

   proof ↗⚑ flag

   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
   Circle—none0/10

   The evidence pack contains no published list of Circle's licensed/registered entities or the jurisdictions they cover — only product/API docs and community commentary on SVB reserve issues, none of which addresses corporate/legal entity transparency.

   ⚑ flag

   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
   Circle—none0/10

   The evidence pack contains only a generic mention of 'built-in compliance guardrails' for agent wallets, with no naming of sanctions screening, wallet risk checks, or travel-rule handling as specific mechanisms. As a regulated stablecoin/payments platform, this axis clearly applies, but no documentation evidence names these specific compliance processes.

   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”

   proof ↗⚑ flag

   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 to Paxos
   Circle~partialprobed5/10

   Circle's docs clearly show infrastructure abstraction — no raw key management, gas sponsorship via credit card, USDC-based gas payment, and automated cross-chain triggers — meaning developers don't operate blockchain nodes or handle gas directly (circle-docs-1, circle-docs-2, circle-docs-3, circle-docs-5). However, there's no direct evidence of a conventional REST API description or client libraries in specific languages, and a probe for a discoverable OpenAPI spec returned 404s across all candidate paths, weakening confidence in a standard REST/SDK developer experience. Missing for 10: explicit REST API documentation with endpoint/method examples, evidence of client libraries (SDKs) in specific languages, and a working OpenAPI/swagger spec.

   • [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
   • [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”
   • [claimed-docs] “Let users pay gas fees with USDC instead of native tokens using Circle's permissionless ERC-4337 paymaster contracts.”
   • [claimed-docs] “Trigger automated actions on the destination blockchain after assets arrive”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   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
   Circle—none0/10

   No evidence pack item documents a sandbox/testnet mode, test values, or deterministic test environments for payments, payouts, or conversions; the docs describe live features (CCTP, wallets, payouts, Circle Mint) without mentioning any test/sandbox mode. missing for 10: documented sandbox or testnet environment, test API keys/values, deterministic test behavior for payments/payouts/conversions.

   ⚑ flag

   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
   Circle~partialclaimed5/10

   Circle's docs confirm a webhook system that POSTs to a configured endpoint when a resource changes state, which supports async state tracking without polling — but the evidence never mentions signing/signature verification of webhooks, nor explicitly lists event types like 'payment confirmed', 'payout settled', or 'conversion executed'. missing for 10: documentation of webhook signature/verification mechanism, explicit enumeration of event types matching payments/payouts/conversions, and any independent confirmation of webhook reliability in production.

   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”

   proof ↗⚑ flag

   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
   Circle~partialprobed5/10

   Circle documents fiat↔USDC conversion via Circle Mint 'at no additional cost' and cross-border fiat payouts through CPN with 'real-time FX quotes' and settlement in USDC onchain, showing conversion is a core capability, but neither doc gives concrete rate/fee schedules or settlement-time SLAs, and no OpenAPI spec was found to confirm a dedicated conversion/quote endpoint (circle-probe-2 shows 404s). Missing for 10: documented fee tables, settlement-time guarantees, and a discoverable quotes/conversion API reference or independent verification of accuracy.

   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   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 Paxos
   Circle—none0/10

   Evidence shows Circle Mint lets qualified businesses convert USD↔USDC directly (not an embeddable end-user onramp) and CPN handles cross-border fiat payouts, but no documented widget or API exists for embedding a card/bank-transfer fiat-to-stablecoin purchase flow for end users inside a third-party product.

   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”

   proof ↗⚑ flag

   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 Paxos
   Circle~partialprobed5/10

   Circle's docs show extensive API surface (Wallets, CCTP, Agent Wallets, CPN, webhooks) and even a CLI/MCP server built atop that API, suggesting API-first design, but no evidence explicitly confirms full UI/console parity, and the openapi spec probe returned 404s in all attempted locations, undermining verifiable completeness. missing for 10: explicit statement of API/UI feature parity, a discoverable OpenAPI spec, and independent confirmation that console-only features (e.g., dashboard settings) are also API-accessible.

   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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
   Circle—none0/10

   The evidence describes individual payout rails (CPN cross-border fiat payouts, Circle Mint USD/USDC conversion) but nowhere documents a batch or bulk payout API that processes many payouts in one call with per-item status tracking. Missing for 10: any mention of batch/bulk endpoint, multi-item payout request format, or per-item status/webhook reporting for mass disbursement runs.

   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”

   proof ↗⚑ flag

   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 drawn
   Circle~partialclaimed5/10

   Circle's docs describe Cross-Chain Payments Network (CPN) enabling cross-border fiat payouts via partner network with real-time FX quotes and local fiat delivery, and Circle Mint for USD↔USDC conversion, matching the off-ramp story's core mechanism. However, no evidence lists a published set of specific supported currencies or countries, nor does it detail settlement timelines or bank-transfer specifics that an ops lead would need to plan payouts. Missing for 10: a published currency/country coverage list, settlement SLAs, and independent confirmation of real-world payout success.

   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”

   proof ↗⚑ flag

   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
   Circle~partialclaimed6/10

   Circle's docs show programmatic USDC transfers via Wallets APIs, cross-border fiat payouts through CPN with real-time FX quotes and onchain USDC settlement, and webhook-based state-change notifications that could serve as status tracking. However, there's no explicit documentation of a 'stored recipient' object/API or a full payout status lifecycle (e.g., enumerated states from initiated to settled), and no independent/hands-on corroboration of payout completion. Missing for 10: stored-recipient management API, explicit payout status enumeration/lifecycle docs, and third-party verification of end-to-end payout settlement.

   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
   • [claimed-docs] “Sponsor network fees so your users don't need to hold native tokens. Set policies and pay gas with your credit card.”

   proof ↗⚑ flag

   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 userControl data retention and deletion

   weight 2 · round drawn
   Circle—none0/10

   No evidence in the pack addresses data retention or deletion controls for AI-native users—no docs on data export, deletion policies, or retention settings; the community items concern reserve/treasury management, not data privacy.

   ⚑ 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
   Circle—none0/10

   Evidence shows Circle Mint conversion and CPN payouts exist, and webhooks notify on state changes, but there is no documented timing from payment to available balance, no published fee schedule per rail, and no mention of statements or accounting-consumable reports. The SVB/reserve community items are off-topic to settlement legibility and are excluded.

   ⚑ flag

   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
   Circle~partialclaimed5/10

   Circle Mint lets qualified businesses convert USD to/from USDC (circle-docs-13), and CPN documents cross-border fiat payouts settled in USDC (circle-docs-12), showing fiat↔stablecoin movement is supported. However, evidence lacks concrete API reference detail or dashboard walkthrough for internal transfers/rebalancing as a documented end-to-end flow — missing for 10: explicit API endpoints/parameters for fiat-stablecoin conversion, dashboard UI documentation, and independent confirmation of the rebalancing workflow.

   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”

   proof ↗⚑ flag

   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 to Paxos
   Circle~partialclaimed4/10

   Circle provides underlying primitives (wallets to receive USDC, webhooks to react to settlement state changes, CPN payout rails) that a developer could assemble into a payment acceptance flow, but the evidence pack shows no single documented 'create a payment / checkout' API object or flow analogous to a payment-intent API — CPN docs describe cross-border payout/self-managed lifecycle rather than a customer-facing checkout. Missing for 10: a dedicated payment/checkout creation endpoint, documented example of presenting an address+confirming settlement end-to-end, and independent confirmation this works in practice.

   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”

   proof ↗⚑ flag

   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
   Circle~partialprobed4/10

   Docs confirm USDC (and EURC via CCTP) support and mention cross-chain transfers, but the evidence pack never lists specific named chains/networks or explicitly names USDT or other peer stablecoins as supported. missing for 10: an explicit supported-chains matrix, explicit USDT/other stablecoin support confirmation, and a consolidated asset-network compatibility table.

   • [claimed-docs] “CCTP natively transfers USDC across blockchains using burn-and-mint, and extends to EURC and registered third-party assets... all without tr…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”

   proof ↗⚑ flag

   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 to Paxos
   Circle~partialclaimed6/10

   Circle documents both a direct USD↔USDC conversion mechanism (Circle Mint, at par, no fee) and a cross-border payments network (CPN) where partners deliver local fiat after USDC settlement, which together support a finance lead settling stablecoin receipts in fiat rather than holding crypto. However, there's no single documented 'auto-convert on receipt' checkout/payout feature purpose-built for merchants, and no independent confirmation of how seamlessly this flows into standard accounting so books never touch crypto. Missing for 10: an explicit automatic-conversion-on-payment-receipt feature, accounting/bookkeeping integration details, and independent/hands-on verification of the payout flow.

   • [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”

   proof ↗⚑ flag

   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 Circle
   Circle~partialprobed6/10

   Circle documents Agent wallets explicitly built to 'hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails,' plus an agent-stack CLI and x402 pay-per-request flow that support agent-initiated payments under human-configured limits (circle-docs-6, circle-docs-7, circle-docs-8). However, the evidence lacks a concrete end-to-end documented example of an agent actually initiating a payout with a specific spend-control policy set by a human, or details on how those controls are configured/enforced. Missing for 10: a worked example/tutorial showing a human setting spend limits and an agent executing a constrained payment, independent/hands-on verification of the guardrails working in practice.

   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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 Circle
   Circle~partialprobed6/10

   Circle documents dedicated Agent wallets with spending controls and compliance guardrails, MPC/passkey key management (no raw private key handling), and an agent CLI/MCP stack for programmatic wallet use, which directly supports the story. However, evidence lacks specifics on scoped-key issuance granularity, concrete documented limits/spend caps, or independent/hands-on validation of policy enforcement in practice. missing for 10: detailed scoped-key/permission model docs, concrete numeric spend-limit examples, independent verification that policy controls hold up in real agent usage.

   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
   • [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”

   proof ↗⚑ flag

   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 Circle
   Circle~partialprobed7/10

   Circle explicitly documents x402 support ('Search x402-compatible APIs and pay per request, without subscriptions or API keys') as part of its Agent Stack, with SDK/CLI and MCP server tooling for agents to discover and pay for services. However, ACP, MPP, and AP2 are not mentioned anywhere in the evidence, and no dedicated x402 endpoint/OpenAPI spec is exposed (openapi probe 404s), leaving the protocol claim documented only at a feature-description level rather than full technical spec. Missing for 10: explicit ACP/MPP/AP2 support or endpoints, and a concrete x402 API reference/OpenAPI schema beyond prose description.

   • [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
   • [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   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 drawn
   Circle—none0/10

   Evidence shows Circle Mint (converting USD↔existing USDC) and CPN (a self-managed model where the founder—not Circle—handles custody, payouts, and compliance for their own stablecoin lifecycle), but nothing documents a Circle-hosted white-label issuance product covering minting, redemption, and reserve management for a founder's own branded coin, nor any honest disclosure of eligibility gating for such a product.

   • [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”

   proof ↗⚑ flag

   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
   Circle—none0/10

   The evidence pack contains no documentation of USDC reserve composition, attestation reports, or any yield/rewards program with eligibility and regulatory caveats — the docs items only cover developer platform features (wallets, CCTP, agent stack, Circle Mint conversion). Community items discuss a 2023 SVB reserve incident but do not constitute or corroborate ongoing published reserve/attestation documentation.

   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
   • [community] “Circle said $3.3bn of USDC's cash reserves remained with SVB and had initiated transfers before the bank failed, then argued the FDIC should…”
   • [community] “Of USDC's ~23% cash reserves, roughly a third ($3.3bn of $9.7bn) was stuck at SVB while the rest was with other banks not facing the same is…”

   proof ↗⚑ flag

   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
   Circle~partialclaimed4/10

   Circle Mint is documented as a custodial USD↔USDC conversion account for 'qualified businesses' at no additional cost, which honestly signals gating, but the evidence never specifies which geographies are supported, what qualification criteria entail, or SLAs/availability guarantees. Missing for 10: stated geographic coverage, explicit eligibility/KYC requirements, and any independent or hands-on corroboration of account onboarding.

   • [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”

   proof ↗⚑ flag

   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 drawn
   Circle—none0/10

   No evidence pack items describe named virtual accounts or dedicated per-customer deposit addresses for automated payment attribution/reconciliation; docs cover wallets, gas sponsorship, CCTP, webhooks, and payouts but nothing about per-customer deposit address issuance or account matching. Missing for 10: documentation of per-customer virtual account/deposit address creation, evidence of automatic incoming-payment-to-customer matching, and any reconciliation tooling tied to those addresses.

   ⚑ flag

   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 Circle
   Circle~partialprobed6/10

   Circle's docs confirm programmatic wallet creation with MPC/passkey-based key custody (no raw private key management for developers), and Agent wallets for per-purpose/per-customer use cases with spending controls, plus webhooks for wallet state changes. However, there's no direct documentation snippet showing explicit API endpoints for deposit address provisioning per customer, and the openapi/API reference spec itself is not accessible (404s), limiting verification of exact wallet-creation API semantics. Missing for 10: explicit API reference for wallet/deposit-address creation endpoints, clearer documentation of per-customer wallet architecture, and independent/hands-on corroboration of custody claims.

   • [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
   • [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”

   proof ↗⚑ flag

   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