zeroclick. / futures
Act II · institutional lens A · 2027Q3 → 2029Q2

Coordinated open rails

Rails can bridge buyer instruments. A wallet or card token can resolve the same 402 through an interoperable router; chat runtimes rarely block a third-party rail and platform take stays near card interchange. By 2029Q2 24% of agent attempts succeed, agents carry 22% of online GMV — inside Bain's 2030 band a year early — and a third of buyers hold a wallet. The binding constraint flips from the buyer's instrument to seller reach.

Act I · 2026 → 2027The buyer delegatesSoftware moves from ranking choices to receiving bounded authority.
Act II · 2027 → 2029 · institutions decide who can transact
Lens AOpen railsauthority becomes portableLens BFragmented webtranslation becomes the taxLens CWalled gardensdelegation becomes captive
Acts III–V · 2029 → 2040Commerce becomes persistentSeller agents, policies and physical execution turn purchases into an operating system.
The shared story, through this institution

Delegation becomes portable.

The buyer still states the same intent and grants the same bounded authority. What changes is that identity, payment and receipts can cross runtimes, so agents compete on judgment instead of captivity.

One constant: the selected everyday mobility need and its human boundary. One variable: who can interpret that authority and where recourse lives.

2029 handoff · the buyer can act

Checkout works. Agency becomes the next contest.

By 2029 the buyer-side instrument is no longer the main constraint. The story can move to seller agents, negotiated capacity and policies that remain valid across providers.

Coordinated open rails · delegated commercesoftware owns 6/8 steps
Purchasing experience · plays as it enters the story

The seller side becomes software too

illustrative emerging mechanism · coordinated open rails · not the default 2029 purchase · illustrative, not a forecast

your policyintentbuyer agentcommercial handoffportable agent exchangecommercial handoffCycleWorks agentcommercial handoffcommute readyoutcome
policytendernegotiationsettlementfulfillment
agent.local/mandates/activeverified
2029 handoff · selected need preserved

The bounded purchase becomes a negotiable mandate.

Outcome

Find a dependable commuter e-bike under $2,200, delivered this month, with theft coverage and local service.

Ceiling$2,200 delivered
Required termslocal service · theft coverage
Boundaryask before changing model or coverage
Authorityportable mandate proof

The person can move the mandate and recourse to another agent. The human boundary is not a negotiable term.

Open a bounded tender
Scene 1 of 5 · Carry the mandate forward
discoverdecidetransactresolve
After the purchase · 2029Q2 · Coordinated open rails

The first forecast ends. The mechanism contest begins.

The near-term engine’s settled agent GMV becomes the initial delegated-demand pool. The structural layer then separates demand an agent can influence from the smaller share it can execute under authority, seller coverage and governance.

Surfaceapproval bundle
Authoritysingle-use mandate; approve this purchase
What this unlocks nextFrom this boundary, six mechanisms can compound differently through 2032, 2036 and 2040; none is treated as the inevitable successor to checkout.
Open economics, physical boundary, machine cast and six mechanism precursors512 structural/economic sensitivity draws · 2029 handoff is branch-conditioned · flows overlap where noted
Financial state
agent influenced$332B–$380B
agent executed$121B–$187B
merchant-routed$107B–$168B
base execution conversion49%
Physical-world boundaryThe bike arrives at a neighborhood shop already paired with the fitting appointment, coverage and portable receipt. Control returns at The person inspects the evidence and authorizes this one commitment; the agent cannot substitute the model after approval.where execution and recourse remain
Purchasing surfaceapproval bundlewhat the person encounters
Authority + controlsingle-use mandate; approve this purchasewhat software may commit
Machine cast in this purchase3 modeled role classes active: Buyer agent, Mandate agent, Settlement agent; human remains operatorrole activation threshold 8% · not agent population
Six future mechanisms, seen from this chaptermodel-derived activation support · not adoption probability
Embedded34% support · Assistants learn to carry merchant state
Mandates58% support · One-use authority becomes legible
Open network47% support · Adapters translate fragmented commerce
Metered11% support · Agents buy small pieces of digital work
Trust market43% support · Agents inherit platform reputation
Object initiated17% support · Products expose a persistent identity
How this institution forms · 2027Q3 → 2029Q2
2027Q3

Interop holds

The major chat runtimes keep third-party rails enabled. A card token and a wallet resolve the same 402 challenge through an interoperable router, so an agent tries whichever the buyer has and falls through to the next. Success reaches 11% and 47% of sellers answer at least one rail.811

2027Q4

Plugins, not projects

The big storefront platforms ship native 402 endpoints as an update, and x402 and MPP begin clearing orders at mid-market merchants that never wrote a line of payment code. Agents route around page-only sellers, suggesting a checkout-capable equivalent mid-task — a nudge merchants feel as lost orders.37

2028Q1

One in ten

Success passes 14% and agent GMV share reaches 3.5%. With compatible rails on more checkout-capable sites, agents compare total cost across rails in parallel; merchants offering more than one see the higher modeled conversion. Onboarding flows pre-link an instrument when a person installs an assistant.7

2028Q2

Seller capability compounds

Page-only sellers now serve 42% of modeled demand, down from 60% at the start, while 56% answer a rail. Cross-border orders become easier to represent because the 402 handshake can carry currency and tax terms, and x402 and MPP each hold just over a fifth of settled volume.37

2028Q3

A majority of sellers

Nearly six in ten sellers expose a rail. Replenishment and subscription purchases — detergent, groceries, renewals — make up an outsized share of agent GMV, because low-stakes, high-frequency orders tolerate the remaining friction. 'No rail' moves beside 'no instrument' as the market's next binding failure.7

2028Q4

Agents negotiate

Agent GMV share passes 10%. Some sellers answer 402 with terms, not just a price — bulk discounts, slower shipping for a lower total — and a few publish agent-only bundles to see whether algorithmic buyers shift demand. This is where the scenario begins turning checkout into negotiation.11

2029Q1

The constraint flips

'No rail' overtakes 'no instrument' as the top failure. Buyers are ready; the long tail of sellers is not. Agents fail over card → x402 → MPP routinely and learn which merchants settle fastest; people stop setting a default payment method and let the agent pick per order.79

2029Q2

Nearly one dollar in five

Agents carry 22% of online GMV with a 24% success rate, and 34% of buyers hold a wallet. The rail mix is five-way — x402 22%, MPP 21%, UCP 20%, card tokens 18% and platform checkout 17%. Interoperability, not standardisation, is what won; agents compete on routing, not exclusivity.678

Continue this institution into the 2040 story →

Open this lens’s model dossier, actors and charts
Narrative dossier · derived before prose

Why this future moves

The market develops coordination capacity that bridges instruments, lowers seller integration effort and exposes failed demand. The writer receives this cross-quarter spine, all actor arcs, counterfactual outcomes and open questions before drafting any scene.

2026Q4the market state moves fastest heresettlement +2.5% · agent GMV +0.2% · seller coverage +16.0%shared
2027Q1the market state moves fastest heresettlement +2.2% · agent GMV +0.3% · seller coverage +10.2%shared
2027Q2the market state moves fastest heresettlement +2.0% · agent GMV +0.4% · seller coverage +6.6%shared
2029Q2the binding failure changes from noWallet to noRailsettlement +1.9% · agent GMV +6.4% · seller coverage +2.2%post-fork
What could break this scenario

What observed purchase-attempt series would justify replacing exogenous intent growth with an estimated adoption process? Would merchants actually respond to failed agent demand quickly enough to reach 65.0% rail coverage? Which runtime policy, distribution or regulatory events would change third-party rail access? How much cross-instrument reach and seller integration savings can ecosystem-wide coordination cause beyond open protocols alone, and which institutions could supply it? Which reproducible commercial-task evaluation series could anchor capability learning after 2029 instead of treating it as a structural prior? Which observed seller-side deployments could distinguish real pricing and inventory delegation from ordinary merchant automation? Which standards, statutes and dispute outcomes would demonstrate that authority, receipts and liability are becoming portable across runtimes? What comparable loss, dispute, collusion and manipulation datasets could anchor adversarial pressure as machine counterparties grow?

Actor model · decisions exposed by the engine

Who moves this future

Each lane is generated from the same quarterly state as the charts. The action is a deterministic interpretation of pressure in the model, not prose invented after the fact.

Shopperdelegates a purchase and decides which instruments an agent may usedelegates more repeat purchases as settlement becomes routine56% → 79%
Merchantpublishes inventory, integrates rails and absorbs fees or failed demandoptimizes price, terms and routing across supported rails46% → 65%
Buying agentdiscovers sellers, chooses a rail and retries when checkout failssearches for a seller exposing a compatible rail11% → 24%
Agent runtimedecides whether an agent can reach third-party payment railskeeps third-party payment challenges reachable95% → 95%
Payment networksissue credentials and settle card, wallet and protocol paymentscompete on interoperable reach and settlement reliability69% → 64%
Commerce platformbundles checkout for sellers and sets platform takebundles seller capability while competing on merchant economics2% → 2%
Coordination ecosystemstandards, networks, runtimes, platforms and independent routers that make instruments and seller rails work togetherconverges on shared routing, authorization and demand signals across providers75% → 75%

The numbers behind coordinated open rails

Share of agent purchase attempts that settle
0%13%25%38%50%forkCoordinated 24%Fragmented 22%Walled 17%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
Agent GMV retained by merchants after platform take
0%15%30%45%60%forkCoordinated 22%Fragmented 19%Walled 14%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
Agent share of online GMV
0%15%30%45%60%forkCoordinated 22%Fragmented 20%Walled 15%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
How settled purchases execute — coordinated open rails
merchant protocol 96%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
browser drives the pagemerchant protocol
Settled volume by rail — coordinated open rails
x402 22%MPP 21%UCP 20%card tokens 18%platform checkout 18%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
x402MPPUCPcard tokensplatform checkout
What buyers hold — coordinated open rails
wallet 35%card token 44%nothing linked 21%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
walletcard tokennothing linked
Why attempts fail — coordinated open rails
settled 24%no instrument 24%no rail 25%seller capability gap 19%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
settledno instrumentno railruntime blockedseller capability gapabandoned

By 2029Q2: 24% of attempts settle, agents carry 22% of online GMV and merchants retain 22% after platform take; 35% of buyers hold a wallet and 65% of sellers answer a rail. Top failure: no rail at 25%.78