Your agent spends within its remit.

Give an AI agent a budget it has to justify. You approve one hold on PayPal, every purchase is checked against what it was planned for, and whatever is left comes back to you.

Scroll to watch one week

Your agent writes a plan.

Groceries, dog food and a birthday gift, each with a reason you can check: last month’s orders, what’s running out, what you asked for. Change any line before you approve.

You approve it once.

PayPal holds $176.50 in your own account. Nothing has been spent yet, and only you can ever add more.

Dog food, $32.50.

It fits its line, and a separate purpose check agrees it’s what the line is for. Remit captures exactly $32.50 from the hold.

Groceries, $43.40.

Paid from Groceries. Every purchase is recorded with the store and the agent’s reasoning, so you can read the week back later.

A phone case, $18.99.

The agent tried to put it under Groceries. The purpose check says no. Nothing moves, and the reason goes in your ledger.

Your agent asks for $104.50.

The gift Sam wants costs $144.50, and its line has $40. The agent can ask for more. Only you can say yes.

Groceries again.

$43.40 from Groceries, and a $2.00 delivery fee from the shared buffer. Lines never borrow from each other.

The week closes.

$55.20 was never spent. It never left your PayPal account, and the hold is released.

The rules are written in code, not in a prompt.

Your agent can be wrong, rushed or talked into things. Remit doesn’t depend on it behaving: every purchase passes the same checks before any money moves, and PayPal itself enforces the hold.

Six rules. Every call. No exceptions for a persuasive prompt.

House rules

Your agent decides what to buy. The wallet decides whether it can.

Only you approve money
A plan or top-up opens only after you approve it on PayPal.
Lines stay separate
A purchase can use its own line, then the shared buffer. Never another line.
No overspending
Remit checks first, and PayPal refuses any capture larger than the hold.MAX_CAPTURE_AMOUNT_EXCEEDED
A second opinion
A separate model checks each purchase against its line. If it can’t be reached, Remit refuses.
Refusals stay on record
Every refused purchase is in your ledger with its reason.
One purchase at a time
Two purchases can never slip through the same check at once.

Plug in the agent you already use.

Remit is an MCP server. Add one config block and a token to any MCP-compatible agent, and it can see its lines, propose a plan and pay, one purchase at a time.

The agent never holds PayPal keys. Every call goes through your wallet and its rules.

For developers

Remit’s MCP server gives any agent four tools. It holds no PayPal keys; every call goes to your wallet.

get_balance what’s left on each line
request_budget propose a plan
request_topup ask you for more
spend one purchase, one line
spend({ line: "groceries",
        amount: 43.40,
        title: "Grocery order",
        reasoning: "2nd order this week" })

→ paid · $1.20 left on this line

Let your agent shop. Keep the say on money.

Sign in to read this week’s plan, approve what your agent asks for, and see every purchase it made.