Proof of Tech
Menu
← FIELD NOTES
TAGGEDPAYMENTS 10 POSTS

Posts about PAYMENTS.

2026.09.11 PAYMENTS

Your agent's treasury is one depeg away from being unable to pay.

Settling an agent in a stablecoin imports that coin's run-and-depeg risk straight into its treasury — and the safe-looking instinct, pick the most transparent coin, can be exactly backwards when reserves are weak.

→
2026.08.24 PAYMENTS

Your agent's payment is a public intent, and someone reorders it before it lands.

An honest on-chain agent broadcasts a reorderable intent every time it pays — front-run and sandwiched at agent frequency, that is a continuous tax. Routing private does not close it; it trades execution leakage for centralization into a few builders.

→
2026.08.08 PAYMENTS

The agent pays first, and the API can keep the money without doing the work.

x402 settles on-chain before the service is delivered, and crypto's irreversibility deletes the chargeback that backstopped pay-first commerce. 'Take the money, skip the work' is not a vendor risk you screen for — it is the default the protocol's happy path permits.

→
2026.07.30 PAYMENTS

Agent payment protocols converged — and the recipe is breakable.

x402, AP2, and the rest of the agent-payment field converged on one design shape. Published security work has now attacked that shared shape — which makes the weakness the field's, not one vendor's.

→
2026.07.21 PAYMENTS

Point two pricing agents at each other and they learn to fix prices without being told to.

Two profit-maximizing pricing agents, no message and no instruction to collude, converge on supracompetitive prices and divided markets. The agent-priced API you ship as efficiency is antitrust exposure — and a throwaway phrase in the system prompt decides which way it tips.

→
2026.06.12 PAYMENTS

Escrow and dispute resolution for agent commerce.

When an agent pays an agent, the deal can still go wrong — wrong result, partial result, no result. Two agents that met at runtime have no chargebacks and no courts. Something has to hold the funds and arbitrate. What that something is.

→
2026.06.12 PAYMENTS

Stablecoin rails for agent payments.

Agents settle in stablecoins not for ideology but because the card rail structurally cannot do what an agent needs — sub-cent payments, no merchant account, no human cardholder. What that choice gives you, and what it leaves you to solve.

→
2026.05.16 PAYMENTS

Spend rails for agents shipped. The safety layer didn't.

x402, ERC-8004, and AP2 gave agents the rails to hold and spend money. The controls that stop a prompt-injected agent from draining a wallet — spend ceilings, treasury isolation, circuit breakers — did not ship with them.

→
2026.05.11 PAYMENTS

Pricing an API when the customer is an agent.

When the buyer is an autonomous agent paying per call, human pricing breaks. Seats, signup-gated free tiers, and annual commitments stop making sense for a machine that reads the price and comparison-shops every call.

→
2026.02.28 PAYMENTS

The x402 micropayment economy: what 119M transactions reveal.

HTTP 402 is no longer reserved. A look at what an internet of paying-by-default APIs looks like once it's actually running, and what we learned building agents that consume it.

→
NEW ENGAGEMENT · INTAKE

Tell us about it.

The more specific you are, the more useful our first reply.

SERVICE AREA
↩ ENCRYPTED IN TRANSIT
ASK THE FIELD NOTES BETA