- 3limit changes, passkeys (P-256) verified on chain (Metal testnet, 12 Nov): 2 of 2, co-signer a test key
AI agents spend. You sign off.
Over its limit, an agent asks; you sign the exact terms with Face ID.
Your own test company, deleted after 24 hours.


No endorsement impliedOne /try run, a test company's sample invoice, test money. What's real?
Why Purser
Agents do the work. The CFO keeps the say.
- Face ID on the exact terms
Above a limit, the CFO signs amount, payee and account. Change one cent and it fails.
- Limits in code, not prompts
Claude agents read and propose; Purser's code holds the limits.
- Rails that refuse too
Airwallex, Metal and Visa via Airi apply their own controls.
- Booked and checkable
Every payment is booked; its signed receipt checks offline.
About Purser
Claude agents decide. Code and the rails enforce.
- ReadClaude reader agent
- CheckChecker agent (Claude) decides, code enforces the limits (see evals)
- CodeCoder agent (Claude) books account and VAT
- SignYou, with Face ID
- PayPayer agent (Claude) proposes, the rail and code enforce (see evals)
These are the payables agents, in Purser Cloud and /try.
On record
Each lock, on record
- 6,461tests passing ↗
- 24sandbox and testnet runs
- 147Airwallex sandbox API calls logged
- 233Metal testnet transactions
- 449Claude calls with request ids
- 63refusals on record
All runs and test companies on record, counted at build.
The core run (the main run, 3 Nov, Northwind Outdoor; agents Sourcing, Support and Treasury): 86 Metal testnet payments, 24 of 24 decisions by Claude, purchase #24 refused on chain. The film, 3:58 ↗