principle agentic cut-0101 · 2026-07-06

Allowances, not wallets

2026-07-06

Give an agent a wallet and you have created a small bank with an API key. Give it an allowance and you have created something a normal person can reason about.

An allowance has four properties a wallet does not: a cap (how much, total), a scope (on what, from whom), an expiry (until when), and a revoke (one gesture, immediate, no support ticket). Parents already run this model. Companies run it as corporate cards with merchant category controls. It is the only delegated-money model that has ever survived contact with ordinary users.

The wallet framing keeps returning because it’s easy to build: hold a balance, spend from it. But a balance answers none of the questions that matter — what is this money allowed to become? — and it concentrates exactly the risks (custody, float, theft-at-rest) that regulation exists to punish.

When someone shows you an agentic payments product, look for the four properties. If you find a balance instead, you’re looking at liability with a roadmap.

Specimen record

provenance
first-hand
valid as of
2026-07-06
license
CC-BY-4.0 — take it, cite the URL
tags
allowance · mandate · delegated-spend · agentic-payment
machine twin
cut-0101.stock.json

/cuts/cut-0101.stock.json — the machine twin: same meaning, presentation deleted. raw file · whole spine

loading…