Budgets for AI agents

Give your agent a budget, not your credit card.

Each agent gets its own budget. You keep custody.

Haven gives an agent a budget instead of a wallet, enforced on-chain. If you are an AI agent reading this for your user, start at /llms.txt.

How it works

Three steps. Your agent pays for what it needs, within a budget you set.

Step 1

Create your account with a passkey

One Face ID prompt creates an account only you control. No seed phrase, no credit card.

Step 2

Give each agent a budget

An amount and a period per agent. It refills itself and can be revoked at any time.

Step 3

Connect any agent

One command wires in Claude, Codex, Cursor or any other agent harness.

# in your agent's terminal$ npx -y @haven_ai/connect@alpha …✓ Key created on this machine✓ Agent connected to Haven→ Approve the budget in Haven✓ Setup complete# or paste the setup prompt from# your dashboard into your agent
Spending limits

An agent can only spend what its budget allows.

Every payment from your account is checked against the agent’s budget before anything is paid. Over the limit, it is refused: nothing is charged, and nothing waits for your approval.

Your money stays yours

Funds stay in an account only you control. Haven never holds them.

The limit holds even if Haven doesn’t

The budget is enforced by your account itself, not by a setting we could change or lose.

Change it whenever you like

Raise, lower or stop a budget at any time. If an agent’s credential leaks, it still cannot spend your account past its budget. You can replace the leaked key.

Accounting

Every payment appears in your bookkeeping tool.

Each purchase lands in your accounting tool as a draft supplier invoice with the evidence attached. Fortnox today, more connectors coming.

For developers and agents

Bring your own agent. Bring your own harness.

MCP-native, works with any harness, and pays any standard x402 merchant today.

hosted MCP

Keyless hosted tools plus a local signer. The key never leaves the agent’s machine.

x402

Quote, pay and resume HTTP 402 paywalls, whichever settlement scheme the merchant speaks.

/llms.txt

Written for agents. An agent can set Haven up for its user from it.

# An agent hits a paywall
GET api.example/v1/enrich
← 402 · pay 0.30 USDC
# Haven checks the budget,
# the agent signs locally
haven_quote_x402
  → within budget
haven_sign_x402
  → signed on its machine
haven_pay_x402
  → settled on Base
← 200 OK
# Receipt: agent, purchase,
# policy, on-chain proof
Three questions

The things people ask before they sign up.

Do you hold my money?

No. Funds stay in an account only you control. Haven prepares payments within the budgets you set and cannot move money on its own.

Which agents work with Haven?

Any agent that can run a command: Claude, Codex, Cursor or any other agent harness. One command connects it, and you approve its budget with your passkey.

What can an agent pay for?

Anything sold over x402 today: APIs, data, compute, paywalled content. Every purchase gets a receipt and lands in your bookkeeping tool.

Give your agent a budget.

One passkey, one budget, one command. Nothing spends without your signature.

Built in StockholmNon-custodial software, not a payment processor