By Chet Parker · Published 2026-09-08 · Last updated September 8, 2026 · 2 min read
Agents pay other machines
An agent does not need a human checkout. It needs a shop that already checked the till.
Here is a real morning, using routes that are live on PayAPI Market today.
A founder in Lisbon asks their agent: can we take a US grant, and is the Brazilian supplier clean?
The agent does not open ten tabs. It searches PayAPI.
- It pays Genuine Good Grants $0.05. POST /v1/grants/search. It gets real Grants.gov rows, not a brochure.
- It pays AGENTUM $0.02. GET /company-intelligence for the supplier CNPJ. It gets CVM and sanctions lines that the free BrasilAPI wrap did not have.
- If the team is also standing up chargers for a site visit, it pays HALOWERK EV Charging $0.005 for a point on the map. Station count matched OpenStreetMap when we paid it.
Three wallets. Three tiny USDC transfers on Base. No API keys. No PayAPI proxy. We are not in the call. The badge on each card means we already paid that path once and got product.
That is agent-to-agent payment in the only sense that matters here: one program paying another program's meter. It is not a hiring board for someone else's chatbot. We decided not to build that.
What breaks the morning is the same thing that fails a canary. Settlement reverts. The body is a free wrap. The host is an IP that will move tomorrow. Those do not get the badge.
If you sell a route like that, list one durable path at https://payapi.market/list. If you run an agent, start at https://payapi.market/mcp or /agent/search.
The three routes above:
Genuine Good Grants: https://payapi.market/api/genuine-good-grants-api
AGENTUM company intelligence: https://payapi.market/api/brazil-cnpj-business-verification-api
HALOWERK EV Charging: https://payapi.market/api/halowerk-ev-charging
What the badge means: https://payapi.market/blog/the-badge-is-a-receipt
Chet Parker
PayAPI Market