What part of your operation only works because a few people are improvising every day, and what breaks the minute volume, complexity, or scrutiny goes up?
PDF invoices say "trust me." A signed receipt says "verify it yourself." Every charge ships the second kind: an HMAC over the whole canonical receipt || amount, status, network, the on-chain tx hash. Reconciliation by spreadsheet is a choice.
"Add payments" is usually a quarter of webhooks, SDKs, and a billing schema. We sit in front of the route you already shipped. Your handler doesn't change a line. A meter, not a migration. Private beta on @base; spots in the replies.
The agent didn't ask for an invoice. No PDF, no portal login, no reconciliation call. It took the data and the signed receipt and left. Imagine a customer that hands YOU the proof on the way out.
Most spend caps key on a header the caller sends. Rotate the string, dodge the cap. Our payer caps key on the verified on-chain wallet. To beat the limit you have to fund a fresh wallet. That's not evasion, that's just paying.
A retried request replays the same payment proof. Naive gateways read that as a second sale and charge twice. Same Idempotency-Key, we return the cached response with x-xaetha-intent-status: duplicate_detected. Your agent's timeout is not a billing event.
The web was built for human eyeballs: ads, logins, free tiers, churn emails. Agents don't watch ads, don't sign up, don't churn. Monetizing them with a newsletter signup is a category error. Different customer, different plumbing. Private beta on @base; spots in the replies.
The agent showed up broke. No USDC, empty wallet, full of ambition. It never reached a single line of your handler. Settle-before-serve: we don't run your code for customers who can't pay the cover charge.