QBT Labs builds the payment stack for autonomous agents. Not wallets. Not checkout flows. Infrastructure — policy, settlement, receipts, and audit — so agents can pay for APIs and tools without human intervention.
The AI payments stack follows the public x402 HTTP 402 payment model, MCP's tool-integration pattern, and stablecoin settlement rails. QBT Labs adds the missing production controls around those standards: budgets, allowlists, signer isolation, receipts, and audit logs.
“A wallet can sign. Production infrastructure decides whether the agent should sign, records why it signed, and leaves a receipt finance can audit later.” — Aggelos Kappos, Founder @ QBT Labs
The x402 tooling installs in under 5 minutes:
npm install @qbtlabs/x402Full docs on GitBook. For production infrastructure, payment channel setup, or policy engine integration — contact QBT Labs at qbtlabs.io.
A branded explainer for autonomous agent payments, budgets, receipts, settlement, and policy controls.
ReferenceDefinitions for x402, AMP, MPP, agent wallets, facilitators, and settlement.
BlogChoosing the right payment protocol for AI agents.
BlogPolicy-controlled agent payments — budgets, allowlists, signer isolation.
GuideHow to price, meter, and settle AI-agent API usage with x402 and AMP.
BlogChannel state, settlement, and security.
Proof pointThe live operating vertical that exercises this stack under real volume.
Building AI agents that need to pay for services? Let's talk about your use case.
Contact Us