Try itExperimental
See what an agent can do with BVNK before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.bvnk.com/api/wallet | head -2 # keyless → 401recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Compliance risk — stories about compliance risk in this arenaCompliance riskevidence →
Stories about compliance risk in this arena
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dxevidence →
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Onramp conversion — stories about onramp conversion in this arenaOnramp conversionevidence →
Stories about onramp conversion in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Payouts offramp — stories about payouts offramp in this arenaPayouts offrampevidence →
Stories about payouts offramp in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Settlement treasury — stories about settlement treasury in this arenaSettlement treasuryevidence →
Stories about settlement treasury in this arena
Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptanceevidence →
Stories about stablecoin acceptance in this arena
Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent accessevidence →
Stories about stablecoin agent access in this arena
Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuanceevidence →
Stories about stablecoin issuance in this arena
Wallets balances — stories about wallets balances in this arenaWallets balancesevidence →
Stories about wallets balances in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where BVNK stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Official SDKs · Scoped API keys · MCP server · Machine-readable spec · Full data export · An 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 · The platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration
Subscribe to events via webhooks
✓7/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—–
Rely on versioned APIs with a documented deprecation policy
~3/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—–
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Compliance risk — stories about compliance risk in this arenaCompliance risk
Stories about compliance risk in this arena
Customer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves
—–
See who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried
—–
The platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at
—–
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
I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
~5/10
Rehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically
~5/10
Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
~5/10
Onramp conversion — stories about onramp conversion in this arenaOnramp conversion
Stories about onramp conversion in this arena
Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
~5/10
Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Payouts offramp — stories about payouts offramp in this arenaPayouts offramp
Stories about payouts offramp in this arena
Run mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status
—–
Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
~6/10
Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
~6/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Settlement treasury — stories about settlement treasury in this arenaSettlement treasury
Stories about settlement treasury in this arena
Settlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume
—–
Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
✓8/10
Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance
Stories about stablecoin acceptance in this arena
Accept 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
✓8/10
The 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
—0/10
Take 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
✓9/10
Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access
Stories about stablecoin agent access in this arena
An 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
—0/10
Agents 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
~3/10
The platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration
—0/10
Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance
Stories about stablecoin issuance in this arena
Issue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly
—–
The economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly
~2/10
Wallets balances — stories about wallets balances in this arenaWallets balances
Stories about wallets balances in this arena
My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
~5/10
Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
✓7/10
Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
~6/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 7/10 | Cclaimed | |
Take 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 C Fiat settlement | finance lead | Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance | 3 | full | 9/10 | Cclaimed | |
Accept 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 C Acceptance | developer | Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance | 3 | full | 8/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement C Payouts | developer | Payouts offramp — stories about payouts offramp in this arenaPayouts offramp | 3 | partial | 6/10 | Cclaimed | |
I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language C Abstraction | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 3 | partial | 5/10 | Tprobed | |
My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly C Balances | finance lead | Wallets balances — stories about wallets balances in this arenaWallets balances | 3 | partial | 5/10 | Cclaimed | |
Rehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically C Sandbox | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 3 | partial | 5/10 | Cclaimed | |
An 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 C Agent payments | ai-native user | Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end C Treasury | finance lead | Settlement treasury — stories about settlement treasury in this arenaSettlement treasury | 2 | full | 8/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 7/10 | Tprobed | |
Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching C Virtual accounts | developer | Wallets balances — stories about wallets balances in this arenaWallets balances | 2 | full | 7/10 | Cclaimed | |
Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics C Wallets | developer | Wallets balances — stories about wallets balances in this arenaWallets balances | 2 | partial | 6/10 | Cclaimed | |
Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries C Offramp | ops lead | Payouts offramp — stories about payouts offramp in this arenaPayouts offramp | 2 | partial | 6/10 | Cclaimed | |
Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times C Conversion | developer | Onramp conversion — stories about onramp conversion in this arenaOnramp conversion | 2 | partial | 5/10 | Cclaimed | |
Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product C Onramp | developer | Onramp conversion — stories about onramp conversion in this arenaOnramp conversion | 2 | partial | 5/10 | Cclaimed | |
Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards C Webhooks | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 2 | partial | 5/10 | Cclaimed | |
Agents 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 C Agent wallets | ai-native user | Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access | 2 | partial | 3/10 | Tprobed | |
The economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly C Yield | finance lead | Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance | 2 | partial | 2/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
The 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 C Chains | developer | Stablecoin acceptance — stories about stablecoin acceptance in this arenaStablecoin acceptance | 2 | none | 0/10 | ||
The platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration C Protocols | ai-native user | Stablecoin agent access — stories about stablecoin agent access in this arenaStablecoin agent access | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Customer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves C Kyc | ops lead | Compliance risk — stories about compliance risk in this arenaCompliance risk | 2 | none | untested | none yet | |
Issue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly C Issuance | founder | Stablecoin issuance — stories about stablecoin issuance in this arenaStablecoin issuance | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Run mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status C Batch | ops lead | Payouts offramp — stories about payouts offramp in this arenaPayouts offramp | 2 | none | untested | none yet | |
See who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried C Licensing | founder | Compliance risk — stories about compliance risk in this arenaCompliance risk | 2 | none | untested | none yet | |
Settlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume C Settlement | finance lead | Settlement treasury — stories about settlement treasury in this arenaSettlement treasury | 2 | none | untested | none yet | |
The platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at C Screening | ops lead | Compliance risk — stories about compliance risk in this arenaCompliance risk | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 42 stories with headroom
What would move BVNK’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
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".
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
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.
Stablecoin agent access — stories about stablecoin agent access in this arenaAn 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
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence of a bulk data export feature or open-format data portability; documentation covers payments, wallets, and APIs but nothing about exporting account/transaction data for migration or leaving the platform.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
No evidence of AI-generated insights, analytics, or suggestions surfaced within BVNK's product based on user data; documentation covers payment infrastructure, wallets, APIs, and webhooks only.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
Missing: any chat/NL command interface, agent SDK, or documented natural-language operation mode.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
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.
Showing the top 8 of 42 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 25 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Bvnk docs22 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Rely on versioned APIs with a documented deprecation policy
- Define rules that trigger actions automatically on events
- I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
- Rehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically
- Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
- Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
- Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
- Do everything through the API that I can do in the UI
- Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
- Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
- Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
- Accept 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
- Take 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
- Agents 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
- My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
- Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
- Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
docs.bvnk.com11 stories
- Set up automations that run autonomously in the background
- Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
- Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product
- Do everything through the API that I can do in the UI
- Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
- Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
- Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
- Take 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
- My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
- Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching
- Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
llms.txt9 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
- Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards
- Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
- Do everything through the API that I can do in the UI
- Accept 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
- Agents 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
bvnk.com8 stories
- Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times
- Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries
- Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement
- Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end
- Take 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
- The economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly
- My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly
- Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics
GitHub README4 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language
- Agents 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
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.bvnk.com/api/wallet | head -2 # keyless → 401reproduced$ curl -si https://api.bvnk.com/api/wallet | head -2 # [redacted]less → 401 HTTP/2 401 server: CloudFront
$curl -sL https://docs.bvnk.com/llms.txt | head -3reproduced$ curl -sL https://docs.bvnk.com/llms.txt | head -3 # BVNK API Documentation > Complete API documentation for BVNK payment infrastructure—crypto payments, wallets, and financial services
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
0 of 15 testable claims verified · 0 contradicted → integrity 0/100
19 distinct capability claims found in BVNK’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
0
Verified
15
Unverified
0
Contradicted
10
Undersold
Unverified (23)
“Real-time webhook notifications for account changes”
Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboardspartialproof ↗
“Real-time webhook notifications for account changes”
“Sandbox environment simulates pay-ins and payouts consistently for testing”
Test against a sandbox environment without touching production datafullproof ↗
“Sandbox environment simulates pay-ins and payouts consistently for testing”
Rehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministicallypartialproof ↗
“Create and manage both crypto and fiat wallets via Portal or API”
Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semanticspartialproof ↗
“Define rules linking a fiat virtual account to a crypto blockchain address”
Define rules that trigger actions automatically on eventspartialproof ↗
“Define rules linking a fiat virtual account to a crypto blockchain address”
Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matchingfullproof ↗
“Transfers API (v3) handles wallet-to-wallet currency conversion, replacing legacy Quote API”
Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement timespartialproof ↗
“Transfers API (v3) handles wallet-to-wallet currency conversion, replacing legacy Quote API”
Rely on versioned APIs with a documented deprecation policypartialproof ↗
“Embedded Wallets let partners offer branded payment and fund management within their own platform”
Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semanticspartialproof ↗
“Accept stablecoin payments from customers and receive the funds as fiat in your account”
Accept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmaticallyfullproof ↗
“Accept stablecoin payments from customers and receive the funds as fiat in your account”
Take 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 cryptofullproof ↗
“Channels provide a persistent, reusable blockchain address for receiving crypto/stablecoins”
Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matchingfullproof ↗
“Customer-enabled wallets can pay out to external bank accounts via their virtual account”
Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countriespartialproof ↗
“Create virtual accounts in USD, EUR, and GBP for businesses or customers”
Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matchingfullproof ↗
“Send stablecoins or cryptocurrencies programmatically from a BVNK account”
Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlementpartialproof ↗
“Automatically convert fiat to crypto and send it on-chain to blockchain addresses”
Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement timespartialproof ↗
“Provision stablecoin and fiat wallets on behalf of your customers”
Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semanticspartialproof ↗
“Earn built-in rewards/yield on idle balances”
The economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainlypartialproof ↗
“Convert between fiat and stablecoin balances freely — fund in one, pay out in the other”
Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to endfullproof ↗
“Convert between fiat and stablecoin balances freely — fund in one, pay out in the other”
Take 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 cryptofullproof ↗
“Accept global stablecoin payments and settle them in fiat currency”
Accept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmaticallyfullproof ↗
“Accept global stablecoin payments and settle them in fiat currency”
Take 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 cryptofullproof ↗
Undersold (10)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my languagepartialproof ↗
Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my productpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Agents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can movepartialproof ↗
My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestlypartialproof ↗
Claims outside our story set (3)
Real capability claims found in BVNK’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“API access secured via Hawk authentication scheme”
source ↗“Partners can add a markup fee to customer transactions to earn extra revenue”
source ↗“Link virtual cards directly to stablecoin balances”
source ↗
Business model
Sales-only: no pricing page anywhere — bvnk.com funnels to 'Speak to an expert'; became part of Mastercard in August 2026 (~$1.8B) after the $2B Coinbase acquisition fell through.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
