Circle vs MoonPay
Circle wins · 18–10 (15 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to MoonPayCircle 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”
MoonPay has a confirmed llms.txt (probe returned HTTP 200 with descriptive content) and dedicated docs on using AI agents, including an official MCP server for searching/retrieving docs. missing for 10: independent third-party confirmation of agent usage beyond MoonPay's own docs/probes.
- [probe] “PROBE llms.txt: HTTP 200 at https://dev.moonpay.com/llms.txt # MoonPay Developer Docs > Integrate MoonPay's on-ramp, off-ramp, and swap pro…”
- [claimed-docs] “Let new customers buy crypto with Apple Pay or Google Pay without a MoonPay account.”
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to CircleCircle 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.”
MoonPay offers headless APIs/SDKs (build-your-own on-ramp, quote and session endpoints) and a dedicated test mode with testnets/simulated payments that could be scripted in a CI pipeline, but there is no evidence of a CLI, automation-first tooling, or documentation describing running MoonPay flows unattended in CI. Missing for 10: explicit CI/automation guidance, evidence of non-interactive KYC/payment flows, and independent confirmation of headless test-mode usage in pipelines.
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
ai-native userConnect an agent via an official MCP server
weight 3 · round to CircleCircle 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”
MoonPay documents an official MCP server for its developer docs that gives AI agents direct access to search and retrieve content, corroborated by a probe confirming the page exists. Missing for 10: independent hands-on verification of the MCP server actually working with an agent, and details on scope/capabilities beyond docs search/retrieval.
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userUse an official CLI
weight 2 · round to CircleCircle 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”
ai-native userDrive the product through a documented public API
weight 3 · round to CircleCircle'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”
MoonPay publishes detailed API reference docs (quotes, sessions, webhooks, test mode) letting developers programmatically drive on/off-ramp flows, and even documents an MCP server for AI agents to browse docs. However, a probe for standard machine-readable API specs (OpenAPI/Swagger) returned 404s across all candidate paths, suggesting no formal machine-consumable spec exists, which limits fully autonomous/agentic API discovery. missing for 10: a discoverable OpenAPI/Swagger spec, independent/hands-on confirmation that an AI agent can successfully call the API end-to-end.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to CircleCircle's Agent Stack docs mention 'Agent wallets... with customizable spending controls and built-in compliance guardrails' (circle-docs-6), which implies some least-privilege control over what an agent can spend, but there is no documentation of scoped API keys, permission tiers, or credential issuance specifically for API access. Missing for 10: explicit API key/token scoping mechanism, documented permission levels for agent credentials, and any independent verification of these controls in practice.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
MoonPaynone0/10Evidence shows API keys and session tokens for general integration (moonpay-docs-15) and a documentation MCP server for search/retrieval (moonpay-docs-6), but nothing about issuing scoped or least-privilege credentials specifically for AI agents acting on a user's behalf. No permissions model, credential scoping, or agent-specific access controls are documented.
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userBuild against official SDKs
weight 2 · round to MoonPayCirclenone0/10Evidence describes Circle's APIs, CLI, MCP server, and webhooks, but no item mentions official language SDKs (e.g., Node/Python/Java client libraries) for building against Circle's platform; the OpenAPI spec probe even returned 404s, suggesting no evidence of SDK generation or distribution.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
MoonPay's docs explicitly mention building on 'APIs and SDKs' (moonpay-docs-3) and provide a demo integrations repo (moonpay-docs-7) and API reference endpoints (moonpay-docs-14, moonpay-docs-15), indicating some SDK/dev-tooling support. However, there's no direct evidence of language-specific SDK packages, an OpenAPI spec (probe shows 404s for standard OpenAPI paths, moonpay-probe-2), or independent developer corroboration of SDK quality/coverage. Missing for 10: concrete SDK package listings (npm, PyPI, etc.), OpenAPI/spec-driven tooling, and independent hands-on confirmation of SDK usability.
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnCircle 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.”
MoonPay documents webhook events that notify applications of account activity, with specific examples like sell_transaction_requote_required, giving developers a concrete subscription mechanism for events. This directly satisfies the story's core need for event-driven notifications. Missing for 10: a full list/catalog of all webhook event types, subscription management API/UI documentation, and independent third-party confirmation of webhook reliability.
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round to CircleCircle 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”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnCirclenone0/10Circle documents an 'Agent Stack' (agent wallets, x402 payments, CLI, MCP server) for building AI agents that consume Circle's crypto rails, but this is infrastructure for third-party agents to interact with Circle—not a built-in AI assistant inside Circle's own product that a user can delegate tasks to.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
MoonPaynone0/10MoonPay's evidence only describes an MCP server that lets external AI agents search/retrieve documentation content (moonpay-docs-6, moonpay-probe-3) — this is a developer-docs tool, not a built-in AI assistant inside the product that end-users can delegate purchase/sell/swap tasks to. No evidence of any in-product assistant, chat interface, or agentic task delegation for users.
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userOperate the product with natural-language commands
weight 2 · round to CircleCircle 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”
MoonPaynone0/10MoonPay's evidence only shows an MCP server for searching/retrieving documentation content, not for operating the actual on-ramp/off-ramp transactions via natural language; there is no evidence of a chat/agent interface that lets a user issue commands like 'buy $50 of ETH' through natural language.
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to MoonPayCirclenone0/10Circle's developer docs are markdown-based (llms.txt) and reference APIs, but there's no evidence of an interactive API reference with runnable examples; probes for OpenAPI/Swagger specs that would power such a reference all returned 404.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.circle.com/llms.txt # Circle Developer Platform > Circle builds infrastructure for digital d…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
MoonPay's dev docs include structured API reference pages (e.g., quotes/get, sessions/create) and a separate GitHub repo of clone-able demo integrations, but there's no evidence of an interactive, in-browser 'try it now' console — a probe for standard OpenAPI/swagger endpoints returned 404s, suggesting no exposed spec powering live runnable examples. Missing for 10: in-docs interactive request builder/console, publicly exposed OpenAPI spec, and confirmation that example code snippets are directly executable from the reference pages.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnCirclenone0/10The probe explicitly checked common OpenAPI spec paths (openapi.json, swagger.json, etc.) and all returned 404, indicating no downloadable machine-readable API spec is available, despite Circle having extensive API documentation. missing for 10: an actual OpenAPI/Swagger spec file accessible at a discoverable URL.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
MoonPaynone0/10No evidence of a downloadable OpenAPI/Swagger spec; a direct probe of common OpenAPI paths (openapi.json, swagger.json, etc.) returned 404 across the board, and docs only mention API reference pages and an MCP server for agent content retrieval, not a machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to MoonPayCirclenone0/10The evidence pack contains no mention of a sandbox/testnet environment, test API keys, or any way to develop against non-production data; all docs describe production wallet, CCTP, CLI, and MCP features without noting a separate test mode. Missing for 10: any mention of sandbox/testnet endpoints, test credentials, or documentation distinguishing sandbox vs production usage.
MoonPay explicitly documents a test mode using testnet blockchains and simulated payments so no real assets are transferred, directly matching the sandbox story, and this is reinforced by clone-able demo integrations for testing before production use. Missing for 10: independent/hands-on confirmation that the sandbox fully mirrors production behavior and more detail on how test-mode credentials/environments are provisioned.
- [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
- [claimed-docs] “The MoonPay Demo Integrations GitHub repository has working, clone-able example integrations ready to use - just add your API keys.”
- [claimed-docs] “Create a session token to initialize a connection”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnCirclenone0/10No evidence of API versioning scheme or a documented deprecation policy; the openapi.json/swagger probes all 404, and no docs mention version numbers or deprecation timelines. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog or migration guide.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.circle.com/openapi.json, https://developers.circle.com/swagger.json, https://deve…”
MoonPaynone0/10No evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; openapi spec probe 404s, and no changelog/versioning page is cited. missing for 10: versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnCirclenone0/10The evidence describes individual operations (wallet creation, single transfers, CCTP transfers, webhooks) via API/CLI/MCP, but no documentation mentions batch or bulk endpoints, bulk payout processing, or multi-item operations in one call. Missing for 10: batch API endpoints, bulk transfer/payout documentation, any bulk wallet or bulk transaction management feature.
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to CircleCircle 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.”
MoonPay exposes webhook events (e.g., transaction status, requote-required) that notify an application when activity occurs, which developers can use to build their own automated actions, but there is no evidence of a built-in rules/automation engine where users define conditional triggers within MoonPay itself. missing for 10: a native rule-builder or automation configuration UI/API, evidence of conditional logic or multi-step workflows tied to events, independent confirmation of automation use in production.
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
Compliance risk — stories about compliance risk in this arenaCompliance risk
Stories about compliance risk in this arena
Kyc
ops leadCustomer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves
weight 2 · round to MoonPayCirclenone0/10Evidence covers wallets, gas sponsorship, CCTP, agent wallets, CLI/MCP, and Circle Mint onboarding, but nowhere documents KYC/KYB endpoints or programmatic counterparty clearance flows before money moves. 'Qualified businesses can apply for a Circle Mint account' implies manual vetting, not a documented API-driven onboarding flow. missing for 10: documented KYC/KYB API endpoints, programmatic counterparty verification/clearance flow, any compliance-status check before transfer.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
MoonPay's docs describe KYC as a built-in, hosted part of its on-/off-ramp widget and API flow (session creation, quotes, webhooks) and note that returning users can skip re-onboarding, but there is no documented standalone KYC/KYB endpoint or explicit 'counterparty cleared' status API that an ops team could call programmatically before initiating a transfer — KYC is embedded in the transaction flow rather than exposed as an independent compliance-check service. missing for 10: explicit KYC/KYB API/endpoint documentation, a way to query verification/clearance status independent of a transaction, and any B2B/KYB (business) onboarding flow.
- [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
- [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
- [claimed-docs] “Connect existing MoonPay usersSkip re-onboarding. Plug into the existing MoonPay account base.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
Licensing
founderSee who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried
weight 2 · round drawnCirclenone0/10The evidence pack contains no published list of Circle's licensed/registered entities or the jurisdictions they cover — only product/API docs and community commentary on SVB reserve issues, none of which addresses corporate/legal entity transparency.
MoonPaynone0/10No evidence pack item names MoonPay's licensed/registered legal entities, regulatory licenses, or jurisdictional coverage; documentation is entirely product/API focused, and community items concern fee transparency and an unrelated scam-fund allegation, not entity/licensing disclosure.
Screening
ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at
weight 2 · round drawnCirclenone0/10The evidence pack contains only a generic mention of 'built-in compliance guardrails' for agent wallets, with no naming of sanctions screening, wallet risk checks, or travel-rule handling as specific mechanisms. As a regulated stablecoin/payments platform, this axis clearly applies, but no documentation evidence names these specific compliance processes.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
MoonPaynone0/10MoonPay's docs mention generic 'KYC and compliance' and 'payments' but never name specific machinery like sanctions screening, wallet risk scoring, or travel-rule data sharing — the exact named-not-waved-at requirement of this story. Missing for 10: any documentation naming sanctions/OFAC screening process, wallet address risk-scoring methodology, or travel-rule protocol implementation (e.g., Notabene/Sygna/TRISA integration).
- [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
- [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
- [claimed-docs] “Millions of users have previously purchased cryptocurrencies using MoonPay, having stored their payment and KYC details, leading to maximize…”
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Abstraction
developerI never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
weight 3 · round to MoonPayCircle'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…”
MoonPay's docs show a conventional REST API (quotes, sessions, webhooks) and widgets/SDKs that abstract on-chain mechanics like fees and rate-locking, letting developers build fiat-to-crypto flows without running nodes (moonpay-docs-3, moonpay-docs-14, moonpay-docs-15, moonpay-docs-11). However, there's no evidence of concrete multi-language client libraries or a public OpenAPI spec (probe found 404s at all candidate spec URLs), so the 'client libraries in my language' part of the story is unsupported. Missing for 10: enumerated SDK languages/repos, published OpenAPI/swagger spec, independent confirmation of ease-of-use across languages.
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
Sandbox
developerRehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically
weight 3 · round to MoonPayCirclenone0/10No evidence pack item documents a sandbox/testnet mode, test values, or deterministic test environments for payments, payouts, or conversions; the docs describe live features (CCTP, wallets, payouts, Circle Mint) without mentioning any test/sandbox mode. missing for 10: documented sandbox or testnet environment, test API keys/values, deterministic test behavior for payments/payouts/conversions.
MoonPay documents a dedicated test mode using testnet blockchains and simulated payments where no real assets are transferred, directly matching the sandbox/testnet rehearsal story for buy/sell/conversion flows. Missing for 10: explicit documentation of deterministic test values (e.g., specific test card numbers or fixed exchange rates) and independent/hands-on confirmation that payouts and conversions behave predictably in test mode.
- [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
Webhooks
developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
weight 2 · round drawnCircle's docs confirm a webhook system that POSTs to a configured endpoint when a resource changes state, which supports async state tracking without polling — but the evidence never mentions signing/signature verification of webhooks, nor explicitly lists event types like 'payment confirmed', 'payout settled', or 'conversion executed'. missing for 10: documentation of webhook signature/verification mechanism, explicit enumeration of event types matching payments/payouts/conversions, and any independent confirmation of webhook reliability in production.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
MoonPay docs confirm a webhook system that notifies apps of account activity and give an example event (sell_transaction_requote_required), supporting event-driven state tracking. However, there is no evidence of cryptographic signing/verification of webhooks, nor documentation of specific 'payment confirmed', 'payout settled', or 'conversion executed' event types the story describes. missing for 10: signature verification details, full enumerated list of transaction lifecycle events (buy/sell/swap completion, payout settlement), independent confirmation of webhook reliability.
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
Onramp conversion — stories about onramp conversion in this arenaOnramp conversion
Stories about onramp conversion in this arena
Conversion
developerConversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
weight 2 · round to MoonPayCircle 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…”
MoonPay documents a Quotes endpoint returning locked rate, fees, and a signature for fiat-to-crypto buys, plus off-ramp requote webhooks for sell price changes, giving developers programmatic access to rates/fees for fiat↔stablecoin conversion. However, stablecoin-to-stablecoin 'swap' conversion is only mentioned as a marketing feature (docs-18) without a documented quotes/fees API for that path, and no settlement-time documentation appears anywhere in the pack. missing for 10: documented quote/fee API for stablecoin-to-stablecoin swaps, explicit settlement-time guarantees, independent confirmation of rate accuracy.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
- [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
Onramp
developerEmbed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
weight 2 · round to MoonPayCirclenone0/10Evidence shows Circle Mint lets qualified businesses convert USD↔USDC directly (not an embeddable end-user onramp) and CPN handles cross-border fiat payouts, but no documented widget or API exists for embedding a card/bank-transfer fiat-to-stablecoin purchase flow for end users inside a third-party product.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
MoonPay documents a widget and API/SDK approach for embedding fiat-to-stablecoin (and crypto) onramp flows, supporting card, Apple Pay, Google Pay and bank transfers, with customization, prefill, webhooks, quotes and session tokens, plus test mode for development. missing for 10: no independent/hands-on developer corroboration of the integration experience, and no explicit confirmation of stablecoin-specific (vs generic crypto) purchase support in the widget docs.
- [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “You can customize the widget to feel like a native part of your site or application by adjusting button and background colors. You can also …”
- [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “MoonPay provides a test mode for integration development and testing. Test mode uses testnet blockchains and simulated payments. No real ass…”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to MoonPayCircle'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”
MoonPay documents a full build-your-own API/SDK path (quotes, sessions, webhooks, prefill, wallet creation, requote handling) that mirrors much of what the hosted widget UI offers, suggesting broad but not explicitly total parity. However, no OpenAPI/swagger spec was found (404s on all probed paths), and there's no explicit documentation stating 100% feature parity between API and UI, with a community question even asking if the API/webhook list is public at all. Missing for 10: explicit statement of full UI/API parity, a published OpenAPI spec, and independent developer confirmation that all UI features are API-accessible.
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Improve your customers' experience and speed up the buying process by pre-filling information such as their wallet address, email, selected …”
- [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
- [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”
Payouts offramp — stories about payouts offramp in this arenaPayouts offramp
Stories about payouts offramp in this arena
Batch
ops leadRun mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status
weight 2 · round drawnCirclenone0/10The evidence describes individual payout rails (CPN cross-border fiat payouts, Circle Mint USD/USDC conversion) but nowhere documents a batch or bulk payout API that processes many payouts in one call with per-item status tracking. Missing for 10: any mention of batch/bulk endpoint, multi-item payout request format, or per-item status/webhook reporting for mass disbursement runs.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Send cross-border fiat payouts through a network of payout partners. Request real-time FX quotes, settle in USDC onchain, and let partners d…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
MoonPaynone0/10MoonPay's docs describe single-transaction on-ramp/off-ramp flows (quotes, sessions, webhooks) for individual end-user purchases/sells, but there is no evidence of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
- [probe] “PROBE openapi: all candidate paths 404 (https://dev.moonpay.com/openapi.json, https://dev.moonpay.com/swagger.json, https://dev.moonpay.com/…”
Offramp
ops leadRecipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
weight 2 · round drawnCircle'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.”
MoonPay documents off-ramp (sell) rails paying out to bank account or card, with build-your-own or hosted options and sell-specific webhooks (requote), showing the payout mechanism exists and is documented for developers. However, there is no evidence of a published, itemized list of supported fiat currencies or countries for the off-ramp, which the story specifically requires. Missing for 10: published currency/country coverage table for off-ramp, independent confirmation of payout rails working across those markets.
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
- [claimed-docs] “Handle the sell_transaction_requote_required webhook to surface in-app requote notifications when a sell price changes.”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
Payouts
developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
weight 3 · round to CircleCircle'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.”
MoonPaynone0/10MoonPay's docs describe on-ramp/off-ramp widgets and APIs for individual users buying/selling crypto (quotes, sessions, webhooks for sell/requote), but there is no evidence of a payouts API that lets a developer programmatically disburse stablecoins to a wallet address or stored recipient list with settlement status tracking — that is a distinct payouts/disbursement capability not shown in the pack.
- [claimed-docs] “A hosted on-ramp and off-ramp you embed in your app. MoonPay runs the KYC, payments, and UI.”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userControl data retention and deletion
weight 2 · round drawnCirclenone0/10No evidence in the pack addresses data retention or deletion controls for AI-native users—no docs on data export, deletion policies, or retention settings; the community items concern reserve/treasury management, not data privacy.
MoonPaynone0/10No evidence pack content addresses data retention policies, user data deletion requests, or privacy controls for AI-native users; docs focus on payments, KYC integration, and widget customization. Missing for 10: any documentation of data retention policy, user-initiated deletion/erasure mechanism, or privacy control API/settings.
Settlement treasury — stories about settlement treasury in this arenaSettlement treasury
Stories about settlement treasury in this arena
Settlement
finance leadSettlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume
weight 2 · round drawnCirclenone0/10Evidence shows Circle Mint conversion and CPN payouts exist, and webhooks notify on state changes, but there is no documented timing from payment to available balance, no published fee schedule per rail, and no mention of statements or accounting-consumable reports. The SVB/reserve community items are off-topic to settlement legibility and are excluded.
MoonPaynone0/10The evidence pack shows webhooks, quotes with locked rates/fees, and test mode, but nothing documents settlement timing (payment to available balance), a published fee schedule per rail, or accounting-consumable statements/reports. A community comment even asks whether MoonPay's fee structure/API is publicly available, suggesting no clear published fee documentation exists. Missing for 10: settlement timing documentation, per-rail fee schedules, downloadable statements/reports for accounting.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [community] “Wow, Congrats to MoonPay! I was curious about their fee structure, and after digging was able to find the following chart... Is the API publ…”
Treasury
finance leadMove value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
weight 2 · round to CircleCircle 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…”
MoonPaynone0/10MoonPay's documented capabilities are consumer-facing on-ramp/off-ramp/swap widgets and APIs (buy, sell, quote, webhooks) for end users converting fiat to crypto and back — there is no evidence of an internal treasury/balance system, account-to-account transfers, or rebalancing API/dashboard aimed at a finance lead managing platform-held fiat and stablecoin balances. Missing for 10: any documentation of internal ledger/balance accounts, transfer-between-balances API, or treasury dashboard for rebalancing fiat vs stablecoin holdings.
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance
Stories about stablecoin acceptance in this arena
Acceptance
developerAccept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically
weight 3 · round to CircleCircle 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”
Chains
developerThe platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold
weight 2 · round to CircleDocs 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…”
MoonPaynone0/10The evidence pack shows general on-ramp/off-ramp and cross-chain swap capabilities but contains no documentation listing specific supported stablecoins (USDC, USDT, etc.) or named blockchain networks. Missing for 10: an explicit supported-assets/networks list, stablecoin-specific documentation, and named chain coverage.
Fiat settlement
finance leadTake crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto
weight 3 · round to CircleCircle 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…”
MoonPay's off-ramp product (docs-17, docs-3) lets crypto be converted to cash paid to a bank account or card, and this can be built into a business's own flow via APIs/webhooks (docs-11, docs-14). However, this is framed as a consumer/end-user cash-out feature, not a documented merchant treasury/settlement product for automatically converting incoming stablecoin payments into a fiat balance so a business's books never hold crypto. Missing for 10: explicit merchant/business settlement documentation, stablecoin-specific auto-conversion mechanics, fiat balance/ledger concept, and accounting-oriented guarantees that crypto is never held.
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
- [claimed-docs] “Build your own on-ramp and off-ramp on MoonPay's APIs and SDKs. Your UI, your flow, our rails.”
- [claimed-docs] “MoonPay can send webhook events that notify your application whenever an activity occurs on your account.”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access
Stories about stablecoin agent access in this arena
Agent payments
ai-native userAn agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured
weight 3 · round to CircleCircle documents Agent wallets explicitly built to 'hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails,' plus an agent-stack CLI and x402 pay-per-request flow that support agent-initiated payments under human-configured limits (circle-docs-6, circle-docs-7, circle-docs-8). However, the evidence lacks a concrete end-to-end documented example of an agent actually initiating a payout with a specific spend-control policy set by a human, or details on how those controls are configured/enforced. Missing for 10: a worked example/tutorial showing a human setting spend limits and an agent executing a constrained payment, independent/hands-on verification of the guardrails working in practice.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “Search x402-compatible APIs and pay per request, without subscriptions or API keys.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
MoonPaynone0/10MoonPay's MCP server (moonpay-docs-6, moonpay-probe-3) only gives agents access to search/retrieve documentation content, not to initiate payments. There is no evidence of an agent payment flow with human-configured spend controls, scoped authority, or delegated transaction limits — the API docs describe quotes/sessions for human-driven checkout flows, not autonomous agent-initiated payouts.
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
- [claimed-docs] “Builds a quote for a fiat-to-crypto buy. Returns locked rate, fees, and signature for payment execution.”
- [claimed-docs] “Create a session token to initialize a connection”
Agent wallets
ai-native userAgents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move
weight 2 · round to CircleCircle documents dedicated Agent wallets with spending controls and compliance guardrails, MPC/passkey key management (no raw private key handling), and an agent CLI/MCP stack for programmatic wallet use, which directly supports the story. However, evidence lacks specifics on scoped-key issuance granularity, concrete documented limits/spend caps, or independent/hands-on validation of policy enforcement in practice. missing for 10: detailed scoped-key/permission model docs, concrete numeric spend-limit examples, independent verification that policy controls hold up in real agent usage.
- [claimed-docs] “Use Agent wallets to hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails.”
- [claimed-docs] “You don't manage raw private keys... Circle secures keys with MPC or passkeys depending on wallet product”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
- [probe] “official CLI documented at https://developers.circle.com/agent-stack/circle-cli”
MoonPaynone0/10Evidence covers MoonPay's on/off-ramp widget, API, and MCP docs-server for content retrieval, but there is no mention of programmatic wallet issuance for AI agents, scoped API keys, policy controls, or documented spend limits governing what an agent can move. The comm-1 item is off-topic (fraud allegation, not agent wallet controls) and ignored.
Protocols
ai-native userThe platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration
weight 2 · round to CircleCircle 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…”
Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance
Stories about stablecoin issuance in this arena
Issuance
founderIssue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly
weight 2 · round drawnCirclenone0/10Evidence shows Circle Mint (converting USD↔existing USDC) and CPN (a self-managed model where the founder—not Circle—handles custody, payouts, and compliance for their own stablecoin lifecycle), but nothing documents a Circle-hosted white-label issuance product covering minting, redemption, and reserve management for a founder's own branded coin, nor any honest disclosure of eligibility gating for such a product.
- [claimed-docs] “Self-managed: You operate your own stablecoin lifecycle, including custody, payouts, and compliance. Circle provides the rails, APIs, and ro…”
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
Yield
finance leadThe economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly
weight 2 · round drawnCirclenone0/10The evidence pack contains no documentation of USDC reserve composition, attestation reports, or any yield/rewards program with eligibility and regulatory caveats — the docs items only cover developer platform features (wallets, CCTP, agent stack, Circle Mint conversion). Community items discuss a 2023 SVB reserve incident but do not constitute or corroborate ongoing published reserve/attestation documentation.
- [claimed-docs] “Qualified businesses can apply for a Circle Mint account to readily convert USD to and from USDC at no additional cost.”
- [community] “Circle said $3.3bn of USDC's cash reserves remained with SVB and had initiated transfers before the bank failed, then argued the FDIC should…”
- [community] “Of USDC's ~23% cash reserves, roughly a third ($3.3bn of $9.7bn) was stuck at SVB while the rest was with other banks not facing the same is…”
Wallets balances — stories about wallets balances in this arenaWallets balances
Stories about wallets balances in this arena
Balances
finance leadMy business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
weight 3 · round to CircleCircle 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.”
MoonPaynone0/10Evidence describes MoonPay purely as an on-ramp/off-ramp/swap payment rail (buy/sell/bridge crypto, webhooks, quotes, session tokens) with no documented custodial account product for holding a business stablecoin balance, nor any stated availability, geography, or gating for such a balance. This is a plausible axis for a crypto payments platform to address, but no supporting evidence exists.
- [claimed-docs] “MoonPay lets you add fiat-to-crypto to your product without rebuilding payments, KYC, and compliance.”
- [claimed-docs] “Use a card, Apple Pay or Google Pay to buy crypto fast. We also accept bank transfers and wires.”
- [claimed-docs] “Turn your crypto into cash. In a flash. Get paid straight to your bank account or Visa card.”
- [claimed-docs] “Trade between tokens, even if they're on different chains (we make bridging seamless too).”
Virtual accounts
developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
weight 2 · round drawnCirclenone0/10No evidence pack items describe named virtual accounts or dedicated per-customer deposit addresses for automated payment attribution/reconciliation; docs cover wallets, gas sponsorship, CCTP, webhooks, and payouts but nothing about per-customer deposit address issuance or account matching. Missing for 10: documentation of per-customer virtual account/deposit address creation, evidence of automatic incoming-payment-to-customer matching, and any reconciliation tooling tied to those addresses.
Wallets
developerCreate wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
weight 2 · round to CircleCircle'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…”
MoonPaynone0/10MoonPay's docs mention it can auto-create a wallet for users via email during the on-ramp purchase flow, but this is a widget-embedded convenience feature, not a documented developer API for programmatically provisioning per-customer/purpose wallets or deposit addresses, and there is no documentation of key custody semantics.
- [claimed-docs] “Users don't have a digital wallet? We can create one for them using just their email address as they go through the purchase flow.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableCirclen/aCircle is a stablecoin/payments infrastructure platform (wallets, CCTP, CLI, agent-stack) that itself PUBLISHES an MCP server so external LLMs/IDEs can use Circle's tools — the reverse relationship. There is no evidence Circle functions as an agent runtime or host into which a user would plug external MCP servers for Circle to consume; this axis does not fit Circle's product category.
- [claimed-docs] “Integrate Circle's MCP server to let your LLM or AI-assisted IDE generate and fix code for crypto apps using Circle's offerings, including W…”
- [probe] “official MCP server documented at https://developers.circle.com/ai/mcp”
MoonPayn/aMoonPay is a fiat-to-crypto payments/API platform, not an AI agent or assistant that itself consumes tools via MCP. The evidence shows MoonPay exposing its own MCP server so external agents can query its docs (the reverse direction), which doesn't make 'plugging MCP servers into MoonPay so it can use their tools' an applicable axis.
- [claimed-docs] “The documentation includes a Model Context Protocol (MCP) server that gives AI agents direct access to search and retrieve content.”
- [probe] “official MCP server documented at https://dev.moonpay.com/platform/overview/using-agents”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableCirclen/aCircle is a stablecoin/payments infrastructure and wallet platform, not a data analytics or insights product; the evidence covers wallets, CCTP, MCP for coding, and treasury/reserve issues, with nothing about generating AI insights or suggestions from a user's own data within the product. This axis is a category error for this type of product.
MoonPayn/aMoonPay is a fiat-crypto on/off-ramp payments infrastructure product, not a data analytics or insights product; there is no user-facing data dashboard or analytics surface where AI-generated insights/suggestions would apply. The MCP server evidence relates to AI agents accessing developer docs, not generating insights from a user's data inside the product.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableCirclenone0/10No evidence of any scheduling, cron-like, or recurring workflow/job capability in Circle's docs, CLI, MCP server, or webhooks — webhooks (circle-docs-10) are event-triggered, not scheduled, and no automation-scheduling feature is documented. Missing for 10: any scheduler/cron API, recurring job configuration, or workflow automation timing controls.
- [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
- [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC, CCTP, payments); it has no concept of user-authored 'automations' with version control, review, and rollback like a workflow/automation builder. This story targets a category of product Circle is not.
ai-native userExport all of my data in open formats and leave
weight 3 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC transfers, payments rails), not a data-storage or productivity product where 'exporting all my data in open formats and leaving' is a meaningful axis; there's no user data corpus to export in this sense.
ai-native userRead the product's source under an open license
weight 2 · not comparableCirclenone0/10No evidence of Circle publishing source code under an open license; Circle is a closed commercial platform with docs, APIs, CLI, and MCP server, but nothing indicates open-source availability of its core product source.
ai-native userSelf-host the core product
weight 3 · not comparableCirclen/aCircle is a hosted infrastructure/API platform for stablecoins and wallets, not open-source software meant to be self-hosted; self-hosting the 'core product' is a category error for this type of managed financial service.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableCirclen/aCircle is a crypto/stablecoin infrastructure and agent-wallet platform, not a data-storage or hosting service; data residency/region choice is not an applicable axis for this product category, and no evidence pack content addresses storage location controls.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableCirclen/aCircle is a stablecoin/crypto infrastructure platform (wallets, USDC, CCTP, payments); AI-model-training data usage controls are not a relevant axis for this product category, and no evidence pack content pertains to it.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableCirclen/aCircle is a stablecoin/blockchain infrastructure platform (wallets, USDC transfers, agent payment rails), not a developer tool or AI agent product with local telemetry collection; opting out of telemetry/usage tracking is not a relevant axis for this kind of product based on the evidence provided.