Self-host the payment path
Run x402 endpoints and AMP channels inside your own infrastructure. No platform sits between your agent and your customer's payment.
Teams choosing how AI agents pay for APIs, tools, and services often compare managed platforms with self-hosted open-source stacks. QBT Labs builds the open-source path: x402-compatible payments, AMP-style channels, encrypted signer isolation, and a spend policy engine for production agent workflows.
Open-source SDKs and MCP tooling teams self-host
Managed agent payment platform
x402-compatible HTTP 402 flow via @qbtlabs/x402
Platform-managed credit and subscription rails
AMP-style payment channels (in development) for repeated calls
Platform-mediated metering
Per-agent budgets, daily caps, recipient allowlists, chain restrictions
Platform policies configured in dashboard
Encrypted vault with process-isolated signer over Unix socket
Custodial / hosted signer
Per-call receipts with request ID, amount, asset, chain, recipient, status
Platform reporting
Base, Solana, Cardano; AMP roadmap adds Hydra L2
Platform-defined chain support
Bring your own facilitator or run your own
Platform facilitator
MIT open source
Commercial platform
Run x402 endpoints and AMP channels inside your own infrastructure. No platform sits between your agent and your customer's payment.
Per-agent budgets, daily caps, recipient allowlists, chain restrictions, and audit logs are first-class — not features bolted on top of a wallet.
MIT-licensed packages. Any x402-compatible facilitator or client interoperates with QBT-Labs-powered endpoints.
QBT Labs ships open-source x402-compatible payment tooling, AMP-style channels, an encrypted vault with process-isolated signer, and a spend policy engine — production-ready primitives for autonomous agent payments.