Circle vs BVNK

Agent access

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

   weight 2 · round drawn
   Circle✓fullprobed8/10

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

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

   proof ↗⚑ flag

   BVNK✓fullprobed8/10

   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.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Circle~partialprobed6/10

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

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

   proof ↗⚑ flag

   BVNK~partialprobed6/10

   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.

   • [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”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Circle
   Circle✓fullprobed8/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Circle
   Circle✓fullprobed8/10

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

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

   proof ↗⚑ flag

   BVNK~partialprobed3/10

   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”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Circle✓fullprobed8/10

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

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

   proof ↗⚑ flag

   BVNK✓fullprobed8/10

   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.

   • [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…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Circle
   Circle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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'.

   • [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.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Circle✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   BVNK✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to BVNK
   Circle~partialprobed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed6/10

   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.

   • [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.”

   proof ↗⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

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

   ⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Circle
   Circle~partialprobed5/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [probe] “official CLI documented at https://github.com/bvnk/agent-wallet-cli”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to BVNK
   Circle—none0/10

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

   ⚑ flag

   BVNK✓fullclaimed7/10

   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.

   • [claimed-docs] “The sandbox environment provides a consistent simulation experience for pay-ins and payouts across all customer accounts.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to BVNK
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed3/10

   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.

   • [claimed-docs] “The Transfers v.3 API replaces the legacy Quote API for wallet-to-wallet currency conversion.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to BVNK
   Circle~partialclaimed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed6/10

   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.

   • [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.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Circle—none0/10

   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.

   • [claimed-docs] “When a resource changes state, Circle sends an HTTP POST to the endpoint you configure so your application can react.”
   • [claimed-docs] “Create and manage wallets, transfer, swap, and bridge USDC across blockchains, execute smart contracts, and discover or pay for services. Al…”

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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.”

   proof ↗⚑ flag

Kyc

1. ops leadCustomer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Licensing

1. founderSee who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried

   weight 2 · round drawn
   Circle—none0/10

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

   ⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Screening

1. ops leadThe platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Abstraction

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

   weight 3 · round drawn
   Circle~partialprobed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialprobed5/10

   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”

   proof ↗⚑ flag

Sandbox

1. developerRehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically

   weight 3 · round to BVNK
   Circle—none0/10

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

   ⚑ flag

   BVNK~partialclaimed5/10

   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.

   • [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.”

   proof ↗⚑ flag

Webhooks

1. developerMoney movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards

   weight 2 · round drawn
   Circle~partialclaimed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed5/10

   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.

   • [claimed-docs] “Webhooks provide real-time, automated notifications for changes in your BVNK account.”
   • [claimed-docs] “BVNK uses **Hawk authentication** for secure API access.”

   proof ↗⚑ flag

Conversion

1. developerConversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times

   weight 2 · round drawn
   Circle~partialprobed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed5/10

   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.

   • [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”

   proof ↗⚑ flag

Onramp

1. developerEmbed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product

   weight 2 · round to BVNK
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed5/10

   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.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to BVNK
   Circle~partialprobed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialprobed7/10

   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…”

   proof ↗⚑ flag

2. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Circle—none0/10

   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.

   ⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Batch

1. ops leadRun mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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'.

   ⚑ flag

Offramp

1. ops leadRecipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries

   weight 2 · round to BVNK
   Circle~partialclaimed5/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed6/10

   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.

   • [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.”

   proof ↗⚑ flag

Payouts

1. developerSend stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement

   weight 3 · round drawn
   Circle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed6/10

   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.

   • [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.”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Circle—none0/10

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

   ⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Settlement

1. finance leadSettlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume

   weight 2 · round drawn
   Circle—none0/10

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

   ⚑ flag

   BVNK—none0/10

   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.

   ⚑ flag

Treasury

1. finance leadMove value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end

   weight 2 · round to BVNK
   Circle~partialclaimed5/10

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

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

   proof ↗⚑ flag

   BVNK✓fullclaimed8/10

   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.

   • [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.”

   proof ↗⚑ flag

Acceptance

1. developerAccept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically

   weight 3 · round to BVNK
   Circle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   BVNK✓fullclaimed8/10

   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.

   • [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.”

   proof ↗⚑ flag

Chains

1. developerThe platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold

   weight 2 · round to Circle
   Circle~partialprobed4/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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.”

   proof ↗⚑ flag

Fiat settlement

1. finance leadTake crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto

   weight 3 · round to BVNK
   Circle~partialclaimed6/10

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

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

   proof ↗⚑ flag

   BVNK✓fullclaimed9/10

   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.

   • [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.”

   proof ↗⚑ flag

Agent payments

1. ai-native userAn agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured

   weight 3 · round to Circle
   Circle~partialprobed6/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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.”

   proof ↗⚑ flag

Agent wallets

1. ai-native userAgents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move

   weight 2 · round to Circle
   Circle~partialprobed6/10

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

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

   proof ↗⚑ flag

   BVNK~partialprobed3/10

   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”

   proof ↗⚑ flag

Protocols

1. ai-native userThe platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration

   weight 2 · round to Circle
   Circle~partialprobed7/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

   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.

   • [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…”

   proof ↗⚑ flag

Issuance

1. founderIssue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly

   weight 2 · round drawn
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK—none0/10

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

   ⚑ flag

Yield

1. finance leadThe economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly

   weight 2 · round to BVNK
   Circle—none0/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed2/10

   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.

   • [claimed-docs] “Put idle balances to work with built-in rewards.”

   proof ↗⚑ flag

Balances

1. finance leadMy business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly

   weight 3 · round to BVNK
   Circle~partialclaimed4/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed5/10

   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.

   • [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.”

   proof ↗⚑ flag

Virtual accounts

1. developerIncoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching

   weight 2 · round to BVNK
   Circle—none0/10

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

   ⚑ flag

   BVNK✓fullclaimed7/10

   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.

   • [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…”

   proof ↗⚑ flag

Wallets

1. developerCreate wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics

   weight 2 · round drawn
   Circle~partialprobed6/10

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

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

   proof ↗⚑ flag

   BVNK~partialclaimed6/10

   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.”

   proof ↗⚑ flag