Give your agent a budget. Not your card.
Connect the agent you already run: a Claude or ChatGPT connector, an n8n flow, your own script. It gets a card or a stablecoin wallet with hard limits, every cent lands in the ledger under its own name, and the payments that matter wait for your signature.
Without Orla
Your card number lives in a prompt
The bot pays for APIs with your real card in an env var. One poisoned page it reads can talk it into spending.Access is all or nothing
Either the agent cannot touch money at all, or it holds the same keys you do. Nothing in between.Nobody writes down what it spent
Receipts scatter across five dashboards. By month end you know the bot cost something, not what or why.Every agent, what it spent, what waits for you.
A row per agent with its status and this month's spend, and a queue of its proposals on top. Open a row to change one agent: its spaces, card, wallet and keys.
A stablecoin budget that cannot overdraw.
Top the agent's wallet up in USDT or USDC and the balance is the entire budget: nothing stands behind it, so no mistake can spend more than you deposited. On its own it only pays addresses you marked trusted, inside its daily cap. Anything past those limits is not refused, it becomes a proposal for you to sign.
- USDT and USDC on Base, Ethereum and Polygon. USDT on Tron.
- An address the agent read in an invoice or a note is refused. That is exactly how a poisoned document turns into somebody else's money.
- Withdraw the remaining balance any time, fee free.
It can buy from pages that charge per request.
A service answers with a price over the web's payment-required standard, the agent pays in USDC and gets the content. No account, no API key, a receipt in about a second. It cannot buy at all until you set both ceilings: the most one request may cost, and its daily cap. The price is written by the other side, so buying without a ceiling is agreeing to a number nobody on your side has seen.
- Name the services it may pay, or leave it open
- Over a limit is refused outright, not queued: the other side is waiting on an open connection
A card that only buys what you allowed.
Give the agent a virtual card drawn on the space's card pool. Its balance is moved out of the pool, so a mistake cannot spend what is not there, and the fence is checked while the payment is still waiting for an answer: which merchant categories, which named merchants, which channels, and the most per payment, day, week and month.
- Blocking cash machines is the sensible reflex
- Amount ceilings sit with the card issuer, the merchant fence with Orla. Both run before money moves.
- Freezing the agent freezes the card
It proposes. You sign.
An agent can never sign a payment, release an approved one, or widen its own access. Not a setting, a rule.
The agent drafts the payment: who, how much, what for.
Every payment while it observes, and anything over its limits, waits here.
You sign and the money leaves. Even in a space with no approval rules.
Booked under the agent's name, old and new value kept on every edit.
Every cent it spends carries its name.
Card purchases, wallet sends and per-request buys land in the ledger as the agent's own rows, not as mystery lines on your statement. The Agents report splits what each one decided on its own from what a person signed, and every autonomous spend sends you a note with what is left of the day's cap.
- Spending grouped by agent, top payees named
- An agent a teammate connected shows up too, marked as theirs
Narrow by default. You open each door.
An agent reaches nothing until you give it a space, and it never does more than you could yourself, recomputed on every call.
Three roles
Analyst reads. Bookkeeper records and files paperwork. Treasurer may also put payments forward.
Hard limits
Specific accounts, a USD ceiling per rolling day, a call cap, an expiry date.
Observation first
A new agent's writes wait as proposals until you have watched it work and flip the switch.
A stop button
Freeze acts on the agent's very next call. Disconnect kills every key and grant.
Masked by default
It sees amounts, dates and names. Card numbers, IBANs and wallet addresses stay hidden unless you deliberately open them.
Two ways in
Add Orla as a connector in Claude or ChatGPT, or mint a key for your own script. Same rules behind both.
The rules, spelled out.
Who signs
A person. The agent proposes, never signs, never releases.Stablecoins
USDT and USDC on Base, Ethereum and Polygon. USDT on Tron.Per-request buys
Refused without both ceilings: per request and per day.Card fence
Categories, named merchants, channels. Per payment, day, week and month.Wallet budget
The balance is the ceiling. Withdraw the rest any time, fee free.Fees
A small percentage on the agent's own spending. Withdrawals are free.Fresh agents
Start observing. Writes queue as proposals.Plans
Agents come with paid plans. The wallet is an add-on. Pricing has the numbers.Let it do the work. Keep the signature.
Connect an agent in a minute from Claude, ChatGPT, n8n or your own code. Agents come with paid plans, and the agent wallet is an add-on. Pricing has the current numbers.