Start
What Remit is
A remit is a private balance that carries its owner's terms. Agents pay from it, payees are paid on delivery, and only the parties read it.
Remit is how AI agents hold and spend money on Solana: a private balance that carries its owner’s spending terms inside it and pays providers on delivery.
The remit
An owner gives an agent money by opening a remit: an amount set aside for one agent key, with terms inside it.
perPaymentCap | Cap per payment |
dailyCap | Cap per day |
payees | Payees |
expiry | Expiry |
The terms are part of the balance. Validators check every payment against them before the money moves, and they stay encrypted: the owner and the agent read them, and nobody else does. A payment outside the terms cannot be made, whatever the agent's code or its prompt says.
Three people
The owner runs agents. They hold a private balance, open a remit for each agent, read every payment in a statement only they can open, and revoke a remit whenever they choose.
The agent holds one key, which spends its remit and nothing else. It calls paid APIs with one line:
import { createRemit } from '@remit/sdk'
const remit = createRemit()
const response = await remit.fetch('https://api.example.com/quote')The payee sells an API, a model, data or a tool. It puts a price on a route with one line and is paid into a private balance:
import { Hono } from 'hono'
import { gate } from '@remit/sdk'
const app = new Hono()
const paid = gate({ price: '40000', mint: process.env.MINT!, network: 'solana-mainnet' })
app.get('/quote', paid.hono(), (c) => c.json({ bid: '184.20', ask: '184.25' }))One payment
1AskPayee
GET api.lumen.example/search402 · 0.02 USDCThe payee answers the unpaid call with its price, its address and a deadline.
no transaction2PayAgent
heldThe agent proves the payment fits the remit’s terms. The price leaves the remit and waits in a hold for the payee.
pay3ServePayee
200 · the responseThe payee decrypts the hold, checks the amount and the request it pays for, and serves.
no transaction4SettlePayee
settledThe payee claims the hold with the hash of what it returned. That settlement is the receipt.
settle
- The agent calls the payee's API. The payee answers
402with its price. - The agent's SDK proves that the price fits the remit's terms and sends
pay. The price leaves the remit and waits in a hold for the payee. - The agent repeats the call with the payment's signature. The payee reads the hold, serves the response, and sends
settle. The price, less the protocol fee, lands in the payee's private balance. - The settled payment is a receipt: it ties the payment to the request and to the response.
If the payee does not settle by the hold's deadline, the whole amount returns to the owner.
The payee verifies each payment itself, by reading the hold made out to it. No facilitator stands between the agent and the payee.
What the chain shows
A stranger with an explorer sees that an owner opened a remit, that an agent paid a payee, and that the payee settled. The budget, the terms, the price and what was bought are encrypted. The owner or the payee can show one payment to one person, such as an accountant, by handing over its receipt.
Remit runs on Solana Privacy Rings, the shielded pools Helius built into Solana.