Software that can pay

A night watchman cannot swipe a bank card for every tiny question a stall might ask after dark: is ice still arriving, is the board still blank, did a neighbor post a price. Humans pay in batches. Software can pay per request if the fee is a fraction of a cent and the wallet is capped.

That product is agentic HTTP payments: a program sends an ordinary web request, the server answers “payment required,” the program pays a tiny dollar on a public-ledger rail, and the answer comes back. No card network for a one-cent ping. No human on the phone at 2 a.m.

A local application is a night helper that can pay for one job — one price ping, one ice alert — with a hard cap. Who fills the cap. Who sees the spend. What happens when the cap is empty. What happens if the helper is wrong and pays the wrong server.

Honest limits: this is early. A protocol can be open and still have almost no stalls using it. A helper without a cap is a drain, not a tool. A helper that holds the stall’s whole till is a theft waiting for a bug. Invent a small, named, capped payment — not an unbounded agent, and not a new bank card for software.

If the invent cannot be spoken as “this program may spend this much for this one ask,” it is not ready for the night board.