Use cases for pay-per-call x402 endpoints and notes on the agentic payments ecosystem.
RSS feed →Use cases
An agent planning logistics or energy dispatch needs a forecast for a point and a lead time, not a dashboard. One x402 call returns GFS — temperature, precipitation and wind — decoded from GRIB, no account.
Use cases
A well-formed mobile number can still be a disposable VoIP line, a recently ported SIM, or an absent subscriber. A live HLR lookup tells an agent which, before it spends on an OTP.
Use cases
Energy and agriculture agents need HDD, CDD and GDD over a period, not raw temperatures to sum themselves. One x402 call computes them from ERA5 with a declared method, no account.
Use cases
A valid IBAN says nothing about who owns it. Verification of Payee checks the name against the account holder in one call — the control that stops an agent from paying a fraudster.
Use cases
An agent often needs the weather that actually happened at a location on a date. One x402 call returns ERA5 reanalysis — temperature, precipitation and wind — decoded from GRIB, no account.
Ecosystem
The exact x402 mechanics an autonomous agent runs to call a paid endpoint — discover the resource, get the 402, sign the payment, settle through a facilitator, and replay.
Use cases
ESG reports and parametric triggers need a departure from a stable baseline, not a raw reading. One x402 call returns the ERA5 value, the 1991-2020 WMO normal, and the anomaly between them.
Use cases
Reinsurance and climate risk need a ranking, not a reading — where a season ranks in the historical record. One x402 call returns the empirical percentile, return period and the sample size it used.
Use cases
An agent reasoning about EU law needs the consolidated act or article text at a date, addressed by its stable identifier — CELEX or ELI — not a paraphrase from memory. One call returns text, status and validity window.
Use cases
An agent that reasons about French law needs the consolidated article text as it stood on a date, plus its in-force or repealed status — not a paraphrase from training data. One call returns both.
Ecosystem
How an autonomous agent finds a paid API with no human in the loop — semantic search over the CDP x402 Bazaar, paid tools exposed through MCP, and per-origin manifests.
Use cases
Before an agent stores, dials or texts a number, it should know the number is well-formed, in which region, and what line type it is. One offline call answers all four in milliseconds.
Use cases
A parametric policy pays on a measured threshold — frost days, a one-day rainfall max, a wind gust. One x402 call returns standard ETCCDI climate indices from ERA5, with the thresholds it applied.
Use cases
An OCR pass over a scanned invoice produces a near-miss IBAN — one wrong digit, an unreadable character. One paid call recomputes the check digits and recovers the missing characters before an agent pays the wrong account.
Use cases
A reporting agent needs the climate balance of a month or season — mean temperature, total rainfall, mean wind — not 90 daily lookups to roll up itself. One x402 call returns it from ERA5.
Use cases
For due diligence and regulatory watch an agent needs the text delta of a statute between two dates, not two full texts to diff itself. One call returns the structured segments and a unified patch.
Use cases
An agent monitoring a statute does not need to re-read the full text each time — it needs the version timeline. One compact call returns every version of a French or EU article with its dates and status.
Ecosystem
Autonomous agents are a poor fit for accounts, API keys and card subscriptions. The HTTP 402 status code plus a wallet lets an agent pay per call with no onboarding — here is why that model fits.
Ecosystem
A sourced, neutral comparison of the three agentic-payment standards — x402, Google's AP2, and the Stripe/Tempo Machine Payments Protocol — from the point of view of a developer wiring an endpoint.
Use cases
Before an agent disburses to an IBAN, it should know the account is valid, which bank it belongs to, and whether it is reachable over SEPA. One paid call answers all three.
Use cases
An autonomous agent disbursing funds should clear the beneficiary's bank against sanctions lists first. Here is the one-call check and where it fits the x402 loop.
