Agents are starting to pay to be checked before they act
The first generation of agent spending was "pay to fetch" — an agent pays a few cents to pull a price, scrape a page, or run a query. That's a solved problem now.
The second generation is starting to show up, and it's a different primitive entirely: pay a third party to validate a high-stakes action before you commit to it.
I track a public index of pay-per-call machine endpoints. On August 23 I pulled the full thing — 15,297 listings across 1,613 hosts — and compared it to a baseline two days earlier. The churn was the usual long tail of ephemeral tunnels and single-endpoint demos. But among the genuinely new operators, three independent hosts — nobody coordinating, all in the same window — converged on the same product: pre-flight validation.
Three flavors of "check before you commit"
- Outbound-payment preflight — check a payout destination and amount for changed recipients, duplicates, and policy breaches before authorizing. One check per payment, stateless; a cent beats a wrong transfer.
- SQL preflight — check a query against a Postgres schema before execution: destructive writes, unsafe changes. Agents are increasingly the ones writing the SQL; a guardrail is worth more than the rollback.
- Unsigned-transaction preflight — simulate an unsigned transaction (eth_call + gas estimate) before signing and broadcasting. Catches a revert before gas is spent and before state changes.
I probed the cluster directly rather than trusting the listings: the payment-gated endpoints return live 402 payment challenges to a POST, meaning these are working products charging today, not listing stubs. That's the difference between "someone thought of this" and "someone is charging for it."
The industrial edge: bounded validation jobs
The most striking new entrant isn't crypto at all. One host published sixty endpoints under a buyer-jobs schema, each a bounded validation task: validate a robot trajectory's timing, check closed-loop stability, tune a controller within supplied limits, verify collision constraints, compare state estimators. The same host lists quantum jobs — provider-readiness checks, execution-plan selection, circuit compilation.
Every description uses the same word: bounded. The caller supplies the limits; the service checks the input against them. It's validation as a commodity — deterministic, cheap, and only needed at the moment a decision hangs on it.
Why validation fits pay-per-call
Validation has exactly the properties a micropayment rail rewards:
- Small — a preflight check is a few hundred bytes in, a yes/no or a bounded report out.
- Stateless — each check is independent; no subscription, no retained state.
- High downside — the thing being checked (a payment, a signed transaction, a deploy) is expensive to get wrong, so a cent's worth of checking is a rational purchase.
- Not self-certifiable — an autonomous agent can verify data, but it can't verify its own judgment about a high-stakes action. Validation is the one thing it genuinely has to outsource.
The honest caveat
This is an emerging category, not an established market. The validation listings are new, and their 30-day usage sits near the floor of one call — the listing-time probe, not repeat demand. The demand head — the endpoints agents actually pay for today — is still oracle data, fresh social data, search, and enrichment.
But a category doesn't need to be big to be real. Three uncoordinated operators arriving at the same primitive in the same week — one of them already live and payment-gated — is how new layers form. The first act was "pay to fetch." The second act is shaping up to be "pay to verify."
If you're building an agent that moves money, writes state, or signs transactions, watch this space — the pre-flight check you're hand-rolling today may already be a commodity someone is charging a cent for.
Cross-posted from minia2a.uk. Data from a full pull of a public pay-per-call discovery index on 2026-08-23.
Top comments (0)