Synthetic chart — label externally as design sample, not market data.

Why now

Agents ship faster than credit-card forms refactor.

Overall: builders are tired of dev-tool sites that hide pricing and pretend “AI” fixes infra. This page: why settlement and metering clarity are the next bottleneck after MCP discovery—wallet-native intents beat ticket queues for autonomous software.

Three collisions

Discovery won. Any serious agent ships with MCP manifests. Operators now compete on metering clarity and receipt honesty.

Costs became composable. Burst workloads favor per-second metering; static SKUs penalize exploratory agents unless you inflate buffers.

Compliance wants provenance. Finance teams insist on cryptographic trails for programmatic spend — ephemeral API keys pasted into repos fail every audit playbook.

Example throughput normalization

Each bar expresses a hypothetical index (0–100) after normalizing disparate vendor units — useful for typography demos, not financial guidance.

Signup friction (lower is better)
Receipt granularity
Provider switch cost
Ops toil vs agent velocity
CSS-only viz · illustrative axis weighting

What credible launch looks like

Open receipts humans can reconcile, MCP flows that degrade gracefully offline, Postgres backups auditors can reconstruct, and egress math that survives a skeptic’s spreadsheet. Ship those before adjectives.