MoonPay vs Paxos

Agent access

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

   weight 2 · round drawn
   MoonPay✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 MoonPay
   MoonPay✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

   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 to Paxos
   MoonPay~partialprobed7/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Paxos~partialclaimed5/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to MoonPay
   MoonPay~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   Paxos~partialclaimed4/10

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

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

   proof ↗⚑ flag

Abstraction

1. developerI never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language

   weight 3 · round drawn
   MoonPay~partialprobed6/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 MoonPay
   MoonPay✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Paxos~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   MoonPay—none0/10

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

   ⚑ flag

   Paxos—none0/10

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

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   MoonPay—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   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