BVNK vs Coinbase Payments (CDP)
enterprise-custom
·usage-based · enterprise-custom
Coinbase Payments (CDP) wins · 9–16 (24 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Coinbase Payments (CDP)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.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [claimed-docs] “As a partner, you can add a markup fee to your customers' transactions, enabling you to collect additional revenue from your customers.”
Probe confirms llms.txt is live (HTTP 200) at docs.cdp.coinbase.com, listing 538 pages of docs, and multiple docs entries are directly sourced from that llms.txt, showing agent-oriented documentation is real and accessible. Missing for 10: no independent third-party report of an agent successfully consuming llms.txt to complete a task.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnBVNK 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.
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
CDP offers SDKs and a CLI (with an MCP server exposing every API endpoint as a tool) that can be scripted headlessly for automation and CI, and its API-first design (webhooks, x402, wallet SDKs) supports programmatic/agentic use. However, there's no explicit documentation of CI-specific patterns (e.g., service-account auth for pipelines, GitHub Actions examples, or headless auth flows without browser/UI steps). missing for 10: explicit CI/headless authentication guidance, CI pipeline examples, independent confirmation of non-interactive operation.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Coinbase Payments (CDP)BVNKnone0/10BVNK 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.
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
Coinbase Payments (CDP) ships an official MCP server via the CDP CLI (`cdp mcp`) exposing every API endpoint as a tool, plus a separate Coinbase Wallet MCP for AI agent wallet actions, both documented and probe-confirmed. missing for 10: independent/hands-on third-party corroboration beyond first-party docs and probes.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
ai-native userUse an official CLI
weight 2 · round to Coinbase Payments (CDP)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.
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
CDP ships an official CLI that also includes an MCP server (`cdp mcp`) exposing every API endpoint as a tool, and docs explicitly reference using the CDP CLI for treasury/payout workflows, directly supporting AI-native/agentic use. Missing for 10: independent hands-on verification of CLI usage and richer documentation of CLI command coverage beyond MCP exposure.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userDrive the product through a documented public API
weight 3 · round drawnBVNK 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.
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
CDP exposes a documented public API/SDK covering wallets, payments, onramp, x402, and webhooks, with client libraries (cdp-sdk) and an explicit CLI/MCP server (`cdp mcp`) exposing every API endpoint as a tool for AI-native workflows. missing for 10: a discoverable OpenAPI/swagger spec (probe found all candidate paths 404), and independent third-party corroboration beyond vendor docs.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnBVNKnone0/10BVNK'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.
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
Coinbase Payments (CDP)none0/10The 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.
ai-native userBuild against official SDKs
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10Evidence 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'.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
Coinbase Payments provides official client SDKs (cdp-sdk on GitHub for EVM/Solana wallets), plus CLI and MCP server tooling explicitly aimed at AI-native/agentic use (x402 payments, MCP for AI assistants, wallet-per-agent support), all documented first-party. Missing for 10: independent/third-party corroboration of SDK quality and a public OpenAPI spec (probe found openapi.json 404s), which would strengthen developer trust.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userSubscribe to events via webhooks
weight 2 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
Docs explicitly describe webhooks for real-time HTTP notifications on CDP integration events, including multi-address wallet activity subscriptions, which fits the ai-native agenticness theme of event-driven automation. Missing for 10: independent/hands-on confirmation of webhook reliability and no explicit event-type catalog or signature-verification detail in evidence.
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnBVNK 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.
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
CDP provides building blocks for autonomous background automation—webhooks for event-driven triggers, auto-liquidation/auto-convert on incoming payments, x402 for agent-to-agent programmatic payments, and an MCP server exposing all API endpoints as tools for AI agents to call—which together let developers wire up unattended, background-running payment flows. However, this is a set of APIs/SDKs and integration primitives rather than a hosted, first-party autonomous automation/orchestration runtime that runs itself; the user must build and host the actual automation logic. Missing for 10: evidence of a native scheduler or persistent agent-runtime service, and independent/hands-on confirmation that these pieces compose into a working autonomous background automation.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnBVNKnone0/10The 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.)
ai-native userOperate the product with natural-language commands
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10No 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.
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
CDP exposes an MCP server (`cdp mcp`) that surfaces every API endpoint as a tool, and Coinbase Wallet MCP lets an AI assistant check balances, send funds, swap tokens, and pay with x402 — enabling natural-language operation via an MCP-compatible AI client. However, this requires a separate AI client/agent host to interpret NL commands; there's no evidence of a built-in chat/NL interface within CDP itself, no independent hands-on validation of the MCP tool coverage, and no examples of complex NL command sequences being executed reliably. missing for 10: first-party or independent demonstration of end-to-end natural-language command execution, evidence of NL interface beyond MCP tool exposure, and confirmation of reliability/robustness of the MCP tool-calling across the full API surface.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnBVNKnone0/10BVNK'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.
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
Coinbase Payments (CDP)none0/10There is no evidence of an interactive API reference with runnable examples; the OpenAPI spec probe returned 404s on all candidate paths, and no docs mention interactive playgrounds or executable code snippets. Missing for 10: interactive API reference UI, runnable/executable examples, OpenAPI/Swagger spec availability.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnBVNKnone0/10The 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.
Coinbase Payments (CDP)none0/10A direct probe for common OpenAPI spec paths returned 404s, and no evidence pack item links to a downloadable machine-readable API spec; only an llms.txt docs index and MCP/CLI tooling are documented, which are not equivalent to an OpenAPI spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.cdp.coinbase.com/llms.txt # Coinbase Developer Documentation - [Docs (538 pages)](https://docs.cdp…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to BVNKBVNK 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.
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
Docs explicitly describe a Sandbox as 'a fully isolated testing environment for custodial features without connecting real funds,' directly matching the story. However, evidence doesn't clarify sandbox coverage for non-custodial/onchain, x402, or webhook features, nor provide hands-on confirmation of the isolation guarantee. Missing for 10: independent/hands-on verification of sandbox isolation, detail on which product areas are sandbox-covered vs not, and any test-data seeding or reset tooling.
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to BVNKThere 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.
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
Coinbase Payments (CDP)none0/10No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec probes 404'd and none of the docs mention version numbers, sunset timelines, or deprecation notices.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10No 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.
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
The only concrete bulk-scale capability is watching up to 100 wallet addresses under one webhook subscription (`wallet.activity.multi`); all other documented operations (send payouts, provision addresses, checkout, onramp) are described as single-item flows with no batch/bulk endpoints shown. Missing for 10: bulk payout/disbursement APIs, batch transaction submission, bulk provisioning of addresses, and any explicit multi-item automation beyond webhook address watching.
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to BVNKBVNK 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.
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
CDP offers event-driven building blocks — webhooks for real-time notifications on wallet/payment activity, and built-in auto-liquidation/auto-convert triggered on fund receipt — that let a developer wire up automation, but there is no documented user-facing rules engine where an AI-native user declaratively defines 'if event X then action Y' logic; the developer must write the handling logic themselves. missing for 10: a declarative rules/automation engine, conditional logic support, or evidence of no-code rule definitions tied to webhook events.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnBVNKnone0/10BVNK'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.
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnBVNKnone0/10BVNK 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.
Compliance risk — stories about compliance risk in this arenaCompliance risk
Stories about compliance risk in this arena
Kyc
ops leadCustomer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves
weight 2 · round drawnBVNKnone0/10Evidence 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.
Coinbase Payments (CDP)none0/10No 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.
Licensing
founderSee who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried
weight 2 · round drawnBVNKnone0/10The 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.
Screening
ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at
weight 2 · round drawnBVNKnone0/10None 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.
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Abstraction
developerI never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
weight 3 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
CDP provides a REST API plus client SDKs (cdp-sdk on GitHub for EVM/Solana wallets) that abstract key management, signing, and broadcasting, and custodial payment features (stable addresses, payouts, checkout) explicitly avoid onchain complexity for the developer. However, some flows (non-custodial send, wallet management) still expose wallet/chain concepts like signing and gas isn't fully hidden everywhere, and no OpenAPI spec was found (probe 404s) suggesting API conventionality is asserted but not independently verifiable, and multi-language client library breadth is unconfirmed beyond the single GitHub SDK repo. Missing for 10: verifiable OpenAPI/REST spec, evidence of multiple language SDKs, and confirmation gas/chain mechanics are fully invisible across all product surfaces.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Sandbox
developerRehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically
weight 3 · round drawnBVNK 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.
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
Coinbase documents a dedicated Sandbox as a fully isolated testing environment for custodial features without real funds, which covers payments-type scenarios. However, evidence doesn't confirm sandbox/testnet coverage extends deterministically to payouts and conversions specifically, nor describe deterministic test values/behaviors. Missing for 10: explicit documentation of testnet/sandbox coverage for payouts and conversions flows, description of deterministic test value behavior, and independent/hands-on confirmation of sandbox reliability.
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
Webhooks
developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
weight 2 · round drawnDocs 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.
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
CDP docs confirm a webhooks system delivering 'real-time HTTP notifications when things happen across your CDP integration' and wallet-activity subscriptions, which supports state-tracking without polling. However, the evidence never confirms webhook payloads are cryptographically signed, nor does it enumerate the specific events named in the story (payment confirmed, payout settled, conversion executed) — it only shows generic notification and wallet-activity events. Missing for 10: explicit signature/verification mechanism documentation, and confirmation of payment/payout/conversion-specific event types.
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
Onramp conversion — stories about onramp conversion in this arenaOnramp conversion
Stories about onramp conversion in this arena
Conversion
developerConversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
weight 2 · round drawnBVNK 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.
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
- [claimed-docs] “As a partner, you can add a markup fee to your customers' transactions, enabling you to collect additional revenue from your customers.”
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
CDP docs show real conversion capabilities (auto-liquidation of onchain funds to fiat, USDC-to-USD auto-conversion into treasury, and converting crypto earnings to fiat) via docs-1, docs-14, docs-19, docs-20, indicating conversion is treated as a core, documented capability rather than a side effect. However, there's no evidence of a distinct quote endpoint, or documented exchange rates, fee schedules, or settlement-time SLAs for these conversions. Missing for 10: explicit quote API, documented conversion fee tables, documented settlement-time guarantees, stablecoin-to-stablecoin conversion documentation.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Onramp
developerEmbed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
weight 2 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
- [claimed-docs] “Embedded Wallets provide partners with seamless payment and fund management capabilities directly within their platform while maintaining th…”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
Coinbase Payments docs explicitly describe an Onramp letting end users buy crypto/stablecoins with card, Apple Pay, Google Pay, or Coinbase account delivered to a wallet, plus a Sandbox for isolated testing — matching the embedded fiat-to-stablecoin onramp story. Missing for 10: no widget code sample or explicit UI-embedding snippet shown, and no independent/hands-on corroboration beyond first-party docs.
- [claimed-docs] “Let users buy crypto with a card, Apple Pay, Google Pay, or a Coinbase account, delivered directly to their wallet”
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [claimed-docs] “Embedded Wallets provide partners with seamless payment and fund management capabilities directly within their platform while maintaining th…”
- [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
CDP's docs show extensive API/SDK/CLI coverage across virtually all payment features (onramp, offramp, checkout, payouts, custom stablecoins, x402, webhooks, treasury), and the CDP CLI even ships an MCP server exposing every API endpoint as a tool, indicating near-total API/CLI parity with any dashboard UI. Missing for 10: no explicit UI-vs-API feature parity statement and no discoverable OpenAPI spec (probe returned 404s for common spec paths), so full completeness/discoverability can't be fully confirmed.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnBVNKnone0/10No 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.
ai-native userRead the product's source under an open license
weight 2 · round drawnBVNKnone0/10BVNK 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.
Coinbase Payments (CDP)none0/10Coinbase 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.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
Payouts offramp — stories about payouts offramp in this arenaPayouts offramp
Stories about payouts offramp in this arena
Batch
ops leadRun mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status
weight 2 · round drawnBVNKnone0/10Evidence 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'.
Coinbase Payments (CDP)none0/10Evidence confirms CDP supports sending fiat/crypto payouts from a custodial account and paying USDC onchain to any wallet, but nothing in the pack documents a batch or bulk payout API, a single-call multi-payee operation, or per-item status reporting for mass disbursements.
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Offramp
ops leadRecipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
weight 2 · round drawnBVNK 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.
- [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
Docs confirm off-ramp functionality — converting stablecoins/USDC to fiat and depositing to bank accounts via ACH, Fedwire, Swift, and SEPA rails (docs-2, docs-14, docs-19) — implying multi-currency support (USD, EUR, GBP) across supported regions. However, no evidence provides a published, explicit list of supported currencies or countries, which the story specifically asks for. Missing for 10: an explicit published table/list of supported countries and currencies, and independent confirmation of real-world payout coverage.
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
Payouts
developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
weight 3 · round drawnBVNK'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.
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
- [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
Docs confirm programmatic stablecoin payouts to wallet addresses (fund a USD treasury and pay out USDC onchain to any wallet, or send payouts/disbursements in fiat or crypto from a custodial account) plus webhook-based status notifications for tracking events. However, there's no evidence of a 'stored recipient' concept, no detailed settlement-status API docs (e.g., payout lifecycle states), and no OpenAPI spec was found (probe-2 returned 404s) to confirm the full request/response tracking flow. Missing for 10: stored-recipient/beneficiary management, explicit payout status/settlement lifecycle documentation, and independent corroboration of end-to-end settlement tracking.
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [claimed-docs] “Receive real-time HTTP notifications when things happen across your CDP integration.”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnBVNKnone0/10No 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.
ai-native userControl data retention and deletion
weight 2 · round drawnBVNKnone0/10BVNK'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.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnBVNKnone0/10No 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.
Settlement treasury — stories about settlement treasury in this arenaSettlement treasury
Stories about settlement treasury in this arena
Settlement
finance leadSettlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume
weight 2 · round drawnBVNKnone0/10No 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.
Coinbase Payments (CDP)none0/10Evidence covers payment rails, payouts, checkouts, and treasury flows, but there is no documented settlement-timing SLA per rail, no published fee schedule, and no mention of accounting-consumable statements or reports. The only 'settlement details' reference is a vague migration note with no actual content shown.
- [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
Treasury
finance leadMove value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
weight 2 · round to BVNKBVNK 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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
- [claimed-docs] “Automatically on-ramp to crypto and send to blockchain addresses.”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
CDP docs describe multiple building blocks for fiat↔stablecoin movement: auto-liquidation of onchain funds into a custodial account, fiat payouts via ACH/Fedwire/Swift/SEPA, converting crypto earnings to fiat, and treasury funding/payout flows (fund USD treasury, pay out USDC onchain) via CLI/SDK. This covers most of the 'rebalancing' story but is spread across separate features rather than a single documented end-to-end internal transfer/rebalancing workflow, and there is no dashboard evidence for these treasury operations (only API/CLI/SDK). Missing for 10: a unified internal transfer ledger view, dashboard-based rebalancing UI, and independent/hands-on confirmation of the full fiat↔stablecoin loop.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Send payouts and disbursements in fiat or crypto from a custodial account”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance
Stories about stablecoin acceptance in this arena
Acceptance
developerAccept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically
weight 3 · round to BVNKBVNK'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.
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
Docs describe a full checkout/payment-acceptance flow: provisioning stable onchain addresses that auto-credit a custodial account, a two-step auth/capture checkout API with developer control over auth timing, partial captures and voids, plus migration guidance from the older Commerce Charge API to the newer Checkouts API with settlement details. This covers create-payment, present-address/flow, and confirm-settlement programmatically. Missing for 10: no independent/hands-on developer confirmation of the checkout flow working end-to-end, and no concrete code sample or OpenAPI spec (probe found openapi.json 404) showing the settlement confirmation call.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept stablecoin payments at checkout with a two-step auth and capture flow, without onchain complexity”
- [claimed-docs] “Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additiona…”
- [claimed-docs] “You control auth, capture timing, partial captures, voids”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.cdp.coinbase.com/openapi.json, https://docs.cdp.coinbase.com/swagger.json, https://docs…”
Chains
developerThe platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10The 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.
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
Docs repeatedly reference USDC support (auto-convert customer USDC, USD treasury payouts in USDC, custom stablecoins backed by USDC) and mention EVM/Solana wallet support, but there is no explicit enumeration of USDT or other stablecoins, nor a clear list of supported chains/networks a developer could match against customer holdings. Missing for 10: explicit multi-stablecoin coverage (USDT, DAI, etc.), a documented list of supported blockchain networks, and any independent confirmation of chain/stablecoin breadth.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
Fiat settlement
finance leadTake crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto
weight 3 · round to BVNKBVNK 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.
- [claimed-docs] “Crypto converted and received in fiat: Accept stablecoin payments from customers and receive fiat currency in your account”
- [claimed-docs] “Use your fiat balance to send stablecoins, or fund in stablecoins and pay out in fiat.”
- [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
- [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
Docs explicitly describe auto-crediting custodial accounts with optional auto-liquidation, accepting USDC and auto-converting to USD into a treasury, and sending fiat payouts via ACH/Fedwire/Swift/SEPA — directly matching the finance-lead's request to settle crypto receipts in fiat and avoid holding crypto on the books. Missing for 10: independent/hands-on verification of the auto-liquidation flow in production, and clearer accounting/reconciliation documentation for finance teams.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send fiat out of a custodial account using ACH, Fedwire, Swift, or SEPA rails”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Convert crypto earnings to fiat and deposit to bank accounts.”
Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access
Stories about stablecoin agent access in this arena
Agent payments
ai-native userAn agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured
weight 3 · round to Coinbase Payments (CDP)BVNKnone0/10Evidence 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.
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
- [claimed-docs] “To create a rule that links a fiat virtual account to a crypto blockchain address, send the `POST /payment/v1/rules` request”
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
CDP documents agent-native payment flows: x402 lets agents pay for or charge APIs programmatically, and the Wallet MCP lets an AI assistant check balances, send funds and pay via a connected Coinbase Wallet, backed by CDP-managed key custody. However, the pack shows no explicit documentation of human-configured spend limits, allowances, or scoped permission policies constraining what an agent can autonomously spend — the closest control language ('you control auth, capture timing, partial captures, voids') applies to merchant checkout capture, not agent wallet spend caps. missing for 10: documented spend-limit/allowance configuration APIs, explicit human-set policy controls for agent wallets, and independent/hands-on confirmation of scoped-authority enforcement.
- [claimed-docs] “Monetize APIs and digital content with payments over HTTP, designed for AI agents and programmatic commerce”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
Agent wallets
ai-native userAgents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move
weight 2 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
CDP provides SDK-based wallet issuance where Coinbase secures private keys (coinbase-payments-gh-1) and exposes wallets to AI agents via MCP (coinbase-payments-docs-18) and x402 payments (coinbase-payments-docs-12/13), showing agents can hold and use funds programmatically. However, the evidence never documents scoped keys, granular policy controls, or explicit spend/limit enforcement mechanisms for agent-held wallets—only general custody and signing features. Missing for 10: explicit policy/permission engine docs, documented per-agent spend limits, and independent verification that agents cannot exceed defined bounds.
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
Protocols
ai-native userThe platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10No 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.
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bvnk.com/llms.txt # BVNK API Documentation > Complete API documentation for BVNK payment infrastru…”
CDP has dedicated x402 docs with SDK/endpoints for both paying ("Pay for an API or resource with x402 and the CDP SDK") and charging ("Charge for your endpoints with x402 and the CDP SDK"), plus a Coinbase Wallet MCP server enabling agents to pay with x402, and an official CDP CLI/MCP exposing API endpoints as tools — this is concrete named-protocol support with SDKs/endpoints, not just aspirational blog content. Missing for 10: no explicit ACP/MPP/AP2 protocol mentions, so coverage is limited to x402 among the named protocols.
- [claimed-docs] “Pay for an API or resource with x402 and the CDP SDK.”
- [claimed-docs] “Charge for your endpoints with x402 and the CDP SDK.”
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
- [probe] “official CLI documented at https://docs.cdp.coinbase.com/cdp-cli/skill”
Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance
Stories about stablecoin issuance in this arena
Issuance
founderIssue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly
weight 2 · round to Coinbase Payments (CDP)BVNKnone0/10The 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.)
Coinbase's docs explicitly describe a custom-stablecoin issuance product ('Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves'), directly matching the story's core ask. However, the evidence pack contains no detail on eligibility/gating requirements, application process, minimum volume, or any independent corroboration of how the program actually works in practice. Missing for 10: honest disclosure of gating/eligibility requirements, independent/hands-on corroboration, and technical detail on minting/redemption mechanics beyond the single overview line.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
Yield
finance leadThe economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly
weight 2 · round to BVNKMarketing 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.
- [claimed-docs] “Put idle balances to work with built-in rewards.”
Coinbase Payments (CDP)none0/10Evidence covers custom stablecoin issuance backed 1:1 by USDC with Coinbase managing issuance/redemption/reserves, but no documentation of reserve composition, attestations, or yield/rewards eligibility and regulatory caveats for finance leads is present.
- [claimed-docs] “Issue your own branded stablecoin backed 1:1 by USDC, with Coinbase managing issuance, redemption, and reserves.”
Wallets balances — stories about wallets balances in this arenaWallets balances
Stories about wallets balances in this arena
Balances
finance leadMy business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
weight 3 · round to BVNKBVNK 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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “Send stablecoins or cryptocurrencies from your BVNK account.”
- [claimed-docs] “Spin up stablecoin and fiat wallets for your customers.”
- [claimed-docs] “Put idle balances to work with built-in rewards.”
- [claimed-docs] “Accept payments globally in stablecoins. Settle in fiat.”
Docs confirm custodial accounts that hold stablecoin balances (auto-credited addresses, auto-conversion to USD, treasury funding/payout in USDC) — docs-1, docs-19, docs-20 — but nothing in the evidence pack states availability constraints, supported geographies, or KYC/eligibility gating for opening such an account. Missing for 10: documented geographic availability/restrictions, explicit KYC/onboarding gating disclosure, and any stated balance limits or custody terms.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
- [claimed-docs] “Fund a USD treasury and pay out USDC onchain to any wallet, with the CDP CLI or SDK.”
Virtual accounts
developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
weight 2 · round to BVNKBVNK 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.
- [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
- [claimed-docs] “This process allows for the ability for the `CUSTOMER ENABLED` wallet to complete payouts to other bank accounts using their virtual account…”
CDP docs explicitly describe provisioning 'stable onchain addresses' that auto-credit a custodial account (dedicated deposit addresses), and webhooks can watch up to 100 wallet addresses per subscription, which supports per-customer address-based reconciliation. However, there's no explicit documentation of named virtual accounts for fiat, nor clear guidance on mapping addresses to specific customer IDs for reconciliation workflows. Missing for 10: explicit per-customer/customer-ID tagging or named virtual account docs, fiat-side dedicated account numbers, and independent/hands-on confirmation of reconciliation accuracy at scale.
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “watch up to 100 wallet addresses under a single subscription with `wallet.activity.multi`.”
- [claimed-docs] “Accept customer USDC, auto-convert it to USD, and collect it in your treasury, with the CDP CLI or SDK.”
Wallets
developerCreate wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
weight 2 · round to Coinbase Payments (CDP)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.
- [claimed-docs] “On BVNK, you can create and manage both crypto and fiat wallets through the Portal or API.”
- [claimed-docs] “A channel is a unique, repeated-use blockchain address that can receive crypto or stablecoins at any time. The address never changes.”
- [claimed-docs] “Create virtual accounts in USD, EUR, GBP for your business or customers.”
- [claimed-docs] “Spin up stablecoin and fiat wallets for your customers.”
CDP SDK docs confirm programmatic wallet creation for EVM/Solana with CDP securing private keys, plus provisioning of custodial onchain deposit addresses that auto-credit accounts, and a sandbox for testing wallet features without real funds. However, the pack lacks explicit detail on per-customer/multi-tenant wallet architecture or deeper key-custody semantics beyond high-level statements. missing for 10: detailed per-customer wallet provisioning patterns, explicit key custody/security model documentation (MPC, backups, exportability)
- [github] “Client libraries for managing EVM and Solana wallets while relying on CDP to secure private keys.”
- [claimed-docs] “Provision stable onchain addresses that auto-credit a custodial account, with optional auto-liquidation”
- [claimed-docs] “Send crypto onchain from a non-custodial wallet where CDP handles signing and broadcasting”
- [claimed-docs] “Sandbox is a fully isolated testing environment for custodial features without connecting real funds.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableBVNKn/aBVNK 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.
- [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
- [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”
Coinbase Payments (CDP)n/aCoinbase 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.
- [claimed-docs] “The CDP CLI includes an MCP server (`cdp mcp`) that exposes every API endpoint as a tool.”
- [claimed-docs] “Give your AI assistant a wallet. Coinbase Wallet MCP connects any AI to your Coinbase Wallet. Check balances, send funds, swap tokens, sign …”
- [probe] “official MCP server documented at https://docs.cdp.coinbase.com/get-started/build-with-ai/base-mcp”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableBVNKnone0/10No 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.
Coinbase Payments (CDP)n/aCoinbase 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.
ai-native userSelf-host the core product
weight 3 · not comparableBVNKn/aBVNK 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.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableBVNKn/aBVNK 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.