Sandbox · simulated, no real money moves
Give your agent a budget. Watch the rules hold.
Pick a task and an agent works through it, paying by card, per API request and by payout from one USDC balance. Change its limits and run it again. Every decision names the rule behind it.
Wallet
self-custodial · two keys6,500.00USDC
One balance for every agent. Your key controls it; agent keys spend only inside their policy.
Add money
US account details, to get paid
Routing
•••• 0110Account
•••• 4471Agents
spent this monthRun a task
7 tasksTry your own payment
Pick a task. An agent runs it against its policy, and every payment shows up in Activity with the rule that decided it.
- Start with Book a flight over the limit. You’ll be asked to approve.
- Then Hold the agent to the deal: a $15 order turns into $45 and still fits the limit.
- Survive a prompt injection to see what a hijacked agent can’t do.
- Change a limit on the left and run a task again.
Activity0 events
- The same APIThe calls you see follow the planned Onbir API and MCP tools: get_balance, pay, issue_card, request_approval and list_payments.
- The same rulesPolicies are checked before every payment, whatever the agent was told, and budgets are also written into your wallet contract.
- Your money, your keysFunds sit as USDC in a self-custodial wallet you control. Onbir can’t move them, and agent keys can be frozen in one tap.
Design partners
Build it with us.
We’re working closely with a small group of teams whose agents spend money today, or will soon. You decide what we build first.
- Sandbox keys and early access to cards, account details and payouts as our partners approve them
- Design-partner pricing when you go live
- A direct line to the founder, and fixes in hours, not days
- Your rails and the countries you pay move up the roadmap
What we ask: a 10-minute call, quick feedback every week, and a non-binding letter of intent if it’s a fit.