[ { "productId": "bvnk", "storyId": "accept-stablecoin-checkout", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "BVNK's docs describe creating payment channels (unique repeated-use blockchain addresses) to accept stablecoin payments, converting to fiat, plus webhook notifications for settlement confirmation and a sandbox for testing pay-ins programmatically. This covers create → present address → confirm settlement end-to-end via documented API, though evidence is docs-only without independent hands-on confirmation. Missing for 10: independent/hands-on verification of the checkout flow working in practice, and more detail on the specific 'create payment' endpoint/response schema.", "evidenceIds": [ "bvnk-docs-9", "bvnk-docs-10", "bvnk-docs-2", "bvnk-docs-3", "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "agent-initiated-payments", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows general wallet/payment/API capabilities (wallets, rules automation, transfers) but nothing describing an 'agent' actor, scoped spend authority, or human-configured spend limits governing agent-initiated payments. The lone 'agent-wallet-cli' repo mention has no accompanying documentation of spend controls or agent payment flows, so this doesn't establish the capability.", "evidenceIds": [ "bvnk-probe-2", "bvnk-docs-5", "bvnk-docs-13" ] }, { "productId": "bvnk", "storyId": "agent-wallet-provisioning", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "BVNK documents general programmatic wallet creation (crypto/fiat) via API/Portal and Hawk-based API authentication, and a probe references an 'agent-wallet-cli' repo, suggesting some agent-oriented wallet tooling exists. However there is no documentation of scoped API keys per agent, policy/permission controls, or explicit spending/movement limits tailored to autonomous agents. Missing for 10: scoped-key issuance mechanics, policy engine/spend-limit configuration, and agent-specific governance documentation.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-1", "bvnk-probe-2" ] }, { "productId": "bvnk", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "BVNK hosts a live llms.txt file at docs.bvnk.com/llms.txt confirmed via HTTP 200 probe, containing structured summaries of its API documentation, and individual doc pages are also machine-readable markdown (.md) endpoints. Missing for 10: no independent third-party confirmation of agent usage/adoption of this llms.txt beyond the probe check.", "evidenceIds": [ "bvnk-probe-1", "bvnk-docs-1", "bvnk-docs-7" ] }, { "productId": "bvnk", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of AI-generated insights, analytics, or suggestions surfaced within BVNK's product based on user data; documentation covers payment infrastructure, wallets, APIs, and webhooks only.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BVNK exposes a rules-based automation API (e.g., POST /payment/v1/rules to auto-link fiat virtual accounts to crypto addresses) and webhooks for real-time automated notifications, plus automatic on-ramp/settlement flows, which together enable background, event-driven automations without manual triggering. However this is payment-domain automation (rules, webhooks) rather than a general agentic/background-task framework, and there's no documentation of scheduling, monitoring dashboards, or broader autonomous workflow orchestration beyond these payment rules. missing for 10: general-purpose scheduling/orchestration beyond payment rules, evidence of monitoring/alerting for autonomous runs, and independent confirmation of reliability of these automations running unattended.", "evidenceIds": [ "bvnk-docs-2", "bvnk-docs-5", "bvnk-docs-14" ] }, { "productId": "bvnk", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BVNK exposes a full REST API with Hawk authentication, webhooks for automated notifications, and a sandbox environment for simulating pay-ins/payouts—all of which support headless, non-interactive automation. There's also a mentioned agent-wallet-cli tool suggesting scriptable/CLI usage. However, there's no explicit documentation of CI pipeline integration, headless auth flows for automated agents, or CI-specific guidance. Missing for 10: explicit CI/automation guide, confirmation the CLI supports non-interactive auth/config for pipelines, and independent evidence of real-world CI usage.", "evidenceIds": [ "bvnk-docs-1", "bvnk-docs-2", "bvnk-docs-3", "bvnk-probe-2" ] }, { "productId": "bvnk", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "medium", "rationale": "BVNK is a payments infrastructure/API platform (wallets, transfers, webhooks) rather than an AI agent or assistant that itself consumes tools via MCP; the evidence shows API/CLI tooling for building agentic wallet integrations, not a chat/agent surface that plugs into MCP servers. This axis (being an MCP client) is a category mismatch for a backend payments product, not a capability gap.", "evidenceIds": [ "bvnk-probe-2", "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "BVNK is a payments infrastructure product, and while an MCP server is a plausible axis for such an API platform, no evidence shows an official MCP server; only Hawk auth, webhooks, and REST APIs are documented, plus an unrelated CLI mention.", "evidenceIds": [ "bvnk-docs-1", "bvnk-docs-2", "bvnk-probe-2" ] }, { "productId": "bvnk", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence BVNK offers a natural-language command interface; its API/CLI (bvnk-probe-2) and docs describe structured REST endpoints and a traditional CLI, not NL-driven interaction. Missing for 10: any chat/NL command interface, agent SDK, or documented natural-language operation mode.", "evidenceIds": [ "bvnk-probe-2", "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "A single probe result points to an 'agent-wallet-cli' GitHub repo described as an official CLI, but there is no documentation content, usage examples, or independent corroboration of its functionality. missing for 10: detailed CLI docs, command reference, install/usage examples, independent confirmation of adoption.", "evidenceIds": [ "bvnk-probe-2" ] }, { "productId": "bvnk", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "BVNK publishes a documented public API (Hawk auth, webhooks, wallets, transfers, payment rules) with a dedicated docs site and llms.txt endpoint confirming API-driven access, plus a sandbox for testing. missing for 10: independent third-party corroboration of API robustness/versioning and explicit rate-limit/SLA documentation.", "evidenceIds": [ "bvnk-docs-1", "bvnk-docs-4", "bvnk-docs-5", "bvnk-docs-6", "bvnk-probe-1" ] }, { "productId": "bvnk", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "BVNK's docs only mention Hawk-based API authentication (bvnk-docs-1) and webhooks, with no mention of scoped, least-privilege, or role-restricted API credentials or agent-specific key issuance. No evidence describes creating limited-permission API keys or tokens for AI agents.", "evidenceIds": [ "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows extensive REST API documentation (auth, webhooks, sandbox, wallets, etc.) and one official CLI tool (agent-wallet-cli), but no evidence of official client SDKs (e.g., Python, JS, Java libraries) that developers could build against. The axis is fair for an API-driven fintech platform, but no SDK evidence is present, so this is 'none' rather than 'na'.", "evidenceIds": [ "bvnk-probe-1", "bvnk-probe-2", "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BVNK documents webhook subscriptions for real-time account event notifications, with a dedicated setup guide for creating a webhook listener. Missing for 10: no details on event type filtering/selection, payload signing/verification specifics, or independent hands-on corroboration of webhook reliability.", "evidenceIds": [ "bvnk-docs-2" ] }, { "productId": "bvnk", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "BVNK's docs describe endpoints and a sandbox simulation environment, but there is no evidence of an interactive API reference (e.g., a Swagger/OpenAPI explorer or 'try it' console) with runnable code examples embedded in the docs.", "evidenceIds": [ "bvnk-docs-3", "bvnk-probe-1" ] }, { "productId": "bvnk", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows extensive API documentation (docs.bvnk.com, llms.txt) and endpoint references, but nowhere is an OpenAPI/Swagger spec or other machine-readable spec file mentioned or linked for download. missing for 10: explicit OpenAPI/Swagger JSON or YAML file, a documented spec download link, any mention of spec format.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "api-sandbox", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BVNK explicitly documents a sandbox environment that simulates pay-ins and payouts consistently across accounts, letting developers test without touching production data. Missing for 10: no explicit statement of how sandbox data/credentials are isolated from production, no independent/hands-on confirmation, and no detail on how to switch environments via API.", "evidenceIds": [ "bvnk-docs-3" ] }, { "productId": "bvnk", "storyId": "api-versioning-policy", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "There is evidence of API versioning practice (Transfers v.3 replacing the legacy Quote API), showing BVNK does version and migrate APIs, but no documented deprecation policy, sunset timeline, or versioning scheme is provided. missing for 10: explicit deprecation policy documentation, versioning scheme details, sunset/EOL timelines, migration guarantees beyond one example.", "evidenceIds": [ "bvnk-docs-6" ] }, { "productId": "bvnk", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of bulk/batch endpoints (e.g., batch payouts, bulk wallet creation, or bulk transfer APIs); documentation covers single-item operations (single wallet, single rule, single transfer) with no mention of batch processing or multi-item requests. missing for 10: bulk/batch API endpoints, batch job status tracking, documentation of multi-item request payloads.", "evidenceIds": [ "bvnk-docs-5", "bvnk-docs-6", "bvnk-docs-12", "bvnk-docs-13" ] }, { "productId": "bvnk", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BVNK exposes a documented Rules API (POST /payment/v1/rules) that automatically links a fiat virtual account to a crypto address, and webhooks provide real-time event notifications that could trigger downstream automation. This shows genuine rule/event-driven automation, but only for a narrow, specific use case rather than a general-purpose rules engine covering arbitrary triggers/actions. Missing for 10: evidence of broader rule types (e.g., conditional logic across multiple event types), a general rules/automation dashboard, and third-party corroboration of rule reliability at scale.", "evidenceIds": [ "bvnk-docs-5", "bvnk-docs-2" ] }, { "productId": "bvnk", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "BVNK's docs show rule-based automation (e.g., linking accounts for fiat-to-crypto transfers) and event-driven webhooks, but there is no evidence of scheduling recurring jobs or workflows (e.g., cron-like recurring payments/transfers) on a timed basis. Missing for 10: any documentation of scheduled/recurring job creation, cron-style triggers, or recurring payment automation.", "evidenceIds": [ "bvnk-docs-5", "bvnk-docs-2" ] }, { "productId": "bvnk", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "BVNK is a payments/wallet infrastructure API with no evidence of any automation versioning, review, or rollback capability (its 'rules' and payment automation features have no documented version history, review workflow, or rollback mechanism). Applies as a fair question for any automation-capable platform, but no supporting evidence exists.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows individual payout, wallet, and transfer APIs (e.g., bvnk-docs-11, bvnk-docs-13, bvnk-docs-6) but nothing documenting a batch/bulk payout endpoint, mass-disbursement operation, or per-item status reporting for multiple payouts in one call. This is a fair axis for a payments platform, so absence of evidence means 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "custodial-stablecoin-balances", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BVNK docs and marketing confirm you can create and hold crypto/stablecoin wallets/balances (bvnk-docs-4, bvnk-docs-15, bvnk-docs-13, bvnk-docs-17, bvnk-docs-19), but there is no documentation on custodial account structure, licensing, geographic availability, or any gating/eligibility disclosures for holding stablecoin balances. missing for 10: explicit custodial/regulatory documentation, stated geographic availability, and honest disclosure of any gating or KYC/jurisdiction restrictions for balance holding.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-13", "bvnk-docs-15", "bvnk-docs-17", "bvnk-docs-19" ] }, { "productId": "bvnk", "storyId": "fiat-onramp-integration", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BVNK documents API-driven fiat-to-crypto conversion (linking fiat virtual accounts to blockchain addresses, automated on-ramp to crypto) and embedded wallets/virtual accounts that a developer could use to build an onramp flow, but there is no documented pre-built onramp widget, and no explicit mention of end users paying via card to buy stablecoins — the flow described is bank/virtual-account based automation rather than a card-based consumer buy widget. Missing for 10: a documented embeddable UI/widget component, explicit card-payment support for the onramp, and end-user-facing checkout flow evidence.", "evidenceIds": [ "bvnk-docs-5", "bvnk-docs-9", "bvnk-docs-14", "bvnk-docs-8", "bvnk-docs-12" ] }, { "productId": "bvnk", "storyId": "fiat-settlement-option", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "BVNK explicitly documents accepting stablecoin payments and receiving fiat currency in the account (bvnk-docs-9), with marketing and docs confirming 'Accept payments globally in stablecoins. Settle in fiat' and 'fund in stablecoins and pay out in fiat' (bvnk-docs-18, bvnk-docs-19), plus payout mechanisms to bank accounts (bvnk-docs-11) and fiat virtual accounts in major currencies (bvnk-docs-12). missing for 10: independent/hands-on confirmation of the auto-conversion accounting flow beyond vendor docs.", "evidenceIds": [ "bvnk-docs-9", "bvnk-docs-18", "bvnk-docs-19", "bvnk-docs-11", "bvnk-docs-12" ] }, { "productId": "bvnk", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BVNK exposes a dedicated Transfers v3 API for wallet-to-wallet currency conversion (replacing a legacy Quote API), plus fiat/stablecoin flows (fund in stablecoin, pay out in fiat) and partner markup-fee controls, indicating conversion is an API-first primitive. However, the pack lacks concrete documentation of quote request/response fields showing rates, fee breakdowns, or settlement-time SLAs for these conversions. missing for 10: explicit quote endpoint schema with rate/fee/settlement fields, independent confirmation of conversion accuracy or timing.", "evidenceIds": [ "bvnk-docs-6", "bvnk-docs-18", "bvnk-docs-14", "bvnk-docs-7", "bvnk-docs-9" ] }, { "productId": "bvnk", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BVNK docs describe fiat payout rails (payout-overview, virtual accounts in USD/EUR/GBP, stablecoin-to-fiat settlement flows) confirming that off-ramp to local bank accounts is supported, but there is no single published table enumerating all supported countries or the full currency corridor list beyond USD/EUR/GBP mentions. missing for 10: a published country/currency coverage matrix, confirmation of local payout rails outside USD/EUR/GBP, and independent verification of settlement speed/coverage claims.", "evidenceIds": [ "bvnk-docs-11", "bvnk-docs-12", "bvnk-docs-9", "bvnk-docs-18", "bvnk-docs-19" ] }, { "productId": "bvnk", "storyId": "kyc-onboarding-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence pack covers wallets, payments, webhooks, embedded wallets, and API auth, but no documented KYC/KYB endpoints or onboarding/counterparty-clearance flows are mentioned anywhere in the docs list.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "machine-payment-protocols", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of x402, ACP, MPP, or AP2 protocol support anywhere in the docs pack; BVNK documents Hawk auth, webhooks, wallets, and fiat/crypto conversion APIs but never mentions these machine-payment protocols by name or provides endpoints/SDKs for them.", "evidenceIds": [ "bvnk-docs-1", "bvnk-probe-1" ] }, { "productId": "bvnk", "storyId": "multi-chain-support", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows BVNK supports generic 'stablecoins' and 'crypto' wallets, but nowhere does it name specific stablecoins (USDC, USDT, etc.) or specific blockchain networks/chains supported. missing for 10: named stablecoin list (USDC, USDT, etc.), named supported chains/networks, any coin-to-chain compatibility matrix.", "evidenceIds": [ "bvnk-docs-9", "bvnk-docs-10", "bvnk-docs-13", "bvnk-docs-18", "bvnk-docs-19" ] }, { "productId": "bvnk", "storyId": "no-node-integration", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs show BVNK exposes a REST API for wallets, transfers, channels and payouts that hides on-chain mechanics (e.g., wallet, rule, and transfer endpoints), so nodes/gas are clearly abstracted. However, evidence only shows a Hawk-authenticated REST API and one CLI repo, not official client libraries/SDKs in multiple languages as the story specifies. Missing for 10: documented multi-language SDKs/client libraries, explicit statement that developers never touch node/gas mechanics.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-5", "bvnk-docs-6", "bvnk-docs-10", "bvnk-docs-1", "bvnk-probe-2" ] }, { "productId": "bvnk", "storyId": "openness-api-parity", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "BVNK's docs show broad API coverage across core UI functions—wallet creation (fiat/crypto), transfers, payouts, rules, embedded wallets, webhooks—and explicitly note wallets can be managed 'through the Portal or API' (bvnk-docs-4), suggesting strong UI/API parity. However there is no explicit statement or independent audit confirming every UI feature (e.g., rewards, virtual cards, markup fee configuration) has a full API equivalent. Missing for 10: explicit parity documentation stating all UI actions are API-accessible, and independent/hands-on verification that no UI-only features exist.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-5", "bvnk-docs-6", "bvnk-docs-8", "bvnk-docs-11", "bvnk-docs-12", "bvnk-probe-1" ] }, { "productId": "bvnk", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a bulk data export feature or open-format data portability; documentation covers payments, wallets, and APIs but nothing about exporting account/transaction data for migration or leaving the platform.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "BVNK is a closed commercial payments platform; no evidence of any open-source license or public source code repository for its core product. missing for 10: any open-source license, public source repo, or statement of source availability.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "BVNK is a hosted payments/wallet infrastructure SaaS (fiat/crypto rails, APIs, webhooks); self-hosting the core product is not a meaningful axis for this kind of regulated financial-infrastructure service, unlike open-source software products.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "payment-webhooks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs confirm BVNK webhooks deliver real-time, automated notifications for account changes (bvnk-docs-2), which supports event-driven state tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed/verifiable, nor does it enumerate specific event types like payment confirmed, payout settled, or conversion executed. Missing for 10: explicit signature/verification mechanism for webhooks, documented list of event types matching the story (payment/payout/conversion events), and any independent confirmation of reliability.", "evidenceIds": [ "bvnk-docs-2", "bvnk-docs-1" ] }, { "productId": "bvnk", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence describes data residency/region selection controls in BVNK's docs or product pages; the evidence pack covers payments, wallets, and API features only. This axis applies to a payments/fintech platform handling customer data, so absence of evidence yields none.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "BVNK is a crypto/fiat payments infrastructure product, not an AI model or AI-tooling product that trains on user data; the AI-training-data privacy axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "BVNK's evidence pack covers payments, wallets, webhooks, and API auth, but contains no mention of data retention policies, deletion controls, or privacy/data lifecycle management features for AI-native users. This is a fintech payments platform where such controls could plausibly exist (e.g., in compliance/data policies), but no documentation surfaces them.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or opt-out controls; BVNK's documentation focuses entirely on payment/wallet/API functionality. This is a fair privacy-posture question for any product handling user data via API/portal, so absence of evidence yields 'none' rather than 'na'. missing for 10: any mention of telemetry collection, opt-out settings, or privacy controls.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains only API/product documentation (webhooks, wallets, transfers, sandbox) and no published disclosure of the specific licensed or registered legal entities behind BVNK or the jurisdictions each covers. No regulatory/licensing page, entity list, or legal disclosures are cited anywhere in the evidence.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "reserve-yield-programs", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Marketing copy mentions a rewards program ('Put idle balances to work with built-in rewards') implying some yield mechanism, but there is no documentation of reserve composition, attestation reports, eligibility criteria, or regulatory caveats for held stablecoins. Missing for 10: reserve composition disclosure, third-party attestation reports, yield program eligibility rules, regulatory/risk caveats for the rewards program.", "evidenceIds": [ "bvnk-docs-17" ] }, { "productId": "bvnk", "storyId": "sanctions-travel-rule", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "None of the evidence names sanctions screening, wallet risk scoring/checks, or travel-rule handling—docs cover authentication, wallets, webhooks, transfers, and embedded partner features only. Absence of any specific compliance-machinery documentation means this axis is unmet.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items document settlement timing SLAs (payment to available balance), a published fee schedule per rail, or exportable statements/reports for accounting reconciliation; evidence only covers API mechanics like wallets, webhooks, transfers, and embedded partner features.", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "stablecoin-issuance", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "bvnk", "storyId": "stablecoin-payouts", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BVNK's docs confirm programmatic stablecoin sending via API (bvnk-docs-13, bvnk-docs-14, bvnk-docs-18), wallet creation/management via API (bvnk-docs-4), and webhook-based notifications for account changes (bvnk-docs-2), plus a sandbox simulation for payouts (bvnk-docs-3). However, there is no explicit documentation of a 'stored recipient' object, dedicated payout endpoint with status-lifecycle documentation (e.g., pending→settled states), or confirmation that webhooks specifically track payout-to-settlement status. missing for 10: dedicated payout API/status-tracking docs, stored-recipient object documentation, explicit settlement-state webhook events.", "evidenceIds": [ "bvnk-docs-13", "bvnk-docs-14", "bvnk-docs-18", "bvnk-docs-4", "bvnk-docs-2", "bvnk-docs-3" ] }, { "productId": "bvnk", "storyId": "testnet-sandbox", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BVNK documents a dedicated sandbox ('payment-sim') that simulates pay-ins and payouts consistently across accounts, which covers part of the story, but there is no explicit documentation of sandbox coverage for currency conversions (Transfers v3) or of deterministic test values/testnet behavior for those flows. missing for 10: sandbox coverage for conversions/Transfers API, explicit deterministic test-value behavior, and independent developer confirmation of sandbox fidelity.", "evidenceIds": [ "bvnk-docs-3", "bvnk-docs-6" ] }, { "productId": "bvnk", "storyId": "treasury-rebalancing", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "BVNK documents crypto/fiat wallet creation, the Transfers v3 API for wallet-to-wallet currency conversion, fiat-to-crypto automation rules, on/off-ramp flows, and messaging like 'use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat' — covering both API and dashboard rebalancing between fiat and stablecoin balances end to end. Missing for 10: an explicit worked example/tutorial showing a full internal transfer+rebalance flow with request/response payloads, and independent (non-vendor) confirmation of dashboard UX.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-5", "bvnk-docs-6", "bvnk-docs-9", "bvnk-docs-12", "bvnk-docs-13", "bvnk-docs-14", "bvnk-docs-18", "bvnk-docs-19" ] }, { "productId": "bvnk", "storyId": "virtual-accounts-addressing", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BVNK docs show both named virtual accounts (USD/EUR/GBP) for businesses/customers and 'channels' — unique, repeated-use blockchain deposit addresses that never change per customer — plus webhooks for real-time notification of incoming funds, directly enabling attribution without manual matching. missing for 10: explicit documentation tying a specific virtual account/address to a customer ID in transaction payloads, and independent/hands-on confirmation of reconciliation workflow.", "evidenceIds": [ "bvnk-docs-10", "bvnk-docs-12", "bvnk-docs-2", "bvnk-docs-11" ] }, { "productId": "bvnk", "storyId": "wallet-provisioning-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm crypto/fiat wallet and virtual-account creation via API or Portal (bvnk-docs-4, bvnk-docs-12), per-customer wallet provisioning (bvnk-docs-15), and reusable deposit addresses/'channels' for receiving crypto (bvnk-docs-10), which together demonstrate programmatic wallet/address provisioning. However there is no documentation of key custody semantics (custodial model, key management, signing responsibility) anywhere in the pack. Missing for 10: explicit key custody/ownership documentation, independent confirmation of API wallet creation workflow beyond docs snippets.", "evidenceIds": [ "bvnk-docs-4", "bvnk-docs-10", "bvnk-docs-12", "bvnk-docs-15" ] }, { "productId": "circle", "storyId": "accept-stablecoin-checkout", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Circle provides underlying primitives (wallets to receive USDC, webhooks to react to settlement state changes, CPN payout rails) that a developer could assemble into a payment acceptance flow, but the evidence pack shows no single documented 'create a payment / checkout' API object or flow analogous to a payment-intent API — CPN docs describe cross-border payout/self-managed lifecycle rather than a customer-facing checkout. Missing for 10: a dedicated payment/checkout creation endpoint, documented example of presenting an address+confirming settlement end-to-end, and independent confirmation this works in practice.", "evidenceIds": [ "circle-docs-10", "circle-docs-11", "circle-docs-12", "circle-docs-13", "circle-docs-1" ] }, { "productId": "circle", "storyId": "agent-initiated-payments", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle documents Agent wallets explicitly built to 'hold and spend USDC and other tokens with customizable spending controls and built-in compliance guardrails,' plus an agent-stack CLI and x402 pay-per-request flow that support agent-initiated payments under human-configured limits (circle-docs-6, circle-docs-7, circle-docs-8). However, the evidence lacks a concrete end-to-end documented example of an agent actually initiating a payout with a specific spend-control policy set by a human, or details on how those controls are configured/enforced. Missing for 10: a worked example/tutorial showing a human setting spend limits and an agent executing a constrained payment, independent/hands-on verification of the guardrails working in practice.", "evidenceIds": [ "circle-docs-6", "circle-docs-7", "circle-docs-8", "circle-probe-4" ] }, { "productId": "circle", "storyId": "agent-wallet-provisioning", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle documents dedicated Agent wallets with spending controls and compliance guardrails, MPC/passkey key management (no raw private key handling), and an agent CLI/MCP stack for programmatic wallet use, which directly supports the story. However, evidence lacks specifics on scoped-key issuance granularity, concrete documented limits/spend caps, or independent/hands-on validation of policy enforcement in practice. missing for 10: detailed scoped-key/permission model docs, concrete numeric spend-limit examples, independent verification that policy controls hold up in real agent usage.", "evidenceIds": [ "circle-docs-6", "circle-docs-1", "circle-docs-8", "circle-docs-9", "circle-probe-3", "circle-probe-4" ] }, { "productId": "circle", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Circle publishes a live llms.txt at developers.circle.com/llms.txt (HTTP 200, confirmed by probe) and also has an official MCP server for agent-oriented coding assistance, showing explicit support for agent-native discovery of docs. Missing for 10: independent/community corroboration of agents actually using llms.txt in practice, and no OpenAPI spec discoverable to complement it.", "evidenceIds": [ "circle-probe-1", "circle-docs-9", "circle-probe-3" ] }, { "productId": "circle", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle offers building blocks for autonomous background behavior—webhooks that react to state changes, CCTP triggers for automated actions after cross-chain transfers, and Agent wallets with spending controls—but there's no explicit documentation of a scheduler, persistent background job runner, or end-to-end 'set up and forget' automation workflow. Missing for 10: dedicated automation/scheduling API or dashboard, evidence of long-running autonomous agent execution, and independent confirmation these triggers work reliably in production.", "evidenceIds": [ "circle-docs-5", "circle-docs-6", "circle-docs-10", "circle-docs-8", "circle-probe-3" ] }, { "productId": "circle", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Circle documents an 'Agent Stack' (agent wallets, x402 payments, CLI, MCP server) for building AI agents that consume Circle's crypto rails, but this is infrastructure for third-party agents to interact with Circle—not a built-in AI assistant inside Circle's own product that a user can delegate tasks to.", "evidenceIds": [ "circle-docs-6", "circle-docs-7", "circle-docs-8", "circle-docs-9" ] }, { "productId": "circle", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle provides a CLI (circle-cli) and REST APIs for wallets, transfers, and webhooks that can be scripted programmatically, which supports headless/automated use in principle, but there is no explicit documentation of CI pipelines, service-account/API-key based non-interactive auth, or example CI workflows. missing for 10: explicit CI/headless setup guide, service-account authentication flow, and independent evidence of running the CLI/API in automated pipelines.", "evidenceIds": [ "circle-docs-8", "circle-probe-4", "circle-docs-10" ] }, { "productId": "circle", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "medium", "rationale": "Circle 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.", "evidenceIds": [ "circle-docs-9", "circle-probe-3" ] }, { "productId": "circle", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Circle documents an official MCP server that integrates with LLMs/AI-assisted IDEs to generate and fix code using Circle's Wallets, Contracts, CCTP, and Gateway offerings, confirmed by both docs and a direct probe of the live URL. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and more detail on setup/config beyond the doc description.", "evidenceIds": [ "circle-docs-9", "circle-probe-3" ] }, { "productId": "circle", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle offers an official MCP server (circle-docs-9, circle-probe-3) that lets LLMs/AI-IDEs interact with Circle's wallet/CCTP/contract APIs, and an 'agent-stack' with agent wallets and a CLI for programmatic control (circle-docs-6, circle-docs-8), suggesting some natural-language/agent-driven operability. However the MCP server is scoped to code generation/fixing rather than live natural-language command execution of transactions, and the CLI is explicitly a structured command interface, not NL-based. Missing for 10: evidence of an actual chat/NL interface for executing live operations (transfers, swaps) rather than just code generation, and independent confirmation of NL command usage in production.", "evidenceIds": [ "circle-docs-9", "circle-docs-6", "circle-docs-8", "circle-probe-3", "circle-probe-4" ] }, { "productId": "circle", "storyId": "agentic-official-cli", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Circle documents an official CLI (circle-cli) explicitly built for agentic workflows—creating/managing wallets, transferring/swapping/bridging USDC, executing smart contracts, and discovering/paying for services 'through a single command interface,' confirmed via docs and a probe. Missing for 10: independent/hands-on verification of the CLI's real-world usage or community adoption beyond first-party docs.", "evidenceIds": [ "circle-docs-8", "circle-probe-4" ] }, { "productId": "circle", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Circle's developer platform (developers.circle.com) documents extensive public APIs covering wallets, CCTP cross-chain transfers, webhooks for event-driven integration, and a CLI/MCP server that wrap the same API, all confirmed live via llms.txt probe and doc excerpts. This clearly supports AI-native users driving the product programmatically. Missing for 10: a directly reachable OpenAPI/swagger spec (probe returned 404 on all standard paths) and independent third-party confirmation of API usability.", "evidenceIds": [ "circle-docs-2", "circle-docs-3", "circle-docs-4", "circle-docs-8", "circle-docs-9", "circle-docs-10", "circle-probe-1", "circle-probe-2", "circle-probe-4" ] }, { "productId": "circle", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Circle's Agent Stack docs mention 'Agent wallets... with customizable spending controls and built-in compliance guardrails' (circle-docs-6), which implies some least-privilege control over what an agent can spend, but there is no documentation of scoped API keys, permission tiers, or credential issuance specifically for API access. Missing for 10: explicit API key/token scoping mechanism, documented permission levels for agent credentials, and any independent verification of these controls in practice.", "evidenceIds": [ "circle-docs-6", "circle-docs-8" ] }, { "productId": "circle", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence describes Circle's APIs, CLI, MCP server, and webhooks, but no item mentions official language SDKs (e.g., Node/Python/Java client libraries) for building against Circle's platform; the OpenAPI spec probe even returned 404s, suggesting no evidence of SDK generation or distribution.", "evidenceIds": [ "circle-probe-2", "circle-docs-8", "circle-docs-9" ] }, { "productId": "circle", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Circle documents webhooks that POST to a configured endpoint when resource state changes, enabling event-driven/agentic reactions to platform events. Missing for 10: details on event/topic subscription management, payload schema/signature verification docs, and independent/hands-on confirmation of reliability.", "evidenceIds": [ "circle-docs-10" ] }, { "productId": "circle", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Circle's developer docs are markdown-based (llms.txt) and reference APIs, but there's no evidence of an interactive API reference with runnable examples; probes for OpenAPI/Swagger specs that would power such a reference all returned 404.", "evidenceIds": [ "circle-probe-1", "circle-probe-2" ] }, { "productId": "circle", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The probe explicitly checked common OpenAPI spec paths (openapi.json, swagger.json, etc.) and all returned 404, indicating no downloadable machine-readable API spec is available, despite Circle having extensive API documentation. missing for 10: an actual OpenAPI/Swagger spec file accessible at a discoverable URL.", "evidenceIds": [ "circle-probe-2" ] }, { "productId": "circle", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of a sandbox/testnet environment, test API keys, or any way to develop against non-production data; all docs describe production wallet, CCTP, CLI, and MCP features without noting a separate test mode. Missing for 10: any mention of sandbox/testnet endpoints, test credentials, or documentation distinguishing sandbox vs production usage.", "evidenceIds": [] }, { "productId": "circle", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of API versioning scheme or a documented deprecation policy; the openapi.json/swagger probes all 404, and no docs mention version numbers or deprecation timelines. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog or migration guide.", "evidenceIds": [ "circle-probe-2" ] }, { "productId": "circle", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence describes individual operations (wallet creation, single transfers, CCTP transfers, webhooks) via API/CLI/MCP, but no documentation mentions batch or bulk endpoints, bulk payout processing, or multi-item operations in one call. Missing for 10: batch API endpoints, bulk transfer/payout documentation, any bulk wallet or bulk transaction management feature.", "evidenceIds": [ "circle-docs-8", "circle-docs-12", "circle-probe-4" ] }, { "productId": "circle", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle supports event-driven automation via webhooks that POST to your endpoint on state changes, CCTP's ability to trigger actions on the destination chain after assets arrive, and Agent wallets with customizable spending controls/policies — but these are developer-configured integrations, not a user-facing rules engine for defining arbitrary if/then automation. Missing for 10: a dedicated no-code/low-code rules builder, conditional logic across multiple event types, and evidence of AI-native users authoring rules themselves rather than developers wiring webhooks/paymaster policies.", "evidenceIds": [ "circle-docs-5", "circle-docs-6", "circle-docs-10" ] }, { "productId": "circle", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No 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.", "evidenceIds": [ "circle-docs-10", "circle-docs-8" ] }, { "productId": "circle", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence describes individual payout rails (CPN cross-border fiat payouts, Circle Mint USD/USDC conversion) but nowhere documents a batch or bulk payout API that processes many payouts in one call with per-item status tracking. Missing for 10: any mention of batch/bulk endpoint, multi-item payout request format, or per-item status/webhook reporting for mass disbursement runs.", "evidenceIds": [ "circle-docs-11", "circle-docs-12", "circle-docs-13" ] }, { "productId": "circle", "storyId": "custodial-stablecoin-balances", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Circle Mint is documented as a custodial USD↔USDC conversion account for 'qualified businesses' at no additional cost, which honestly signals gating, but the evidence never specifies which geographies are supported, what qualification criteria entail, or SLAs/availability guarantees. Missing for 10: stated geographic coverage, explicit eligibility/KYC requirements, and any independent or hands-on corroboration of account onboarding.", "evidenceIds": [ "circle-docs-13" ] }, { "productId": "circle", "storyId": "fiat-onramp-integration", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Circle Mint lets qualified businesses convert USD↔USDC directly (not an embeddable end-user onramp) and CPN handles cross-border fiat payouts, but no documented widget or API exists for embedding a card/bank-transfer fiat-to-stablecoin purchase flow for end users inside a third-party product.", "evidenceIds": [ "circle-docs-13", "circle-docs-11", "circle-docs-12" ] }, { "productId": "circle", "storyId": "fiat-settlement-option", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle documents both a direct USD↔USDC conversion mechanism (Circle Mint, at par, no fee) and a cross-border payments network (CPN) where partners deliver local fiat after USDC settlement, which together support a finance lead settling stablecoin receipts in fiat rather than holding crypto. However, there's no single documented 'auto-convert on receipt' checkout/payout feature purpose-built for merchants, and no independent confirmation of how seamlessly this flows into standard accounting so books never touch crypto. Missing for 10: an explicit automatic-conversion-on-payment-receipt feature, accounting/bookkeeping integration details, and independent/hands-on verification of the payout flow.", "evidenceIds": [ "circle-docs-12", "circle-docs-13", "circle-docs-11" ] }, { "productId": "circle", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle documents fiat↔USDC conversion via Circle Mint 'at no additional cost' and cross-border fiat payouts through CPN with 'real-time FX quotes' and settlement in USDC onchain, showing conversion is a core capability, but neither doc gives concrete rate/fee schedules or settlement-time SLAs, and no OpenAPI spec was found to confirm a dedicated conversion/quote endpoint (circle-probe-2 shows 404s). Missing for 10: documented fee tables, settlement-time guarantees, and a discoverable quotes/conversion API reference or independent verification of accuracy.", "evidenceIds": [ "circle-docs-12", "circle-docs-13", "circle-docs-11", "circle-probe-2" ] }, { "productId": "circle", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle's docs describe Cross-Chain Payments Network (CPN) enabling cross-border fiat payouts via partner network with real-time FX quotes and local fiat delivery, and Circle Mint for USD↔USDC conversion, matching the off-ramp story's core mechanism. However, no evidence lists a published set of specific supported currencies or countries, nor does it detail settlement timelines or bank-transfer specifics that an ops lead would need to plan payouts. Missing for 10: a published currency/country coverage list, settlement SLAs, and independent confirmation of real-world payout success.", "evidenceIds": [ "circle-docs-11", "circle-docs-12", "circle-docs-13" ] }, { "productId": "circle", "storyId": "kyc-onboarding-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers wallets, gas sponsorship, CCTP, agent wallets, CLI/MCP, and Circle Mint onboarding, but nowhere documents KYC/KYB endpoints or programmatic counterparty clearance flows before money moves. 'Qualified businesses can apply for a Circle Mint account' implies manual vetting, not a documented API-driven onboarding flow. missing for 10: documented KYC/KYB API endpoints, programmatic counterparty verification/clearance flow, any compliance-status check before transfer.", "evidenceIds": [ "circle-docs-13", "circle-docs-11" ] }, { "productId": "circle", "storyId": "machine-payment-protocols", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Circle explicitly documents x402 support ('Search x402-compatible APIs and pay per request, without subscriptions or API keys') as part of its Agent Stack, with SDK/CLI and MCP server tooling for agents to discover and pay for services. However, ACP, MPP, and AP2 are not mentioned anywhere in the evidence, and no dedicated x402 endpoint/OpenAPI spec is exposed (openapi probe 404s), leaving the protocol claim documented only at a feature-description level rather than full technical spec. Missing for 10: explicit ACP/MPP/AP2 support or endpoints, and a concrete x402 API reference/OpenAPI schema beyond prose description.", "evidenceIds": [ "circle-docs-7", "circle-docs-6", "circle-docs-8", "circle-docs-9", "circle-probe-2" ] }, { "productId": "circle", "storyId": "multi-chain-support", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs confirm USDC (and EURC via CCTP) support and mention cross-chain transfers, but the evidence pack never lists specific named chains/networks or explicitly names USDT or other peer stablecoins as supported. missing for 10: an explicit supported-chains matrix, explicit USDT/other stablecoin support confirmation, and a consolidated asset-network compatibility table.", "evidenceIds": [ "circle-docs-4", "circle-docs-13", "circle-probe-1" ] }, { "productId": "circle", "storyId": "no-node-integration", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle's docs clearly show infrastructure abstraction — no raw key management, gas sponsorship via credit card, USDC-based gas payment, and automated cross-chain triggers — meaning developers don't operate blockchain nodes or handle gas directly (circle-docs-1, circle-docs-2, circle-docs-3, circle-docs-5). However, there's no direct evidence of a conventional REST API description or client libraries in specific languages, and a probe for a discoverable OpenAPI spec returned 404s across all candidate paths, weakening confidence in a standard REST/SDK developer experience. Missing for 10: explicit REST API documentation with endpoint/method examples, evidence of client libraries (SDKs) in specific languages, and a working OpenAPI/swagger spec.", "evidenceIds": [ "circle-docs-1", "circle-docs-2", "circle-docs-3", "circle-docs-5", "circle-probe-2" ] }, { "productId": "circle", "storyId": "openness-api-parity", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Circle's docs show extensive API surface (Wallets, CCTP, Agent Wallets, CPN, webhooks) and even a CLI/MCP server built atop that API, suggesting API-first design, but no evidence explicitly confirms full UI/console parity, and the openapi spec probe returned 404s in all attempted locations, undermining verifiable completeness. missing for 10: explicit statement of API/UI feature parity, a discoverable OpenAPI spec, and independent confirmation that console-only features (e.g., dashboard settings) are also API-accessible.", "evidenceIds": [ "circle-docs-8", "circle-docs-9", "circle-docs-10", "circle-probe-2", "circle-probe-4" ] }, { "productId": "circle", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "payment-webhooks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle's docs confirm a webhook system that POSTs to a configured endpoint when a resource changes state, which supports async state tracking without polling — but the evidence never mentions signing/signature verification of webhooks, nor explicitly lists event types like 'payment confirmed', 'payout settled', or 'conversion executed'. missing for 10: documentation of webhook signature/verification mechanism, explicit enumeration of event types matching payments/payouts/conversions, and any independent confirmation of webhook reliability in production.", "evidenceIds": [ "circle-docs-10", "circle-docs-12", "circle-docs-13" ] }, { "productId": "circle", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data retention or deletion controls for AI-native users—no docs on data export, deletion policies, or retention settings; the community items concern reserve/treasury management, not data privacy.", "evidenceIds": [] }, { "productId": "circle", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Circle 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.", "evidenceIds": [] }, { "productId": "circle", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no published list of Circle's licensed/registered entities or the jurisdictions they cover — only product/API docs and community commentary on SVB reserve issues, none of which addresses corporate/legal entity transparency.", "evidenceIds": [] }, { "productId": "circle", "storyId": "reserve-yield-programs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation of USDC reserve composition, attestation reports, or any yield/rewards program with eligibility and regulatory caveats — the docs items only cover developer platform features (wallets, CCTP, agent stack, Circle Mint conversion). Community items discuss a 2023 SVB reserve incident but do not constitute or corroborate ongoing published reserve/attestation documentation.", "evidenceIds": [ "circle-docs-13", "circle-comm-1", "circle-comm-3" ] }, { "productId": "circle", "storyId": "sanctions-travel-rule", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains only a generic mention of 'built-in compliance guardrails' for agent wallets, with no naming of sanctions screening, wallet risk checks, or travel-rule handling as specific mechanisms. As a regulated stablecoin/payments platform, this axis clearly applies, but no documentation evidence names these specific compliance processes.", "evidenceIds": [ "circle-docs-6" ] }, { "productId": "circle", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Circle Mint conversion and CPN payouts exist, and webhooks notify on state changes, but there is no documented timing from payment to available balance, no published fee schedule per rail, and no mention of statements or accounting-consumable reports. The SVB/reserve community items are off-topic to settlement legibility and are excluded.", "evidenceIds": [] }, { "productId": "circle", "storyId": "stablecoin-issuance", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Circle Mint (converting USD↔existing USDC) and CPN (a self-managed model where the founder—not Circle—handles custody, payouts, and compliance for their own stablecoin lifecycle), but nothing documents a Circle-hosted white-label issuance product covering minting, redemption, and reserve management for a founder's own branded coin, nor any honest disclosure of eligibility gating for such a product.", "evidenceIds": [ "circle-docs-11", "circle-docs-13" ] }, { "productId": "circle", "storyId": "stablecoin-payouts", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle's docs show programmatic USDC transfers via Wallets APIs, cross-border fiat payouts through CPN with real-time FX quotes and onchain USDC settlement, and webhook-based state-change notifications that could serve as status tracking. However, there's no explicit documentation of a 'stored recipient' object/API or a full payout status lifecycle (e.g., enumerated states from initiated to settled), and no independent/hands-on corroboration of payout completion. Missing for 10: stored-recipient management API, explicit payout status enumeration/lifecycle docs, and third-party verification of end-to-end payout settlement.", "evidenceIds": [ "circle-docs-11", "circle-docs-12", "circle-docs-10", "circle-docs-1", "circle-docs-2" ] }, { "productId": "circle", "storyId": "testnet-sandbox", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item documents a sandbox/testnet mode, test values, or deterministic test environments for payments, payouts, or conversions; the docs describe live features (CCTP, wallets, payouts, Circle Mint) without mentioning any test/sandbox mode. missing for 10: documented sandbox or testnet environment, test API keys/values, deterministic test behavior for payments/payouts/conversions.", "evidenceIds": [] }, { "productId": "circle", "storyId": "treasury-rebalancing", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Circle Mint lets qualified businesses convert USD to/from USDC (circle-docs-13), and CPN documents cross-border fiat payouts settled in USDC (circle-docs-12), showing fiat↔stablecoin movement is supported. However, evidence lacks concrete API reference detail or dashboard walkthrough for internal transfers/rebalancing as a documented end-to-end flow — missing for 10: explicit API endpoints/parameters for fiat-stablecoin conversion, dashboard UI documentation, and independent confirmation of the rebalancing workflow.", "evidenceIds": [ "circle-docs-13", "circle-docs-12", "circle-docs-11" ] }, { "productId": "circle", "storyId": "virtual-accounts-addressing", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items describe named virtual accounts or dedicated per-customer deposit addresses for automated payment attribution/reconciliation; docs cover wallets, gas sponsorship, CCTP, webhooks, and payouts but nothing about per-customer deposit address issuance or account matching. Missing for 10: documentation of per-customer virtual account/deposit address creation, evidence of automatic incoming-payment-to-customer matching, and any reconciliation tooling tied to those addresses.", "evidenceIds": [] }, { "productId": "circle", "storyId": "wallet-provisioning-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Circle's docs confirm programmatic wallet creation with MPC/passkey-based key custody (no raw private key management for developers), and Agent wallets for per-purpose/per-customer use cases with spending controls, plus webhooks for wallet state changes. However, there's no direct documentation snippet showing explicit API endpoints for deposit address provisioning per customer, and the openapi/API reference spec itself is not accessible (404s), limiting verification of exact wallet-creation API semantics. Missing for 10: explicit API reference for wallet/deposit-address creation endpoints, clearer documentation of per-customer wallet architecture, and independent/hands-on corroboration of custody claims.", "evidenceIds": [ "circle-docs-1", "circle-docs-6", "circle-docs-10", "circle-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "accept-stablecoin-checkout", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Docs describe a full checkout/payment-acceptance flow: provisioning stable onchain addresses that auto-credit a custodial account, a two-step auth/capture checkout API with developer control over auth timing, partial captures and voids, plus migration guidance from the older Commerce Charge API to the newer Checkouts API with settlement details. This covers create-payment, present-address/flow, and confirm-settlement programmatically. Missing for 10: no independent/hands-on developer confirmation of the checkout flow working end-to-end, and no concrete code sample or OpenAPI spec (probe found openapi.json 404) showing the settlement confirmation call.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-4", "coinbase-payments-docs-9", "coinbase-payments-docs-11", "coinbase-payments-docs-19", "coinbase-payments-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "agent-initiated-payments", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "CDP documents agent-native payment flows: x402 lets agents pay for or charge APIs programmatically, and the Wallet MCP lets an AI assistant check balances, send funds and pay via a connected Coinbase Wallet, backed by CDP-managed key custody. However, the pack shows no explicit documentation of human-configured spend limits, allowances, or scoped permission policies constraining what an agent can autonomously spend — the closest control language ('you control auth, capture timing, partial captures, voids') applies to merchant checkout capture, not agent wallet spend caps. missing for 10: documented spend-limit/allowance configuration APIs, explicit human-set policy controls for agent wallets, and independent/hands-on confirmation of scoped-authority enforcement.", "evidenceIds": [ "coinbase-payments-docs-6", "coinbase-payments-docs-12", "coinbase-payments-docs-13", "coinbase-payments-docs-18", "coinbase-payments-gh-1", "coinbase-payments-docs-17" ] }, { "productId": "coinbase-payments", "storyId": "agent-wallet-provisioning", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "CDP provides SDK-based wallet issuance where Coinbase secures private keys (coinbase-payments-gh-1) and exposes wallets to AI agents via MCP (coinbase-payments-docs-18) and x402 payments (coinbase-payments-docs-12/13), showing agents can hold and use funds programmatically. However, the evidence never documents scoped keys, granular policy controls, or explicit spend/limit enforcement mechanisms for agent-held wallets—only general custody and signing features. Missing for 10: explicit policy/permission engine docs, documented per-agent spend limits, and independent verification that agents cannot exceed defined bounds.", "evidenceIds": [ "coinbase-payments-gh-1", "coinbase-payments-docs-18", "coinbase-payments-docs-12", "coinbase-payments-docs-13", "coinbase-payments-docs-17" ] }, { "productId": "coinbase-payments", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Probe confirms llms.txt is live (HTTP 200) at docs.cdp.coinbase.com, listing 538 pages of docs, and multiple docs entries are directly sourced from that llms.txt, showing agent-oriented documentation is real and accessible. Missing for 10: no independent third-party report of an agent successfully consuming llms.txt to complete a task.", "evidenceIds": [ "coinbase-payments-probe-1", "coinbase-payments-docs-19", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Coinbase Payments (CDP) is a payments/wallet infrastructure platform, not a data analytics or insights product; the evidence covers payment rails, MCP/AI-agent connectivity, and webhooks but nothing about surfacing AI-generated insights or suggestions from a user's own data inside the product. This story is a category error for this type of product.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP provides building blocks for autonomous background automation—webhooks for event-driven triggers, auto-liquidation/auto-convert on incoming payments, x402 for agent-to-agent programmatic payments, and an MCP server exposing all API endpoints as tools for AI agents to call—which together let developers wire up unattended, background-running payment flows. However, this is a set of APIs/SDKs and integration primitives rather than a hosted, first-party autonomous automation/orchestration runtime that runs itself; the user must build and host the actual automation logic. Missing for 10: evidence of a native scheduler or persistent agent-runtime service, and independent/hands-on confirmation that these pieces compose into a working autonomous background automation.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-6", "coinbase-payments-docs-12", "coinbase-payments-docs-13", "coinbase-payments-docs-15", "coinbase-payments-docs-16", "coinbase-payments-docs-17", "coinbase-payments-docs-18" ] }, { "productId": "coinbase-payments", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP offers SDKs and a CLI (with an MCP server exposing every API endpoint as a tool) that can be scripted headlessly for automation and CI, and its API-first design (webhooks, x402, wallet SDKs) supports programmatic/agentic use. However, there's no explicit documentation of CI-specific patterns (e.g., service-account auth for pipelines, GitHub Actions examples, or headless auth flows without browser/UI steps). missing for 10: explicit CI/headless authentication guidance, CI pipeline examples, independent confirmation of non-interactive operation.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-gh-1", "coinbase-payments-probe-4", "coinbase-payments-docs-15" ] }, { "productId": "coinbase-payments", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "medium", "rationale": "Coinbase Payments (CDP) is a payments/API infrastructure platform, not an AI agent or assistant that consumes external tools; the evidence shows it operates in the opposite direction — CDP exposes itself AS an MCP server (cdp mcp, Wallet MCP) for other AI agents to use its payment tools, not the reverse. The story asks whether this product can plug in and use others' MCP servers, which is a client/agent-role capability that doesn't fit a payments backend's category.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-docs-18", "coinbase-payments-probe-3" ] }, { "productId": "coinbase-payments", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Coinbase Payments (CDP) ships an official MCP server via the CDP CLI (`cdp mcp`) exposing every API endpoint as a tool, plus a separate Coinbase Wallet MCP for AI agent wallet actions, both documented and probe-confirmed. missing for 10: independent/hands-on third-party corroboration beyond first-party docs and probes.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-docs-18", "coinbase-payments-probe-3" ] }, { "productId": "coinbase-payments", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP exposes an MCP server (`cdp mcp`) that surfaces every API endpoint as a tool, and Coinbase Wallet MCP lets an AI assistant check balances, send funds, swap tokens, and pay with x402 — enabling natural-language operation via an MCP-compatible AI client. However, this requires a separate AI client/agent host to interpret NL commands; there's no evidence of a built-in chat/NL interface within CDP itself, no independent hands-on validation of the MCP tool coverage, and no examples of complex NL command sequences being executed reliably. missing for 10: first-party or independent demonstration of end-to-end natural-language command execution, evidence of NL interface beyond MCP tool exposure, and confirmation of reliability/robustness of the MCP tool-calling across the full API surface.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-docs-18", "coinbase-payments-probe-3", "coinbase-payments-probe-4" ] }, { "productId": "coinbase-payments", "storyId": "agentic-official-cli", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "CDP ships an official CLI that also includes an MCP server (`cdp mcp`) exposing every API endpoint as a tool, and docs explicitly reference using the CDP CLI for treasury/payout workflows, directly supporting AI-native/agentic use. Missing for 10: independent hands-on verification of CLI usage and richer documentation of CLI command coverage beyond MCP exposure.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-docs-19", "coinbase-payments-docs-20", "coinbase-payments-probe-4" ] }, { "productId": "coinbase-payments", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "CDP exposes a documented public API/SDK covering wallets, payments, onramp, x402, and webhooks, with client libraries (cdp-sdk) and an explicit CLI/MCP server (`cdp mcp`) exposing every API endpoint as a tool for AI-native workflows. missing for 10: a discoverable OpenAPI/swagger spec (probe found all candidate paths 404), and independent third-party corroboration beyond vendor docs.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-gh-1", "coinbase-payments-probe-2", "coinbase-payments-probe-4", "coinbase-payments-docs-6" ] }, { "productId": "coinbase-payments", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack describes CDP's payment features, wallets, webhooks, and an MCP/CLI surface for agents, but nowhere documents scoped or least-privilege API key/credential issuance (e.g., permission-limited API keys, role-based scopes, or agent-specific credential restrictions). Missing for 10: any mention of API key scopes/permissions, credential restriction mechanisms, or least-privilege agent authentication documentation.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "agentic-sdks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Coinbase Payments provides official client SDKs (cdp-sdk on GitHub for EVM/Solana wallets), plus CLI and MCP server tooling explicitly aimed at AI-native/agentic use (x402 payments, MCP for AI assistants, wallet-per-agent support), all documented first-party. Missing for 10: independent/third-party corroboration of SDK quality and a public OpenAPI spec (probe found openapi.json 404s), which would strengthen developer trust.", "evidenceIds": [ "coinbase-payments-gh-1", "coinbase-payments-docs-17", "coinbase-payments-docs-18", "coinbase-payments-docs-12", "coinbase-payments-docs-13", "coinbase-payments-probe-3", "coinbase-payments-probe-4" ] }, { "productId": "coinbase-payments", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs explicitly describe webhooks for real-time HTTP notifications on CDP integration events, including multi-address wallet activity subscriptions, which fits the ai-native agenticness theme of event-driven automation. Missing for 10: independent/hands-on confirmation of webhook reliability and no explicit event-type catalog or signature-verification detail in evidence.", "evidenceIds": [ "coinbase-payments-docs-15", "coinbase-payments-docs-16" ] }, { "productId": "coinbase-payments", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "There is no evidence of an interactive API reference with runnable examples; the OpenAPI spec probe returned 404s on all candidate paths, and no docs mention interactive playgrounds or executable code snippets. Missing for 10: interactive API reference UI, runnable/executable examples, OpenAPI/Swagger spec availability.", "evidenceIds": [ "coinbase-payments-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "A direct probe for common OpenAPI spec paths returned 404s, and no evidence pack item links to a downloadable machine-readable API spec; only an llms.txt docs index and MCP/CLI tooling are documented, which are not equivalent to an OpenAPI spec.", "evidenceIds": [ "coinbase-payments-probe-2", "coinbase-payments-probe-1" ] }, { "productId": "coinbase-payments", "storyId": "api-sandbox", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs explicitly describe a Sandbox as 'a fully isolated testing environment for custodial features without connecting real funds,' directly matching the story. However, evidence doesn't clarify sandbox coverage for non-custodial/onchain, x402, or webhook features, nor provide hands-on confirmation of the isolation guarantee. Missing for 10: independent/hands-on verification of sandbox isolation, detail on which product areas are sandbox-covered vs not, and any test-data seeding or reset tooling.", "evidenceIds": [ "coinbase-payments-docs-8" ] }, { "productId": "coinbase-payments", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes 404'd and none of the docs mention version numbers, sunset timelines, or deprecation notices.", "evidenceIds": [ "coinbase-payments-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The only concrete bulk-scale capability is watching up to 100 wallet addresses under one webhook subscription (`wallet.activity.multi`); all other documented operations (send payouts, provision addresses, checkout, onramp) are described as single-item flows with no batch/bulk endpoints shown. Missing for 10: bulk payout/disbursement APIs, batch transaction submission, bulk provisioning of addresses, and any explicit multi-item automation beyond webhook address watching.", "evidenceIds": [ "coinbase-payments-docs-16", "coinbase-payments-docs-3", "coinbase-payments-docs-15" ] }, { "productId": "coinbase-payments", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "CDP offers event-driven building blocks — webhooks for real-time notifications on wallet/payment activity, and built-in auto-liquidation/auto-convert triggered on fund receipt — that let a developer wire up automation, but there is no documented user-facing rules engine where an AI-native user declaratively defines 'if event X then action Y' logic; the developer must write the handling logic themselves. missing for 10: a declarative rules/automation engine, conditional logic support, or evidence of no-code rule definitions tied to webhook events.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-15", "coinbase-payments-docs-16", "coinbase-payments-docs-19", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of scheduling, cron-like recurrence, or workflow orchestration features in Coinbase Payments/CDP docs; the pack covers payments, payouts, webhooks, MCP/CLI tooling but nothing about recurring jobs or automated scheduling.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of versioning, review, or rollback mechanisms for automations/workflows built on CDP; the docs cover payment rails, wallets, webhooks, and MCP/CLI tools but nothing about tracking or reverting automation configurations.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence confirms CDP supports sending fiat/crypto payouts from a custodial account and paying USDC onchain to any wallet, but nothing in the pack documents a batch or bulk payout API, a single-call multi-payee operation, or per-item status reporting for mass disbursements.", "evidenceIds": [ "coinbase-payments-docs-2", "coinbase-payments-docs-3", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "custodial-stablecoin-balances", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Docs confirm custodial accounts that hold stablecoin balances (auto-credited addresses, auto-conversion to USD, treasury funding/payout in USDC) — docs-1, docs-19, docs-20 — but nothing in the evidence pack states availability constraints, supported geographies, or KYC/eligibility gating for opening such an account. Missing for 10: documented geographic availability/restrictions, explicit KYC/onboarding gating disclosure, and any stated balance limits or custody terms.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-19", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "fiat-onramp-integration", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Coinbase Payments docs explicitly describe an Onramp letting end users buy crypto/stablecoins with card, Apple Pay, Google Pay, or Coinbase account delivered to a wallet, plus a Sandbox for isolated testing — matching the embedded fiat-to-stablecoin onramp story. Missing for 10: no widget code sample or explicit UI-embedding snippet shown, and no independent/hands-on corroboration beyond first-party docs.", "evidenceIds": [ "coinbase-payments-docs-5", "coinbase-payments-docs-8", "coinbase-payments-docs-14" ] }, { "productId": "coinbase-payments", "storyId": "fiat-settlement-option", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Docs explicitly describe auto-crediting custodial accounts with optional auto-liquidation, accepting USDC and auto-converting to USD into a treasury, and sending fiat payouts via ACH/Fedwire/Swift/SEPA — directly matching the finance-lead's request to settle crypto receipts in fiat and avoid holding crypto on the books. Missing for 10: independent/hands-on verification of the auto-liquidation flow in production, and clearer accounting/reconciliation documentation for finance teams.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-2", "coinbase-payments-docs-19", "coinbase-payments-docs-14" ] }, { "productId": "coinbase-payments", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "CDP docs show real conversion capabilities (auto-liquidation of onchain funds to fiat, USDC-to-USD auto-conversion into treasury, and converting crypto earnings to fiat) via docs-1, docs-14, docs-19, docs-20, indicating conversion is treated as a core, documented capability rather than a side effect. However, there's no evidence of a distinct quote endpoint, or documented exchange rates, fee schedules, or settlement-time SLAs for these conversions. Missing for 10: explicit quote API, documented conversion fee tables, documented settlement-time guarantees, stablecoin-to-stablecoin conversion documentation.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-14", "coinbase-payments-docs-19", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm off-ramp functionality — converting stablecoins/USDC to fiat and depositing to bank accounts via ACH, Fedwire, Swift, and SEPA rails (docs-2, docs-14, docs-19) — implying multi-currency support (USD, EUR, GBP) across supported regions. However, no evidence provides a published, explicit list of supported currencies or countries, which the story specifically asks for. Missing for 10: an explicit published table/list of supported countries and currencies, and independent confirmation of real-world payout coverage.", "evidenceIds": [ "coinbase-payments-docs-2", "coinbase-payments-docs-14", "coinbase-payments-docs-19", "coinbase-payments-docs-3" ] }, { "productId": "coinbase-payments", "storyId": "kyc-onboarding-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack items mention KYC/KYB endpoints, counterparty verification, or onboarding flows to clear senders/recipients before funds move; docs cover payment rails, wallets, checkouts, webhooks, and stablecoins but nothing about identity/compliance verification APIs.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "machine-payment-protocols", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "CDP has dedicated x402 docs with SDK/endpoints for both paying (\"Pay for an API or resource with x402 and the CDP SDK\") and charging (\"Charge for your endpoints with x402 and the CDP SDK\"), plus a Coinbase Wallet MCP server enabling agents to pay with x402, and an official CDP CLI/MCP exposing API endpoints as tools — this is concrete named-protocol support with SDKs/endpoints, not just aspirational blog content. Missing for 10: no explicit ACP/MPP/AP2 protocol mentions, so coverage is limited to x402 among the named protocols.", "evidenceIds": [ "coinbase-payments-docs-12", "coinbase-payments-docs-13", "coinbase-payments-docs-17", "coinbase-payments-docs-18", "coinbase-payments-probe-3", "coinbase-payments-probe-4" ] }, { "productId": "coinbase-payments", "storyId": "multi-chain-support", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Docs repeatedly reference USDC support (auto-convert customer USDC, USD treasury payouts in USDC, custom stablecoins backed by USDC) and mention EVM/Solana wallet support, but there is no explicit enumeration of USDT or other stablecoins, nor a clear list of supported chains/networks a developer could match against customer holdings. Missing for 10: explicit multi-stablecoin coverage (USDT, DAI, etc.), a documented list of supported blockchain networks, and any independent confirmation of chain/stablecoin breadth.", "evidenceIds": [ "coinbase-payments-docs-10", "coinbase-payments-docs-19", "coinbase-payments-docs-20", "coinbase-payments-gh-1" ] }, { "productId": "coinbase-payments", "storyId": "no-node-integration", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP provides a REST API plus client SDKs (cdp-sdk on GitHub for EVM/Solana wallets) that abstract key management, signing, and broadcasting, and custodial payment features (stable addresses, payouts, checkout) explicitly avoid onchain complexity for the developer. However, some flows (non-custodial send, wallet management) still expose wallet/chain concepts like signing and gas isn't fully hidden everywhere, and no OpenAPI spec was found (probe 404s) suggesting API conventionality is asserted but not independently verifiable, and multi-language client library breadth is unconfirmed beyond the single GitHub SDK repo. Missing for 10: verifiable OpenAPI/REST spec, evidence of multiple language SDKs, and confirmation gas/chain mechanics are fully invisible across all product surfaces.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-4", "coinbase-payments-docs-7", "coinbase-payments-gh-1", "coinbase-payments-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "openness-api-parity", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "CDP's docs show extensive API/SDK/CLI coverage across virtually all payment features (onramp, offramp, checkout, payouts, custom stablecoins, x402, webhooks, treasury), and the CDP CLI even ships an MCP server exposing every API endpoint as a tool, indicating near-total API/CLI parity with any dashboard UI. Missing for 10: no explicit UI-vs-API feature parity statement and no discoverable OpenAPI spec (probe returned 404s for common spec paths), so full completeness/discoverability can't be fully confirmed.", "evidenceIds": [ "coinbase-payments-docs-17", "coinbase-payments-docs-19", "coinbase-payments-docs-20", "coinbase-payments-probe-2", "coinbase-payments-probe-4" ] }, { "productId": "coinbase-payments", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of data export/portability features or account-closure/data-takeout tooling in open formats; evidence covers payments, wallets, MCP/CLI integration but nothing about exporting user data or leaving the platform with it.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Coinbase Payments (CDP) is a closed commercial API/SDK platform; there is a GitHub repo for client SDKs but no evidence of the core product/service source being available under an open license, and no license information is cited. Evidence only shows client library repos and docs, not the underlying platform source.", "evidenceIds": [ "coinbase-payments-gh-1" ] }, { "productId": "coinbase-payments", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Coinbase Payments (CDP) is a managed custodial/cloud platform for payments and wallet infrastructure that relies on Coinbase-operated custody, compliance, and settlement rails; self-hosting the core product is not a coherent option for this category of service.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "payment-webhooks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "CDP docs confirm a webhooks system delivering 'real-time HTTP notifications when things happen across your CDP integration' and wallet-activity subscriptions, which supports state-tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed, nor does it enumerate the specific events named in the story (payment confirmed, payout settled, conversion executed) — it only shows generic notification and wallet-activity events. Missing for 10: explicit signature/verification mechanism documentation, and confirmation of payment/payout/conversion-specific event types.", "evidenceIds": [ "coinbase-payments-docs-15", "coinbase-payments-docs-16" ] }, { "productId": "coinbase-payments", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions data residency, regional storage options, or data locality controls for Coinbase Payments/CDP; the docs focus entirely on payment rails, wallets, and AI-agent commerce features.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Coinbase Payments is a crypto/fiat payments API platform, not an AI model or data-processing service; opting out of AI training data usage is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items address data retention policies, data deletion controls, or privacy/data-lifecycle settings for AI-native users; all documentation covers payments, wallets, and MCP/CLI integration rather than data governance.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for CDP Payments; the documentation covers payment features, wallets, and AI/MCP integration but is silent on data collection controls.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item discloses the specific licensed/registered legal entities behind Coinbase Payments products or the jurisdictions/licenses they operate under; all evidence is product/API documentation with no legal-entity or licensing disclosure page cited.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "reserve-yield-programs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers custom stablecoin issuance backed 1:1 by USDC with Coinbase managing issuance/redemption/reserves, but no documentation of reserve composition, attestations, or yield/rewards eligibility and regulatory caveats for finance leads is present.", "evidenceIds": [ "coinbase-payments-docs-10" ] }, { "productId": "coinbase-payments", "storyId": "sanctions-travel-rule", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack lists payment, wallet, onramp, and MCP features but never names sanctions screening, wallet risk scoring, or travel-rule handling as documented compliance machinery; these terms simply do not appear anywhere in the pack.", "evidenceIds": [] }, { "productId": "coinbase-payments", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers payment rails, payouts, checkouts, and treasury flows, but there is no documented settlement-timing SLA per rail, no published fee schedule, and no mention of accounting-consumable statements or reports. The only 'settlement details' reference is a vague migration note with no actual content shown.", "evidenceIds": [ "coinbase-payments-docs-9", "coinbase-payments-docs-2", "coinbase-payments-docs-3" ] }, { "productId": "coinbase-payments", "storyId": "stablecoin-issuance", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Coinbase's docs explicitly describe a custom-stablecoin issuance product ('Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves'), directly matching the story's core ask. However, the evidence pack contains no detail on eligibility/gating requirements, application process, minimum volume, or any independent corroboration of how the program actually works in practice. Missing for 10: honest disclosure of gating/eligibility requirements, independent/hands-on corroboration, and technical detail on minting/redemption mechanics beyond the single overview line.", "evidenceIds": [ "coinbase-payments-docs-10" ] }, { "productId": "coinbase-payments", "storyId": "stablecoin-payouts", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm programmatic stablecoin payouts to wallet addresses (fund a USD treasury and pay out USDC onchain to any wallet, or send payouts/disbursements in fiat or crypto from a custodial account) plus webhook-based status notifications for tracking events. However, there's no evidence of a 'stored recipient' concept, no detailed settlement-status API docs (e.g., payout lifecycle states), and no OpenAPI spec was found (probe-2 returned 404s) to confirm the full request/response tracking flow. Missing for 10: stored-recipient/beneficiary management, explicit payout status/settlement lifecycle documentation, and independent corroboration of end-to-end settlement tracking.", "evidenceIds": [ "coinbase-payments-docs-3", "coinbase-payments-docs-20", "coinbase-payments-docs-7", "coinbase-payments-docs-15", "coinbase-payments-docs-16", "coinbase-payments-probe-2" ] }, { "productId": "coinbase-payments", "storyId": "testnet-sandbox", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Coinbase documents a dedicated Sandbox as a fully isolated testing environment for custodial features without real funds, which covers payments-type scenarios. However, evidence doesn't confirm sandbox/testnet coverage extends deterministically to payouts and conversions specifically, nor describe deterministic test values/behaviors. Missing for 10: explicit documentation of testnet/sandbox coverage for payouts and conversions flows, description of deterministic test value behavior, and independent/hands-on confirmation of sandbox reliability.", "evidenceIds": [ "coinbase-payments-docs-8" ] }, { "productId": "coinbase-payments", "storyId": "treasury-rebalancing", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP docs describe multiple building blocks for fiat↔stablecoin movement: auto-liquidation of onchain funds into a custodial account, fiat payouts via ACH/Fedwire/Swift/SEPA, converting crypto earnings to fiat, and treasury funding/payout flows (fund USD treasury, pay out USDC onchain) via CLI/SDK. This covers most of the 'rebalancing' story but is spread across separate features rather than a single documented end-to-end internal transfer/rebalancing workflow, and there is no dashboard evidence for these treasury operations (only API/CLI/SDK). Missing for 10: a unified internal transfer ledger view, dashboard-based rebalancing UI, and independent/hands-on confirmation of the full fiat↔stablecoin loop.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-2", "coinbase-payments-docs-3", "coinbase-payments-docs-14", "coinbase-payments-docs-19", "coinbase-payments-docs-20" ] }, { "productId": "coinbase-payments", "storyId": "virtual-accounts-addressing", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "CDP docs explicitly describe provisioning 'stable onchain addresses' that auto-credit a custodial account (dedicated deposit addresses), and webhooks can watch up to 100 wallet addresses per subscription, which supports per-customer address-based reconciliation. However, there's no explicit documentation of named virtual accounts for fiat, nor clear guidance on mapping addresses to specific customer IDs for reconciliation workflows. Missing for 10: explicit per-customer/customer-ID tagging or named virtual account docs, fiat-side dedicated account numbers, and independent/hands-on confirmation of reconciliation accuracy at scale.", "evidenceIds": [ "coinbase-payments-docs-1", "coinbase-payments-docs-16", "coinbase-payments-docs-19" ] }, { "productId": "coinbase-payments", "storyId": "wallet-provisioning-api", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "CDP SDK docs confirm programmatic wallet creation for EVM/Solana with CDP securing private keys, plus provisioning of custodial onchain deposit addresses that auto-credit accounts, and a sandbox for testing wallet features without real funds. However, the pack lacks explicit detail on per-customer/multi-tenant wallet architecture or deeper key-custody semantics beyond high-level statements. missing for 10: detailed per-customer wallet provisioning patterns, explicit key custody/security model documentation (MPC, backups, exportability)", "evidenceIds": [ "coinbase-payments-gh-1", "coinbase-payments-docs-1", "coinbase-payments-docs-7", "coinbase-payments-docs-8" ] }, { "productId": "moonpay", "storyId": "accept-stablecoin-checkout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "agent-initiated-payments", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-docs-6", "moonpay-probe-3", "moonpay-docs-14", "moonpay-docs-15" ] }, { "productId": "moonpay", "storyId": "agent-wallet-provisioning", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-probe-1", "moonpay-docs-19", "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay 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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-headless", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "moonpay-docs-3", "moonpay-docs-13", "moonpay-docs-14", "moonpay-docs-15" ] }, { "productId": "moonpay", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay 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.", "evidenceIds": [ "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "agentic-public-api", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-11", "moonpay-docs-13", "moonpay-probe-2", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-docs-15", "moonpay-docs-6", "moonpay-probe-3" ] }, { "productId": "moonpay", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-3", "moonpay-docs-7", "moonpay-docs-14", "moonpay-docs-15", "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-11", "moonpay-docs-12" ] }, { "productId": "moonpay", "storyId": "api-interactive-docs", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-7", "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-probe-2", "moonpay-docs-14", "moonpay-docs-15" ] }, { "productId": "moonpay", "storyId": "api-sandbox", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-13", "moonpay-docs-7", "moonpay-docs-15" ] }, { "productId": "moonpay", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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).", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-11", "moonpay-docs-12" ] }, { "productId": "moonpay", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay is a fiat-crypto on/off-ramp payments API, not a workflow/job orchestration or automation platform; scheduling recurring jobs is outside its product category.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay is a fiat-to-crypto payment/on-ramp API product, not an automation/workflow builder; there is no concept of 'automations' to version, review, or roll back in its evidence pack.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-17", "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "custodial-stablecoin-balances", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-1", "moonpay-docs-16", "moonpay-docs-17", "moonpay-docs-18" ] }, { "productId": "moonpay", "storyId": "fiat-onramp-integration", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-docs-2", "moonpay-docs-3", "moonpay-docs-8", "moonpay-docs-9", "moonpay-docs-11", "moonpay-docs-13", "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-16" ] }, { "productId": "moonpay", "storyId": "fiat-settlement-option", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "moonpay-docs-17", "moonpay-docs-3", "moonpay-docs-11", "moonpay-docs-14" ] }, { "productId": "moonpay", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-12", "moonpay-docs-18", "moonpay-docs-11" ] }, { "productId": "moonpay", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-3", "moonpay-docs-17", "moonpay-docs-12", "moonpay-docs-11" ] }, { "productId": "moonpay", "storyId": "kyc-onboarding-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-1", "moonpay-docs-2", "moonpay-docs-4", "moonpay-docs-15", "moonpay-docs-20", "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "machine-payment-protocols", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "multi-chain-support", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "no-node-integration", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-3", "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-11", "moonpay-probe-2" ] }, { "productId": "moonpay", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-3", "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-11", "moonpay-docs-9", "moonpay-docs-10", "moonpay-probe-2", "moonpay-comm-2" ] }, { "productId": "moonpay", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "MoonPay stores user KYC and transaction data (moonpay-docs-20) but the evidence pack contains no mention of any data export feature, open-format download, or account portability/deletion tooling for end users.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay is a closed commercial fintech API/widget product, not an open-source codebase; source availability under an open license is not an applicable axis for this kind of product.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay is a hosted fiat-crypto payment/compliance SaaS, not open-source software; self-hosting the core payment/KYC infrastructure is not a fair or offered axis for this category of product.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "payment-webhooks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-11", "moonpay-docs-12" ] }, { "productId": "moonpay", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "MoonPay is a crypto payment on-ramp/off-ramp provider, not an AI model or AI-training data controller; opting out of AI-training data usage is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of any telemetry/usage-tracking opt-out mechanism or privacy controls for AI-native users; documentation covers payments, KYC, and integration features only.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "reserve-yield-programs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "sanctions-travel-rule", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "moonpay-docs-1", "moonpay-docs-2", "moonpay-docs-20" ] }, { "productId": "moonpay", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-11", "moonpay-comm-2" ] }, { "productId": "moonpay", "storyId": "stablecoin-issuance", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "stablecoin-payouts", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-2", "moonpay-docs-14", "moonpay-docs-15", "moonpay-docs-11", "moonpay-docs-17" ] }, { "productId": "moonpay", "storyId": "testnet-sandbox", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-13", "moonpay-docs-14", "moonpay-docs-15" ] }, { "productId": "moonpay", "storyId": "treasury-rebalancing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-14", "moonpay-docs-16", "moonpay-docs-17", "moonpay-docs-11" ] }, { "productId": "moonpay", "storyId": "virtual-accounts-addressing", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "moonpay", "storyId": "wallet-provisioning-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "moonpay-docs-10" ] }, { "productId": "paxos", "storyId": "accept-stablecoin-checkout", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-12", "paxos-docs-13", "paxos-docs-14", "paxos-docs-15", "paxos-docs-16", "paxos-docs-17", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "agent-initiated-payments", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-2", "paxos-docs-8", "paxos-docs-9", "paxos-docs-11" ] }, { "productId": "paxos", "storyId": "agent-wallet-provisioning", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-2", "paxos-docs-3", "paxos-docs-5" ] }, { "productId": "paxos", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "paxos-probe-1", "paxos-docs-1", "paxos-docs-18" ] }, { "productId": "paxos", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Paxos is a stablecoin/crypto infrastructure API platform; evidence only shows AI assistance for documentation help (paxos-docs-18), not AI-generated insights or suggestions derived from a user's own data within the product. No mention of analytics, dashboards, or AI-driven recommendations based on account/transaction data.", "evidenceIds": [ "paxos-docs-18" ] }, { "productId": "paxos", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-16", "paxos-docs-17", "paxos-docs-8", "paxos-docs-9" ] }, { "productId": "paxos", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "paxos-docs-18" ] }, { "productId": "paxos", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-2", "paxos-docs-3", "paxos-docs-4", "paxos-docs-22" ] }, { "productId": "paxos", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a stablecoin/crypto infrastructure API platform, not an AI agent or MCP client; plugging MCP servers into it to use their tools is not a fair axis for this product category. No evidence contradicts this framing.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "paxos", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "paxos", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "paxos-docs-2", "paxos-docs-3", "paxos-docs-4", "paxos-docs-19", "paxos-docs-20", "paxos-docs-21", "paxos-docs-16", "paxos-probe-1", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-2", "paxos-docs-3" ] }, { "productId": "paxos", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-19", "paxos-docs-20", "paxos-docs-21", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-16", "paxos-docs-17" ] }, { "productId": "paxos", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-22", "paxos-docs-18", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "api-sandbox", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "paxos-docs-1", "paxos-docs-4", "paxos-docs-22" ] }, { "productId": "paxos", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-19", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-16", "paxos-docs-17" ] }, { "productId": "paxos", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a financial/crypto infrastructure API (payments, brokerage, custody) rather than an AI-native workflow/automation platform; scheduling recurring jobs or workflows is not a capability category this product addresses—it offers webhooks for event-driven callbacks, not job scheduling. This is a category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a financial/stablecoin infrastructure API platform, not an automation/workflow builder; there is no concept of 'automations' to version, review, or roll back in this product category.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-10", "paxos-docs-11" ] }, { "productId": "paxos", "storyId": "custodial-stablecoin-balances", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "paxos-docs-5", "paxos-docs-6", "paxos-docs-8", "paxos-docs-9", "paxos-docs-11", "paxos-docs-13" ] }, { "productId": "paxos", "storyId": "fiat-onramp-integration", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-5", "paxos-docs-11" ] }, { "productId": "paxos", "storyId": "fiat-settlement-option", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-12", "paxos-docs-13", "paxos-docs-14", "paxos-docs-9" ] }, { "productId": "paxos", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-10", "paxos-docs-19" ] }, { "productId": "paxos", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-9", "paxos-docs-13", "paxos-docs-14", "paxos-docs-11" ] }, { "productId": "paxos", "storyId": "kyc-onboarding-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-5", "paxos-docs-6", "paxos-docs-7", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "machine-payment-protocols", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "multi-chain-support", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-12", "paxos-docs-10", "paxos-docs-8", "paxos-docs-9" ] }, { "productId": "paxos", "storyId": "no-node-integration", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-10", "paxos-docs-22", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-17", "paxos-docs-23", "paxos-probe-2", "paxos-docs-5", "paxos-docs-6", "paxos-docs-8", "paxos-docs-9", "paxos-docs-16" ] }, { "productId": "paxos", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a stablecoin/crypto infrastructure and payments API platform, not a data-hosting or AI-native application where users accumulate personal data that would need export/portability; 'export all my data in open formats and leave' is a category mismatch for this kind of financial API product.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a proprietary fintech/crypto platform API, not open-source software; the axis of reading source code under an open license does not apply to this kind of product.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a regulated financial/stablecoin infrastructure platform accessed via hosted API/dashboard/sandbox; self-hosting the core product is not a coherent concept for a regulated custody/payments service and no evidence suggests any self-hosted deployment option.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "payment-webhooks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-16", "paxos-docs-17" ] }, { "productId": "paxos", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a crypto/stablecoin payments and brokerage platform, not an AI model or AI-native product that trains on user data; the AI-training opt-out axis does not apply to this category of product.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Paxos is a regulated stablecoin/crypto-payments API platform, not an AI agent or developer tool with telemetry/usage-tracking settings relevant to an AI-native user's privacy posture; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "reserve-yield-programs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "paxos", "storyId": "sanctions-travel-rule", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-5", "paxos-docs-6", "paxos-docs-7" ] }, { "productId": "paxos", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-9", "paxos-docs-11", "paxos-docs-14" ] }, { "productId": "paxos", "storyId": "stablecoin-issuance", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-11" ] }, { "productId": "paxos", "storyId": "stablecoin-payouts", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-10", "paxos-docs-7", "paxos-docs-16", "paxos-docs-19", "paxos-probe-2" ] }, { "productId": "paxos", "storyId": "testnet-sandbox", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-1", "paxos-docs-4", "paxos-docs-22", "paxos-docs-8", "paxos-docs-9" ] }, { "productId": "paxos", "storyId": "treasury-rebalancing", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-8", "paxos-docs-9", "paxos-docs-10", "paxos-docs-11", "paxos-docs-23", "paxos-docs-22" ] }, { "productId": "paxos", "storyId": "virtual-accounts-addressing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-12", "paxos-docs-13", "paxos-docs-15", "paxos-docs-16" ] }, { "productId": "paxos", "storyId": "wallet-provisioning-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "paxos-docs-5", "paxos-docs-6", "paxos-docs-11" ] }, { "productId": "stripe-crypto", "storyId": "accept-stablecoin-checkout", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Stripe documents a stablecoin payments API supporting USDC/USDP/USDG across multiple networks, with refunds/partial refunds, checkout/onramp flows (hosted, embedded, mobile SDK), and even machine-to-machine stablecoin payments via x402 — covering the create-payment-present-flow-confirm-settlement lifecycle described in the story. Missing for 10: explicit code-level API reference (e.g., PaymentIntent creation with stablecoin payment method, webhook/settlement confirmation snippet) and independent hands-on developer confirmation that programmatic settlement works as documented.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-2", "stripe-crypto-docs-3", "stripe-crypto-docs-11", "stripe-crypto-docs-12", "stripe-crypto-docs-13", "stripe-crypto-docs-14", "stripe-crypto-docs-16", "stripe-crypto-docs-17" ] }, { "productId": "stripe-crypto", "storyId": "agent-initiated-payments", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Stripe documents machine/agent stablecoin payments via the x402 protocol (docs-16, docs-17) and recurring stablecoin withdrawal authorization (docs-4), showing some agent-payment-adjacent capability, but there is no documentation of a human configuring spend controls/limits that scope an agent's authority to move funds. missing for 10: explicit spend-control/authorization-limit configuration by a human, documented agent payout workflow with scoped permissions, and any hands-on or third-party confirmation of this flow working.", "evidenceIds": [ "stripe-crypto-docs-16", "stripe-crypto-docs-17", "stripe-crypto-docs-4" ] }, { "productId": "stripe-crypto", "storyId": "agent-wallet-provisioning", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Stripe documents stablecoin financial accounts, cards, and support for the x402 machine-payment protocol, hinting at agent/programmatic payment flows, but there is no documentation of agent-specific wallet issuance, scoped API keys, policy controls, or explicit spend limits for autonomous agents. missing for 10: agent-scoped key issuance, policy/permission controls, documented spend limits for agents, independent corroboration of agentic wallet safety.", "evidenceIds": [ "stripe-crypto-docs-16", "stripe-crypto-docs-17", "stripe-crypto-docs-5", "stripe-crypto-docs-6" ] }, { "productId": "stripe-crypto", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Stripe's docs.stripe.com exposes an llms.txt file (HTTP 200) and per-page .md agent-readable docs (e.g. crypto.md, stablecoin-payments.md, machine.md), confirmed by direct probes, so an agent can be pointed at llms.txt or markdown docs directly. Missing for 10: no independent/community confirmation of an agent actually consuming llms.txt successfully, and no dedicated agent-oriented documentation index beyond the generic llms.txt.", "evidenceIds": [ "stripe-crypto-probe-1", "stripe-crypto-probe-2", "stripe-crypto-docs-16" ] }, { "productId": "stripe-crypto", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/crypto infrastructure product, not an analytics or data-insights tool; there is no evidence of AI-generated insights or suggestions surfaced from user data within the product, and this axis is a category mismatch for this product type.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers crypto/stablecoin payment features (onramp, payouts, financial accounts) but contains no mention of automation setup, scheduling, workflows, or autonomous background agent execution tied to this product. missing for 10: any evidence of automation/workflow builder, scheduling or triggers, autonomous agent execution, or background task orchestration.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Stripe provides a documented CLI (stripe-cli) and API-based integration for crypto/stablecoin payments, which enables headless/automated/CI usage of the broader Stripe platform, and a machine-payment protocol (x402) suited for agentic/automated payment flows. However, there's no crypto-specific evidence of CI/test-mode tooling, fixtures, or automation examples tailored to the crypto product beyond generic docs. Missing for 10: crypto-specific CI/test examples, sandbox/test-mode automation docs, and independent confirmation of headless workflows for stablecoin features.", "evidenceIds": [ "stripe-crypto-probe-5", "stripe-crypto-docs-16", "stripe-crypto-docs-17", "stripe-crypto-probe-2" ] }, { "productId": "stripe-crypto", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/financial infrastructure product, not an agent or orchestrator that itself consumes external MCP servers' tools. Evidence only shows Stripe publishing its own MCP server (docs.stripe.com/mcp) for others to call into it, which is the server role, not the client role the story asks about — this axis is a category error for this product type.", "evidenceIds": [ "stripe-crypto-probe-4" ] }, { "productId": "stripe-crypto", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "Stripe publishes an official MCP server (docs.stripe.com/mcp) that lets AI agents connect to Stripe capabilities, and Stripe itself is a service/platform (not an agent), so the axis applies and is satisfied. missing for 10: no detail on which crypto/stablecoin tools are exposed via MCP, no independent/hands-on corroboration of the MCP server's functionality.", "evidenceIds": [ "stripe-crypto-probe-4" ] }, { "productId": "stripe-crypto", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Stripe documents an official MCP server (docs.stripe.com/mcp) that would let AI agents/LLMs invoke Stripe functionality via natural-language-driven tool calls, and the crypto/stablecoin docs describe machine-native payment support over the x402 protocol for agentic/automated transactions. However, there is no direct evidence of a natural-language command interface specifically for the crypto/stablecoin product surface (onramp, financial accounts, payouts), and no hands-on confirmation of AI-native operation. Missing for 10: crypto-specific natural-language command examples, hands-on/independent verification of MCP or x402 usage for stablecoin flows, and documentation tying the MCP server to crypto-specific actions.", "evidenceIds": [ "stripe-crypto-probe-4", "stripe-crypto-docs-16", "stripe-crypto-docs-17" ] }, { "productId": "stripe-crypto", "storyId": "agentic-official-cli", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Stripe documents an official CLI (stripe-cli) as part of its platform, which applies to the Crypto & Stablecoins product since it's built on the same Stripe API/tooling. missing for 10: X, Y - no crypto-specific CLI command examples, no independent/hands-on confirmation of CLI use for crypto endpoints.", "evidenceIds": [ "stripe-crypto-probe-5" ] }, { "productId": "stripe-crypto", "storyId": "agentic-public-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Stripe Crypto is part of the broader Stripe API/platform, which is documented and programmatically drivable (docs.stripe.com, CLI, MCP server referenced), and x402 protocol support suggests machine-native payment flows. However, the evidence pack lacks crypto-specific API reference/OpenAPI spec (openapi probe returned 404s) or SDK examples for driving crypto/stablecoin features specifically via API. missing for 10: crypto-specific API reference or OpenAPI schema, explicit SDK/code examples for stablecoin endpoints, independent confirmation of agentic/API-driven crypto workflows beyond x402 mention.", "evidenceIds": [ "stripe-crypto-docs-16", "stripe-crypto-docs-17", "stripe-crypto-probe-1", "stripe-crypto-probe-2", "stripe-crypto-probe-3", "stripe-crypto-probe-4", "stripe-crypto-probe-5" ] }, { "productId": "stripe-crypto", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Stripe's crypto/stablecoin docs are exposed as machine-readable markdown, an llms.txt index, an official CLI, and a documented MCP server, suggesting the crypto APIs are reachable via Stripe's standard official SDKs, but the evidence never explicitly names or links official language SDKs (e.g., stripe-node/python/ruby) covering crypto/stablecoin endpoints. Missing for 10: explicit SDK documentation/examples for crypto features, independent corroboration of SDK usage in agentic/AI workflows, and confirmation the OpenAPI spec (needed for SDK generation) is accessible (probe found it 404).", "evidenceIds": [ "stripe-crypto-probe-1", "stripe-crypto-probe-2", "stripe-crypto-probe-4", "stripe-crypto-probe-5", "stripe-crypto-probe-3", "stripe-crypto-docs-16" ] }, { "productId": "stripe-crypto", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers crypto/stablecoin payment features, onramp, payouts, financial accounts, and even x402 protocol support, but contains no mention of webhooks or event subscription mechanisms for the crypto/stablecoin product. Webhooks are a plausible and expected capability for a payments API, so the axis applies, but no evidence supports it here.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Stripe docs, an llms.txt file, and a CLI/MCP server, but there is no mention of an interactive API reference with runnable examples (e.g., API explorer, try-it console). OpenAPI probe returned 404s, and no docs cite an interactive playground for crypto/stablecoin endpoints.", "evidenceIds": [ "stripe-crypto-probe-3", "stripe-crypto-probe-1", "stripe-crypto-probe-2" ] }, { "productId": "stripe-crypto", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack explicitly shows a probe that checked common OpenAPI spec locations (openapi.json, swagger.json, etc.) and all returned 404, and no other citation confirms a downloadable machine-readable API spec for Stripe Crypto & Stablecoins. Only llms.txt and markdown docs are shown as available, not a structured OpenAPI/JSON schema.", "evidenceIds": [ "stripe-crypto-probe-3", "stripe-crypto-probe-1" ] }, { "productId": "stripe-crypto", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack for Stripe Crypto & Stablecoins covers wallets, onramp, payouts, refunds, and cards, but nowhere mentions a test/sandbox mode or non-production environment for crypto/stablecoin flows. Since sandbox testing is a plausible and expected capability for an API-based payments product, its absence here is a gap rather than an inapplicable axis.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack discusses API versioning practices or a documented deprecation policy for Stripe's crypto/stablecoin APIs; the OpenAPI probe even returned 404s. missing for 10: any mention of API version headers, changelog, or deprecation policy documentation.", "evidenceIds": [ "stripe-crypto-probe-3" ] }, { "productId": "stripe-crypto", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of bulk/batch operations across many items (e.g., batch payouts, bulk API calls, batch job endpoints) for the crypto/stablecoin product; docs describe single-transaction flows (onramp, payouts, refunds).", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers crypto/stablecoin payment rails, onramp, payouts, and financial accounts, but contains no mention of user-definable event-triggered rules or automation/workflow logic. Webhooks or event-based automation are not referenced anywhere in the pack. missing for 10: rule-definition mechanism, event-trigger automation framework, evidence of conditional action execution.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/crypto infrastructure product, not an automation/orchestration platform; scheduling recurring AI-native jobs or workflows is outside its category (recurring stablecoin withdrawals are billing automation, not job/workflow scheduling for AI agents).", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto is a payments/stablecoin infrastructure product, not an automation/workflow builder; there is no concept of 'automations' with version history or rollback in this product's evidence, so this axis is a category error.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "batch-disbursements", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Stripe can pay out stablecoins to individual connected accounts and issue cards, but there is no documentation of a batch/bulk payout API, mass disbursement endpoint, or per-item status reporting for many payouts in one operation.", "evidenceIds": [ "stripe-crypto-docs-8", "stripe-crypto-docs-9", "stripe-crypto-docs-10" ] }, { "productId": "stripe-crypto", "storyId": "custodial-stablecoin-balances", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Stripe's docs describe Stablecoin Financial Accounts letting eligible businesses hold a stablecoin balance, with explicit gating language ('eligible businesses', 'countries where it's available') and honest disclosure that it's not universally available, plus card issuance against the balance. However, the docs do not enumerate the specific list of supported geographies/countries, and community evidence shows historical exclusion of crypto businesses and confusion over payout mechanics, suggesting real-world gating is stricter/less transparent than the docs alone convey. missing for 10: an explicit published list of eligible countries/geographies, independent confirmation of account availability, and clarity on gating criteria beyond 'eligible businesses'.", "evidenceIds": [ "stripe-crypto-docs-5", "stripe-crypto-docs-6", "stripe-crypto-docs-7", "stripe-crypto-comm-1", "stripe-crypto-comm-2", "stripe-crypto-comm-3" ] }, { "productId": "stripe-crypto", "storyId": "fiat-onramp-integration", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Stripe documents a fiat-to-crypto onramp with hosted, embedded (web), and embedded components (mobile SDK) options for buying stablecoins via cards/bank transfers, with Stripe as merchant of record handling KYC/fraud (stripe-crypto-docs-11 through 15). This directly matches the story of a documented widget/API for in-product onramp embedding. Missing for 10: independent hands-on developer confirmation of the embedded widget integration experience and no code-sample evidence in the pack.", "evidenceIds": [ "stripe-crypto-docs-11", "stripe-crypto-docs-12", "stripe-crypto-docs-13", "stripe-crypto-docs-14", "stripe-crypto-docs-15" ] }, { "productId": "stripe-crypto", "storyId": "fiat-settlement-option", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Stripe's documented crypto product explicitly states customers can pay with crypto that settles as fiat in the merchant's Stripe balance, directly matching the finance-lead need to accept stablecoins without holding crypto on the books, and this is backed by first-party docs on stablecoin payments, refunds, and settlement mechanics. missing for 10: no independent/hands-on accounting confirmation that settlement is always fiat-only (vs. optional stablecoin balance retention), and no explicit mention of bank payout timing/documentation for finance reconciliation.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-2", "stripe-crypto-docs-3", "stripe-crypto-probe-2" ] }, { "productId": "stripe-crypto", "storyId": "fx-conversion-api", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Stripe offers onramp (fiat-to-crypto) and stablecoin payments/payouts, but there is no documented quote/conversion-rate API exposing exchange rates, fees, or settlement times for conversions between fiat and stablecoins or between stablecoins — pricing and rate details are absent from the evidence pack. missing for 10: a dedicated conversion/quote endpoint, documented FX rate and fee schedule for stablecoin conversions, documented settlement-time SLAs, and stablecoin-to-stablecoin conversion support.", "evidenceIds": [ "stripe-crypto-docs-11", "stripe-crypto-docs-12", "stripe-crypto-docs-13", "stripe-crypto-docs-15", "stripe-crypto-docs-5", "stripe-crypto-docs-9" ] }, { "productId": "stripe-crypto", "storyId": "global-fiat-offramp", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Docs describe crypto payments settling as fiat in the merchant's Stripe balance and stablecoin payouts to connected accounts/financial accounts, but there is no documented dedicated 'off-ramp' feature converting stablecoin balances into bank transfers with a published list of supported currencies/countries — in fact docs note stablecoin balances exist precisely in markets where fiat Treasury isn't available, implying no guaranteed bank conversion there. Missing for 10: explicit off-ramp/conversion mechanism from stablecoin to bank transfer, a published country/currency coverage list, and independent confirmation it works as described.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-6", "stripe-crypto-docs-9", "stripe-crypto-docs-8" ] }, { "productId": "stripe-crypto", "storyId": "kyc-onboarding-api", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Stripe states it internally handles KYC verifications and sanctions screening for onramp transactions, and community evidence shows recipient-type restrictions (individuals/sole proprietors only) implying some vetting occurs — but there are no documented KYC/KYB endpoints, verification statuses, or flows that an ops lead can programmatically invoke to clear a counterparty before sending/receiving. missing for 10: documented KYC/KYB API endpoints, verification status objects, or ops-controllable onboarding flow for senders/recipients.", "evidenceIds": [ "stripe-crypto-docs-15", "stripe-crypto-comm-3", "stripe-crypto-comm-4" ] }, { "productId": "stripe-crypto", "storyId": "machine-payment-protocols", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Stripe docs explicitly name and document x402 protocol support for stablecoin payments, including a technical detail (0.01 USDC minimum), which goes beyond blog-level aspiration. However, there is no documented support for ACP, MPP, or AP2 protocols in the evidence pack, so the 'speaks the machine-payment protocols by name' story is only partially fulfilled. Missing for 10: ACP support/endpoints, MPP support/endpoints, AP2 support/endpoints, and independent corroboration of x402 usage in production.", "evidenceIds": [ "stripe-crypto-docs-16", "stripe-crypto-docs-17" ] }, { "productId": "stripe-crypto", "storyId": "multi-chain-support", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs explicitly enumerate supported stablecoins (USDC, USDP, USDG) and specific chains per coin (Tempo, Ethereum, Solana, Polygon, Base), letting developers match customer holdings to supported networks. Community commentary raises ethical/centralization concerns about Solana but does not dispute the accuracy of the documented coverage. Missing for 10: independent verification of full USDT support (not mentioned in evidence) and confirmation the list is exhaustive/up to date.", "evidenceIds": [ "stripe-crypto-docs-2", "stripe-crypto-docs-1", "stripe-crypto-probe-2" ] }, { "productId": "stripe-crypto", "storyId": "no-node-integration", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Stripe's crypto/stablecoin docs present a conventional REST-style API (via standard Stripe API, Financial Accounts, onramp, x402) abstracting settlement, custody, and payouts without requiring developers to run nodes or manage gas directly, and Stripe's general SDKs cover multiple languages. However, the evidence pack doesn't explicitly confirm crypto-specific client libraries or SDK coverage for these crypto endpoints, and community comments raise confusion over how crypto payouts/checkout actually work in practice. missing for 10: explicit confirmation of crypto-specific client library support across languages, clearer docs on gas/chain abstraction mechanics, and independent developer confirmation that no chain-level operations leak into the integration.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-4", "stripe-crypto-docs-5", "stripe-crypto-docs-11", "stripe-crypto-docs-16", "stripe-crypto-probe-2", "stripe-crypto-comm-4" ] }, { "productId": "stripe-crypto", "storyId": "openness-api-parity", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Stripe's crypto/stablecoin docs describe everything as API/SDK-driven integrations (Payment Intents, Financial Accounts, onramp embedded/API components, payouts), suggesting an API-first design typical of Stripe, but the evidence never explicitly confirms that every UI-exposed action (e.g., wallet linking in the Express Dashboard, card issuance flows) has a documented equivalent API call, nor is there any AI-agent-specific tooling cited beyond the general Stripe MCP/CLI probes which aren't crypto-specific. missing for 10: explicit statement or example that all Dashboard/Express UI crypto actions map 1:1 to API endpoints, and independent verification of full API/UI parity for this specific crypto product.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-9", "stripe-crypto-docs-11", "stripe-crypto-docs-13", "stripe-crypto-docs-14", "stripe-crypto-probe-4", "stripe-crypto-probe-5" ] }, { "productId": "stripe-crypto", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/financial infrastructure product, not a data-management or knowledge tool; data export/portability in open formats is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto is a closed commercial SaaS payments product; there is no open-source source code license involved, making this axis a category error rather than a gap.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto is a hosted SaaS payments service; self-hosting the core product is a category error for this type of product, akin to asking to self-host a hosted payment processor.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "payment-webhooks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack documents Stripe Crypto's onramp, stablecoin payments, financial accounts, and payouts, but contains no mention of webhooks, event types, or signed notifications for crypto-specific state changes (payment confirmed, payout settled, conversion executed). Since this is an applicable axis for a payments platform but no supporting evidence exists in the pack, it must be judged 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/crypto product, not a data storage or AI infrastructure platform; data residency/region selection is not a relevant axis for this product category, and no evidence pack content addresses data storage location choices.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments infrastructure product, not an AI model or data-processing service; preventing user data from being used for AI training is not an applicable axis for this product category.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments product; data retention/deletion controls for AI-native privacy posture is a category error for this axis, not a payments feature.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Crypto & Stablecoins is a payments/financial infrastructure product, not an AI agent or SDK with telemetry collection concerns relevant to AI-native users; opting out of telemetry/usage tracking is a category mismatch for this product's axis.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "regulatory-posture-transparency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item discloses which licensed/registered legal entities operate Stripe's crypto/stablecoin products or lists jurisdictional coverage of those entities; docs describe features and networks, not corporate/regulatory entity structure. Community threads even highlight regulatory murkiness ('the regulatory details are complex') without clarifying entity/jurisdiction transparency.", "evidenceIds": [ "stripe-crypto-docs-15", "stripe-crypto-comm-2" ] }, { "productId": "stripe-crypto", "storyId": "reserve-yield-programs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers stablecoin payment/payout mechanics and financial account features but contains no documentation of reserve composition, attestations, or a yield/rewards program with eligibility and regulatory caveats for held stablecoin balances.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "sanctions-travel-rule", "verdict": "partial", "quality": 3, "confidence": "medium", "rationale": "Docs mention Stripe handles 'regulatory requirements, KYC verifications, and sanctions screening' for onramp transactions (stripe-crypto-docs-15), but this is a single generic line, not a detailed compliance framework. There is no mention of wallet risk-scoring/checks or travel-rule handling anywhere in the pack. Missing for 10: named wallet risk-check mechanism, travel-rule compliance documentation, detail on sanctions screening process/providers.", "evidenceIds": [ "stripe-crypto-docs-15" ] }, { "productId": "stripe-crypto", "storyId": "settlement-transparency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Docs confirm crypto payments settle as fiat into the Stripe balance and mention refunds support, but there is no evidence of documented settlement timing (e.g., T+n days), no published fee schedule per rail/network, and no mention of statements or accounting-ready reports for crypto/stablecoin transactions.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-3" ] }, { "productId": "stripe-crypto", "storyId": "stablecoin-issuance", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Stripe's crypto offerings cover payments, onramp, payouts, and stablecoin financial accounts — but there is no evidence of a stablecoin issuance product (minting a branded coin, redemption mechanics, reserve management/attestation). This is a distinct product category (e.g., Bridge/Paxos-style issuance-as-a-service) that Stripe's evidence pack never mentions.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "stablecoin-payouts", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Stripe documents stablecoin payouts to connected accounts (platforms/marketplaces) and wallet-linking via Express Dashboard, implying an API-driven payout path, but the evidence never shows a generic 'pay any wallet address or stored recipient' API call, nor documented status-tracking fields through to final settlement. Community reports also note real constraints (recipients must be individuals/sole proprietors, confusion about payout flow), and a Connect-only payout model is narrower than the story's general wallet-payout claim. Missing for 10: explicit API reference/status object for tracking payout progress to settlement, confirmation that arbitrary external wallet addresses (not just linked connected accounts) can be paid, and resolution of community confusion about how payouts actually work.", "evidenceIds": [ "stripe-crypto-docs-8", "stripe-crypto-docs-9", "stripe-crypto-comm-3", "stripe-crypto-comm-4" ] }, { "productId": "stripe-crypto", "storyId": "testnet-sandbox", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item mentions a sandbox, testnet, or deterministic test values for crypto/stablecoin payments, payouts, or conversions; Stripe's general test-mode is not documented here for this crypto product. Missing for 10: documented testnet/sandbox mode, test API keys or test wallet addresses for crypto flows, deterministic test value behavior for payments/payouts/conversions.", "evidenceIds": [] }, { "productId": "stripe-crypto", "storyId": "treasury-rebalancing", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Stripe documents stablecoin Financial Accounts that let businesses hold, receive, and send stablecoin balances alongside fiat Treasury, plus card issuance backed by those balances, but there is no explicit documentation of a finance-lead-facing internal transfer/rebalancing flow moving value between fiat and stablecoin balances via API or dashboard — the onramp/payout docs are customer- or payout-facing, not treasury rebalancing tools. missing for 10: dedicated API/dashboard endpoint or flow for converting/rebalancing between fiat and stablecoin balances, end-to-end docs for finance-lead treasury operations, independent confirmation of this workflow.", "evidenceIds": [ "stripe-crypto-docs-5", "stripe-crypto-docs-6", "stripe-crypto-docs-7", "stripe-crypto-docs-11", "stripe-crypto-docs-8" ] }, { "productId": "stripe-crypto", "storyId": "virtual-accounts-addressing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence describes Stripe's crypto payment acceptance, onramp, stablecoin financial accounts, and payouts, but nowhere mentions per-customer dedicated deposit addresses or named virtual accounts for automatic reconciliation of incoming crypto/stablecoin payments. Payments appear tied to Stripe's standard Checkout/PaymentIntent flow rather than unique wallet addresses per customer.", "evidenceIds": [ "stripe-crypto-docs-1", "stripe-crypto-docs-2", "stripe-crypto-docs-5", "stripe-crypto-docs-6" ] }, { "productId": "stripe-crypto", "storyId": "wallet-provisioning-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers stablecoin payments, onramp, financial accounts, and payouts to connected accounts, but there is no documented API for programmatically creating per-customer or per-purpose wallets/deposit addresses with custody semantics; wallet linking is described as user-driven (Express Dashboard) not developer-provisioned.", "evidenceIds": [ "stripe-crypto-docs-5", "stripe-crypto-docs-6", "stripe-crypto-docs-9" ] } ]