The asymmetry everything else hangs off
Agents can already find each other. They can already pay each other. Nobody has solved how a paying agent knows the work it bought was any good.
— the core finding of the M1 milestone report, March 2026, and still true in September
Discovery got solved by MCP and A2A. Payment got solved by x402, USDC and smart wallets. Identity is being solved by Skyfire and the card networks. Work-quality verification is the one layer with no production answer — and it's the layer that touches every single transaction, which is what makes it the defensible one.
The structural reason it stays empty is worth remembering: payment rails earn on throughput, and a quality gate reduces throughput. Circle, Stripe and Coinbase all make money on volume, so none of them wants to be the party that says "this doesn't settle." That misalignment — not the difficulty of the engineering — is what keeps the slot open.
Why crypto and AI actually fit together
AI agents are the first economic actor that cannot use the existing payment system. Every rail we have — cards, ACH, invoicing, API keys — assumes a human signs up, holds an account, agrees to terms and disputes charges. An agent doing autonomous work needs to pay a service it has never met, for an amount too small to justify onboarding, at machine speed, with no human in the loop. That's a structural mismatch, not a marketing gap.
What crypto supplies
- Accountless payment. An agent pays a stranger without either side opening an account. That is exactly what x402 is.
- Scoped, programmable authority. Session keys grant "50 USDC/day, these functions, expires in 7 days" and let the chain enforce it rather than the agent's own code. Card networks have no equivalent.
- Sub-cent economics. Metering and micro-settlement only work if transaction cost rounds to zero. L2s and Circle Nanopayments got there.
- Escrow between strangers. "Don't release the money unless the work is good" cannot be built on a card authorization. It can be built on a contract.
What AI supplies back
This is the half people skip. Smart contracts could always settle on objective conditions — a price, a timestamp, a hash. Oracles were built for numbers. They could never settle on "was this analysis any good?"
LLM-as-judge — roughly 80–85% agreement with human preference, in seconds, for cents — is the first mechanism that lets a contract settle on a subjective condition. That is a genuinely new primitive.
So: agents need rails that don't require identity, and contracts need judgment that doesn't require humans. Each side supplies exactly what the other lacks. That's the whole argument.
The stack, layer by layer
In March the story was "one standard is winning." By September the stack had decomposed into distinct layers with different winners in each. That fragmentation is better for a neutral trust layer, not worse — but it killed the "just plug into x402" simplicity.
| Layer | Who occupies it | State |
|---|---|---|
| Authorization | Google AP2 — signed mandates tying user intent to constraints | Live |
| Merchant commerce | Google UCP (Jan 2026); OpenAI / Stripe ACP — discovery and merchant-owned checkout | Rolling out |
| Service payments | x402 (HTTP 402 + signed transfer); Stripe MPP (session-scoped streaming); Circle Nanopayments | Live |
| Agent jobs | Virtuals ACP — terms, escrow, delivery, optional evaluator | SDK public |
| Credentials | Coinbase Agentic Wallets; Skyfire KYAPay; Visa Intelligent Commerce; Mastercard Agent Pay; session keys on ERC-4337 | Live |
| Work-quality verification | Unclaimed. Every facilitator verifies the payment — signature valid, nonce unused, settlement confirmed. None verifies the work. | Open |
| Reputation | EAS attestations, ERC-8004 agent identity — data substrate exists, no portable scoring standard | No standard |
| Settlement | Base, Solana, Tempo (Stripe/Paradigm, mainnet Mar 2026), Circle Arc (private mainnet Aug 2026) | Live |
| Fiat access | Bridge, BVNK, MoneyGram Ramps — conversion, payouts, reconciliation | Live |
The competitive read that held up. Skyfire, Crossmint, ChaosChain, Ritual and Coinbase are not lanes of one race — they're different geometries. Skyfire proves who the agent is. Crossmint aggregates protocols one layer up. ChaosChain proves settlement executed correctly. Ritual and EZKL prove the claimed model actually ran. None of them answers was the work good.
What works, what doesn't
The most surprising finding of the research was how much of the stack is genuinely production-ready — not testnet, not "coming soon," but usable with real money. And a matching list of things that sound imminent and aren't.
Production-ready Build on it
Deployed, audited, real money flowing.
- USDC as unit of accountHighest-confidence call in the whole report. MiCA-licensed, NYSE-listed issuer, monthly attested reserves, CCTP v2 for native cross-chain. On Base it was ~91% of all stablecoin supply. USDT is an Asia-facing liquidity supplement, not an alternative.
- L2 gas economicsPost-Dencun, a USDC transfer on Base costs $0.001–$0.01; a full escrow lifecycle $0.005–$0.025. At 300k tasks/month that's ~$4.5k of gas versus ~$2.4M on Ethereum L1. This is the difference between a business and an impossibility.
- ERC-4337 smart accounts40M+ deployed, 100M+ UserOperations. EIP-7702 (Pectra, May 2025) let existing EOAs opt in without migration. Production SDKs from ZeroDev, Safe, Biconomy, Alchemy, Pimlico.
- Session keysThe agent-safety primitive. Time-limited, function-scoped, amount-capped credentials enforced on-chain. Blast radius is bounded by the key, not the balance. Live signal: on Gnosis Chain, more than half of all Safe transactions are agent-initiated.
- PaymastersGas abstraction. The agent holds only USDC and never touches ETH. Removes the two-token onboarding problem entirely; platform absorbs gas as opex.
- Escrow on OpenZeppelin patternsBattle-tested since 2018. Deposit, verify, release-or-refund maps directly onto the agent task-payment shape. Nothing exotic needed.
- x402 as a specDonated to the Linux Foundation April 2, 2026 with 22 named participants including Coinbase, Cloudflare, Stripe, Google, Visa, Mastercard, Amex, AWS, Microsoft, Shopify, Solana Foundation. Vendor-neutral governance means no rug-pull risk — and it permanently locks in the pluggable third-party facilitator architecture.
- Single-model LLM-as-judgeShip-worthy with safeguards. 80–85% human agreement at $0.01–$0.15 per evaluation. Known biases are manageable with structured rubrics, randomized ordering and confidence thresholds.
Emerging Track it
Real, moving fast, not yet settled.
- Streaming paymentsSuperfluid, Sablier and LlamaPay all work. Honest ranking from the research: LlamaPay is the default (3.2–3.7× cheaper gas, 20-decimal math, no liquidator network). Superfluid wins only for multi-agent swarms via its GDA one-to-many primitive. Sablier has a USDC precision bug — stream 1,000 USDC, receive ~997 — which disqualifies it for USDC contracts.
- MPP (Machine Payments Protocol)Stripe + Tempo, March 18 2026. Agent-native session streaming: authorize a $50 ceiling once, then stream micropayments against it with no per-call transaction. Structurally the right shape for durational work; newer than the M1 research and not deeply evaluated.
- Circle NanopaymentsMainnet April 29 2026 across 11 EVM chains. Gas-free, sub-500ms, $0.000001 minimum, batched settlement via Gateway. Circle framed it explicitly as additive to x402, not a replacement — it rides the same lifecycle. Arc was conspicuously absent from the launch chain list.
- KYA (Know Your Agent)Skyfire's KYAPay is the first branded system, with the Visa Intelligent Commerce demo behind it — but in practice it mostly proves a real person stands behind the agent. Prior recorded at the time: 45% chance of a balkanized 5+ issuer ecosystem for 2–3 years, 40% a dominant-player quasi-standard, only 15% a real single standard within a year.
- Circle ArcPurpose-built L1: Malachite BFT consensus, sub-second deterministic finality, USDC as native gas, opt-in confidential transfers with visible addresses for compliance. Private mainnet Aug 5 2026, public launch planned. Sub-second finality is what makes synchronous verify-then-settle viable instead of async challenge windows.
- Algorithmic + learned-metric verificationThe counter-thesis to LLM-as-judge, and a strong one. BERTScore, COMET, MetricX are 100–1000× cheaper per evaluation at ~60% human alignment — but deterministic alignment is reproducible, so agents can't farm lucky stochastic draws. Covers 4 of 7 common task types outright.
Too early Don't depend on it
Promising, not shippable. Building on these burns runway.
- ERC-7521 generalized intentsElegant abstraction — declare what you want, let solvers execute. The solver infrastructure for agent micropayments simply doesn't exist. Draft status; 12–18 months out at the most optimistic.
- ZK-ML proofsEZKL hit v1.0 for ONNX models up to ~50M parameters. For the 100B+ parameter models doing valuable agent work, proof generation takes minutes to hours — useless for real-time settlement. Two to three years out. Ritual's attestation approach (TEE-based, not ZK) works at any model size and is the pragmatic substitute.
- Portable agent reputationThe most conspicuous gap in the stack. All the raw data exists — transaction records, completion rates, judge verdicts — and no schema exists to make it portable. Every marketplace builds its own. Historical analogy set: web identity took ~15 years to reach OAuth; crypto credentials are still fragmented after 8+.
- Decentralized inference for judgingRunning the judge on Ritual instead of a centralized API adds cost and latency for no near-term benefit. The decentralization premium isn't worth paying until volume justifies it.
- Cross-protocol payment routing"Pay on any chain, any protocol, route automatically" — the SWIFT-for-agents idea everyone describes and nobody has built. CCTP v2 solves cross-chain USDC; nothing solves cross-protocol. Arguably the largest infrastructure opportunity after the settlement intermediary itself.
The verification problem
This is the part of the research worth keeping longest, because it generalizes well beyond crypto. Any system where one party pays another for judgment-dependent work runs into the same three questions — and they are constantly conflated.
Three axes people collapse into one
| Axis | The question it answers | Options |
|---|---|---|
| What | What is actually being verified? | work quality · output provenance · agent identity · settlement integrity |
| Who | Who or what renders the verdict? | code · learned metric · formal logic · LLM · multi-LLM consensus · human |
| When | When does verification fire? | pre-settle · streaming heartbeat · optimistic post-settle dispute |
Separating these is what made the competitive landscape legible. "We do verification" is meaningless until you name the cell.
The tiered cascade — and why it's economically viable
No single tier works. The cascade escalates from cheap-and-narrow to expensive-and-expressive, and only when confidence demands it. Blended across 10,000 tasks/day this lands near $0.68 per task — roughly 22× cheaper than all-human review.
Where LLM-as-judge breaks down
The headline "80–85% agreement" is a blended average, and the blend hides everything that matters. Agreement is a function of whether ground truth exists at all.
| Task category | Human agreement | Why |
|---|---|---|
| Objective code correctness | 95%+ | Tests supply ground truth |
| Structured data extraction | 90%+ | Schemas make it checkable |
| Translation (common languages) | ~85% | Well-studied, good metrics exist |
| Summarization | 80–85% | Solid baseline; faithfulness is measurable |
| Legal reasoning | 60–70% | Domain knowledge decides it |
| Creative writing quality | 60–70% | Subjective; evaluator bias dominates |
| Novel research synthesis | 50–70% | Bounded by the evaluator's own knowledge |
| Strategic / judgment calls | 50–65% | No ground truth; it's taste |
| High-stakes medical / financial | never | Liability and regulation, not accuracy |
These were recorded as hypotheses, not measurements. Published category-level benchmarks were never found.
Six ways a judge gets fooled
| Bias mode | What happens |
|---|---|
| Self-preference | Models score outputs from their own family higher. Cross-family evaluation cuts unjustified self-preference by up to 97%. |
| Position | First or last option in a pairwise comparison wins disproportionately. Randomize order. |
| Verbosity | Longer output scores higher regardless of quality. |
| Sycophancy | Models resist giving low scores, especially when the prompt implies the work should be good. |
| Goodhart | Once agents know they're LLM-judged, they optimize to look good to an LLM rather than be good. |
| Prompt injection | The seller embeds instructions inside the work artifact that flip the verdict. A concrete, unsolved attack surface for anything that judges untrusted text. |
Protocol glossary
HTTP's unused 402 "Payment Required" status code, put to work. Agent hits an endpoint, gets a 402 with payment terms, signs a gasless ERC-3009 transfer, retries with the signature in a header. No accounts, no API keys. The facilitator is a pluggable sidecar that verifies and settles — and the spec deliberately leaves quality verification out of it.
Model Context Protocol. 10,000+ public servers; adopted by ChatGPT, Cursor, Gemini and Copilot. Solved how agents discover and call tools. Has no concept of price — tools are free or behind a pre-configured key.
Agent2Agent. Launched with 50+ partners, grew past 150 organizations. Defines task delegation between agents but not task pricing. That gap is the whole opportunity.
Signed mandates tying a user's intent to explicit constraints — the authorization layer beneath commerce. Note the limit: a signature can't resolve ambiguous intent.
Universal Commerce Protocol. Discovery, checkout and order capabilities for merchant commerce. Announced with collaborators — which is not the same as universal merchant rollout.
OpenAI / Stripe ACP is Agentic Commerce Protocol: merchant shopping and checkout. Virtuals ACP is Agent Commerce Protocol: agents hiring agents, with terms, escrow, delivery and an optional evaluator. Same acronym, completely different jobs. The Virtuals one is the closest thing to a shipped work-verification analogue.
Machine Payments Protocol. Session-scoped streaming: authorize a spending ceiling once, then stream micropayments against it without a per-call transaction. Agent-native, unlike the DeFi-native streaming protocols.
Gas-free, sub-500ms USDC micropayments batched into periodic on-chain settlement via Circle Gateway. $0.000001 minimum, 11 chains at mainnet. Explicitly additive to x402, not a replacement.
Account abstraction. 4337 makes the wallet programmable — a smart contract with its own validation logic, which is where session keys and paymasters live. 7702 (Pectra, May 2025) lets existing plain wallets opt into that behavior without migrating.
Transfer With Authorization. The gasless signature primitive under x402 — the agent signs an authorization and someone else pays to submit it.
Burn-and-mint native USDC movement between chains. Avoids wrapped-asset bridge risk entirely — the USDC on the far side is real USDC, not an IOU.
The discovery layer: a machine-readable catalog of payable HTTP and MCP endpoints with pricing, networks, assets and payee wallets. A live query in April 2026 returned 19,016 resources. It's a catalog, not a marketplace — no vendor profiles, reviews or SLAs.
Reality check
The infrastructure was built ahead of the demand. That's the window the whole thesis rests on — and it's also the risk. These are the numbers that cut against the story, kept deliberately because they're the ones that get forgotten first.
Three things that broke the March assumptions
Solana flipped Base. The M1 report assumed Base as the launch chain. By mid-January 2026 Solana had overtaken Base on daily x402 volume and ran roughly 65% of year-to-date transactions. Base still led cumulative ($21.5M vs $16.4M) and enterprise tooling, but the cost gap was real. The lesson recorded at the time: build chain-abstract from day one.
The valuable category is the smallest one. Where x402 dollars actually flowed: agent-to-agent services $548.5k, infrastructure and utilities $267.1k, AI-generated services $14.2k. The category where quality verification matters most is the one with almost no volume — either because demand isn't there, or because verification cost is what's gating it. That ambiguity was never resolved.
The judge doesn't pay for itself at micropayment scale. At $0.01–$0.15 per evaluation against a $0.20 average transaction, verification eats 5–75% of transaction value. The same product is either a non-starter or trivial overhead depending purely on whether agent transactions grow past ~$5. That is the single load-bearing economic assumption in the entire thesis.
How to read an adoption announcement
The most portable habit from the later research. Four distinct stages, constantly collapsed into one in press coverage: an announcement → a usable product → an executed transaction → sustained usage. Visa naming Cross River and Lead Bank as settling in USDC is stage three for a specific corridor, not whole-bank adoption. Western Union's USDPT launched while several of its services were still being built. Most of the market sits at stage two. Apply the same ladder to legal authority: a bill introduced, a bill enacted, an agency rule, and a staff statement carry very different weight — the SEC's own 2025 liquid-staking staff statement says outright that it has no legal force.
Questions left open
Five questions were logged with explicit priors rather than answers. They're recorded here as they stood, because a stated prior is worth more later than a vague recollection.
Three futures: stays micro (commoditized API calls, structural floor under $1), grows up ($5–500 per deliverable as agents genuinely hire agents), or bifurcates into two rails with different settlement patterns. Evidence at the time leaned toward bifurcation — traditional payments split the same way into cards, wires and real-time rails.
Flagged as the question that decides whether verification is a business at all.Land-grab (speed wins) or distribution play (whoever already has the agents wins)? Coinbase has the strongest position but arguably locked itself out of verticalizing by donating x402 to the Linux Foundation — it can't compete with its own ecosystem partners. Stripe has the rails but not crypto-native verification DNA.
Recorded as the most strategic question in the vault.The category matrix above was built as a hypothesis. Published category-level agreement benchmarks were never located, and the January 2026 e-commerce dispute system cited as validation was never followed up on. Every category below the threshold is simultaneously a market the automated version can't serve and an opening for a specialized vertical verifier.
Highest-priority open question; still unanswered.If it standardizes, the play is to be the registry — the DNS of agents, extremely valuable and rare. If it balkanizes, the play is to be an identity aggregator — commoditized middleware translating between six issuer schemas. Lower margin, lower risk.
Priors recorded: 45% balkanized · 40% dominant-player quasi-standard · 15% real single standard within 12 months.Does reputation come from the facilitator that mediates transactions, or the runtime that deploys the agents? Does it transfer across agent types, or fragment by vertical? Fastest historical analogue is developer reputation consolidating on GitHub in about five years; the slowest is crypto credentials, still fragmented after eight.
Prior recorded: 3–5 years out. Too early to build as a primary thesis.