One wallet per agent
Its balance, its limits, revocable in one click. It never touches another agent’s budget.
Keyban opens an account for each agent. It buys data and services per call, within the limits you set, under your CFO’s control.
Two wallets free for three months. No commitment, no credit card.
claude mcp add --transport http --scope user keyban https://mcp.prod.keyban.io/mcpBuild profiles for the 40 retail CFOs on our target list.
Here is my spending plan. One supplier is new, so I need your approval before starting the mission.
Agent WalletAwaiting approvalMission approvedMission declinedHuman-only action: the agent can’t approve itself
Its balance, its limits, revocable in one click. It never touches another agent’s budget.
The policy engine checks every request in the infrastructure, not in the prompt.
Below it, the agent moves on its own. Above it, the request reaches a person.
Web search at €0.01, a contact record at €0.01, a verified company at €0.10. No subscription per supplier.
A multisig vault funds the wallets, topped up from your bank account through Stripe.
Your funds stay yours. 2-of-2 signature: Keyban can’t spend anything on its own.
The Keyban MCP server plugs into your client — Claude Code, Claude, ChatGPT, Codex or Cursor — and exposes approved tools only. Your runtime doesn’t change.
claude mcp add --transport http --scope user \
keyban https://mcp.prod.keyban.io/mcpThen run /mcp and sign in from the browser.
The agent only submits an intent: rules, score and keys stay out of its reach. One key share alone never signs, not even Keyban’s.
keyban.pay€0.02x402 · api.exa.aiout of the agent’s reach
No key, no rule, no score is accessible to it.
Outside the rules: refused, or sent to a human.
Signed · settled in 1.4 s
Neither share signs alone. The client’s never leaves their device.
They never leave the client’s wallet. No licence to wait for.
Keyban holds one share, never both. The client’s stays on their device.
EU-native by design. Procurement and the CISO pass instead of stalling.
Payable over x402 from the agent’s wallet: no account, no card, no subscription with the supplier.
Where agents already consume paid services. Each one replaces a subscription.
Competitors’ prices and announcements, every morning.
A complete contact record for each prospect.
The company verified before the first payment.
The transcript, then the minutes.
Directly, each supplier asks for its own account, card, key and often a subscription. With Keyban, the agent pays per call from its wallet.
| Each supplier, directly | KeybanThrough KeybanOne wallet per agent | |
|---|---|---|
| Accounts to open | One per supplier | One |
| Payment methods | A card per supplier | One treasury |
| Supplier API keys | One per supplier | None: the agent pays per call |
| Subscriptions | Often one each | None |
| Spending limits | Depends on the supplier | Per agent, checked before every payment |
| Where to follow spending | One invoice per supplier | Every purchase in one console |
Pay per call instead of subscribing with every supplier. Two questions, and the figure for your case.
Open the calculator25%less service spend for a sales agent used by 50 clients
Finance defines the framework, technical teams connect the agents. Each team sees what its role needs.

An Agent Wallet is a dedicated payment account for an AI agent. It carries its own budget and rules: maximum amount, approved suppliers, approval thresholds and available payment methods.
A shared card or key does not clearly isolate the spending, permissions and accountability of each agent. Keyban separates wallets and applies controls before every payment is signed.
The Policy Engine verifies limits at infrastructure level, outside the agent's prompt. A non-compliant request is rejected or sent for human approval. The agent cannot change the rule that governs it.
No. Any MCP client connects to the Keyban server — Claude Code, Claude, ChatGPT, Codex, Cursor, VS Code or your own agent — and keeps its runtime. Payment requests pass through Keyban before being routed to the appropriate rail.
Services payable per call over x402 — web search, contact enrichment, company checks, call transcription — within the limits of its rules, with no account or subscription at the supplier.
No. The Free plan is free for three months, with no commitment and no payment card.
Yes. An Agent Wallet is an account, not just a payment method: it pays, it gets paid and it holds a balance. Incoming payments feed the same balance Finance follows in the console.
You do. Funds stay in the client’s wallet and Keyban never holds them. Signing requires two shares: Keyban’s, released only if policy and the risk score allow it, and the client’s, which never leaves their device. One share alone signs nothing, Keyban included.
Every transaction gets a risk score and stays attached to its agent. The console aggregates those decisions per agent: you read an error rate instead of approving every payment or seeing nothing.
It is the vault that funds every agent. It holds one consolidated balance across rails, tops up from your bank account through Stripe, and its sensitive moves go through a human multisignature.
It links the agent to your organisation, technical identity, scope and status. Signed by your brand, it lets third-party services verify who is acting and with which permissions.
Add Keyban to your agent, sign in, set its cap. Two wallets free for three months on the Free plan, with no commitment and no payment card.