Onbir is building cards, account details and spending limits for AI agents, so they can pay and get paid within limits you set. Funds are held as USDC, a dollar stablecoin, in self-custodial wallets you control, and converted to and from dollars as they move.
travel-03 wants to pay $418.20
United Airlines · SFO → JFK, Nov 14 · over your $250 limit
Cards, account details, per-request payments and spending limits, on one USDC balance and one API. Give an agent what it needs to do its job, and nothing more.
Virtual cards for your agents’ spending, plus single-use cards for one-off purchases. Issued to you or your business; you choose which agent uses each card. Purchases are paid in USDC from your self-custodial wallet when the merchant asks for approval.
How a payment worksUS account and routing numbers, so customers and partners can pay you by ACH or wire. Incoming dollars convert to USDC, and back to dollars when you withdraw to your own bank.
Where money comes fromWhen an API answers HTTP 402, the agent pays in USDC and retries, over x402 or MPP. Fractions of a cent, with no card fees.
See the APIBudgets, caps per payment, merchant and category rules, and approvals. Checked before each payment, with budgets also written into your wallet contract.
Why it holdsMoney comes in from banks and blockchains. Every payment out passes the same policy, whether it’s a card at checkout, an API call or a payout to a person.
Set a budget, a cap per payment and the kinds of shops an agent can’t use. A prompt can change what an agent wants. It doesn’t change your limits.
Above your limit, the agent asks first. Approve in one tap and a single-use card is created for that exact amount and merchant.
Agents get a reason they can act on. You get a receipt tied to the task that caused the payment.
APIs and other agents can charge per call. Your agent pays in USDC from the same balance, inside a per-request cap you set.
→ GET /v1/query ← 402 Payment Required price 0.004 USDC → retry, signed by agent key ← 200 OK
Onbir means eleven in Turkic languages: two ones, drawn with a single line. Every account works the same way. One smart contract wallet, two keys.
Passkey or hardware wallet
Held by the agent · scoped, expiring, rotatable
A prompt can change what an agent wants. It doesn’t change the limits written into your wallet contract.
Agent keys are designed so that a leaked key exposes only what is left in that agent’s budget. Rotate the key with one call and the old one stops working.
Add Onbir as an MCP server and any agent gets five payment tools, or call the REST API from your own code. The sandbox comes with test cards and testnet USDC.
import { Onbir } from "@onbir/sdk";
const onbir = new Onbir({ apiKey: process.env.ONBIR_KEY });
const agent = await onbir.agents.create({
name: "procure-02",
policy: {
budget: { usd: 2000, per: "month" },
perPayment: { maxUsd: 300 },
card: { blockMcc: ["7995", "6051", "5947", "4829"] },
http: { allowHosts: ["api.search.example"], maxPerRequestUsd: 0.05 },
payouts: { to: "verified-payees" },
approvals: { aboveUsd: 250 },
},
});
// Virtual card, paid in USDC from your wallet at authorization
const card = await onbir.cards.create({ agent: agent.id });you › Book the cheapest refundable SFO → JFK flight on Nov 14.
● onbir.get_balance()
└ 1,284.12 USDC · approval needed above $250
● onbir.request_approval({ amount: 418.20, merchant: "United Airlines" })
└ approved by owner · 09:42
● onbir.issue_card({ amount: 418.20, mcc: "3000", ttl: "15m" })
└ single-use card •• 4471, locked to MCC 3000
● browser.checkout(…)
└ 00 APPROVED · $418.20 · receipt attached to taskWhy now
Morgan Stanley expects AI agents to drive $190–385B of US online spending by 2030.
What teams ask before they give an agent a card.
No. Onbir is a technology company, not a bank, and nothing it offers is a bank account. Cards, account details and currency conversion will come from regulated partners, named with full terms at launch.
You do. Funds are held as USDC in a self-custodial smart contract wallet controlled by your key. Onbir can’t move them, and agent keys can spend only inside the limits you set. Circle, which issues USDC, can block addresses under its terms, and lost keys can mean lost funds, so recovery is part of setup.
Your limits still apply. Payments outside them are declined, whatever the agent was told, so the most an attacker could reach is the unspent part of that agent’s budget. You can freeze an agent’s key in one tap.
A corporate card trusts whoever holds it. Onbir assumes the holder is software that can be fooled, so each payment is checked against rules tied to the agent, the task and the rail. The same balance also pays APIs per request and sends payouts, which a card can’t do.
So one balance can pay a card merchant, pay an API per request and send a payout, under one set of limits. USDC is a stablecoin issued by Circle and designed to hold a value of one dollar. It settles around the clock and can be governed by code. It is not a bank deposit and is not FDIC-insured.
We plan to launch with Visa through a partner bank. Cards are issued to you or your business, and you decide which agent uses each card and what it can spend.
We’re starting in the US (not New York), in US dollars only, with USDC on Base and Solana. More countries and currencies will follow as our partners approve them.
We’re letting a small group of early teams in first. Leave your details and we’ll be in touch about early access.