zeroclick. / futures
Footnotes

Every claim, and where it came from

  1. Agent purchases settled on withzero rails since 2026-05-19: 39,044 calls, $714.05, 171 distinct paying wallets, 23 capabilities active in the week of 2026-08-17.BigQuery `withzero.withzero_analytics.capability_invocations` (one row per HTTP request), queried 2026-08-21. Metered routes record no amount, and proof-intent identity routes record zero-amount settlements that are excluded here, so the dollar figure is a floor and the call count a ceiling.
  2. ORA's live agent-readiness index reported 14,616 sites scanned, an average score of 34/100 and 2% graded B or above on 2026-08-24; payment support was the weakest published layer at 6% average fill.ORA Research, `How ready is the web for agents?`, https://ora.ai/research, and scoring methodology, https://ora.ai/methodology, retrieved 2026-08-25. ORA is an external, continuously updated index; its measurements provide public context and do not seed, calibrate or validate this simulation.
  3. x402 is the volume leader among agent payment rails: roughly 165M payments from ~69k agents by April 2026.agenticplug.ai protocol tracker (secondary), April 2026; the x402 Foundation under the Linux Foundation listed 40 members in July 2026. Primary Coinbase figures were not independently verified for this page.
  4. Merchant-facing protocols are still evolving rather than converging on one checkout. Google launched UCP in January 2026 across APIs, A2A and MCP. In March 2026 OpenAI shifted ACP toward product discovery and merchant-owned checkout after saying its initial Instant Checkout lacked the flexibility it wanted.Google Developers Blog, `Under the Hood: Universal Commerce Protocol`, https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/, published 2026-01-11; OpenAI, `Powering Product Discovery in ChatGPT`, https://openai.com/index/powering-product-discovery-in-chatgpt/, published 2026-03-24; retrieved 2026-08-26. These announcements establish available mechanisms, not adoption rates.
  5. All major US card networks now ship agent payment tokens: Mastercard Agent Pay (announced 2025-04-29, live) and Visa Intelligent Commerce (Agent Score, Agentic Registry at Visa Payments Forum 2026); Google AP2 launched September 2025 with 60+ partners.aimmediahouse.com, eco.com, agenticplug.ai, retrieved 2026-08-21.
  6. Forecasts for agent-driven commerce diverge mostly by definition: Bain $300–500B US by 2030 (15–25% of e-commerce); Morgan Stanley 10–20% of US e-commerce; Gartner 20% of digital commerce via AI platforms; McKinsey $3–5T globally.Bain 2030 snap chart (Dec 2025), Digital Commerce 360 on McKinsey (2025-10-20), Stellagent integrated analysis; retrieved 2026-08-21.
  7. Every curve on this page comes from a deterministic mean-field simulation: purchase intents → execution surface → instrument-to-rail match → outcome, stepped quarterly, with seller adoption and buyer instrument migration as share movements. Visual browser control, site-scoped WebMCP tools and remote merchant protocols are modeled separately. Interoperability has an explicit cross-rail conversion rate, and platform take is reported as merchant-retained GMV. No LLM computes a value; uncertainty bands come from 4,096 seeded Latin-hypercube runs that cover every assumed range densely and evenly.`capabilities/futures/sim/engine.ts`, `sim/ledger.ts`, `sim/sweep.ts` and `sim/sensitivity.ts`. `npm run sim -- run --branch open` reproduces the open-rails series; `npm run sim:sweep` reproduces the bands.
  8. The three scenarios share every parameter except ten lever values: rail interoperability, the chance a chat runtime blocks third-party rails, platform take rate, relative integration cost for five rails, relative WebMCP implementation cost, and which rail the agent-native incumbents push after the fork.`npm run sim -- check` prints the differing keys and `non-lever diffs: 0`.
  9. The near-term simulation starts from disclosed scenario priors rather than a readiness score. Before a run is accepted, four accounting checks require seller-capability, buyer-instrument and runtime shares to conserve to one and first-quarter outcomes to close.`npm run sim -- run --branch open` prints the model-internal start-state checks. `sim/validate.ts` defines them; they validate accounting, not empirical fit.
  10. An LLM was tried as the seller-adoption decision model and rejected: at temperature 0 it returned the same x402 adoption probability (0.72) for every lost-sales level from 0% to 95%, and pushed wallet-holding buyers to 79–87% in both tested scenarios regardless of the levers.Spike run 2026-08-21, claude-haiku-4.5 via openrouter, 20-step monotonicity sweep; total spend under $0.50. The LLM now drafts prose only.
  11. A 402 Payment Required response can be a machine-payment handshake: the server returns payment instructions, the client constructs a signed payment payload and retries the request with proof. This settles access to a resource; product discovery, authority, checkout semantics, fulfillment and recourse require other layers.Coinbase Developer Platform, `Welcome to x402` and `Client / Server Flow`, https://docs.cdp.coinbase.com/x402/welcome and https://docs.cdp.coinbase.com/x402/core-concepts/client-server, retrieved 2026-08-26; MPP, https://mpp.dev.
  12. ZeroClick publishes this scenario and has a commercial interest in open agent commerce. ZeroClick itself is not a modeled actor: no scenario assumes that its current products persist, supply the coordination layer or win future market share.Disclosure. The simulation models market capabilities and actor classes, not company valuation or product-market fit.
  13. The chapter architecture adapts AI 2027's scenario method: repeatedly ask what happens next, and begin each chapter with a compact state of the world. Here that method is applied to commerce institutions and purchasing interfaces rather than general AI capability.AI 2027, scenario and methodology, https://ai-2027.com/ and https://ai-2027.com/scenario.pdf, retrieved 2026-08-24.
  14. Delegation is better treated as a curve than a ladder: the useful degree of agent autonomy varies with category, stakes and reversibility, and higher-authority actions require bounded, auditable and reversible controls.McKinsey, `The automation curve in agentic commerce`, https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-automation-curve-in-agentic-commerce, retrieved 2026-08-24.
  15. Agentic product search can shift scarce human effort from inspecting products toward articulating preferences; platform capability may therefore advance faster than consumer delegation, creating an adoption lag.Dong, Luo and Xu, `From Product Search to Preference Articulation: The Economics of Agentic Search`, arXiv:2608.08395, https://arxiv.org/abs/2608.08395, August 2026.
  16. The four commerce-arena profiles are counterfactual lenses, not empirical category estimates. Their repeatability, reversibility, consequence and preference-articulation values alter purchasing-interface thresholds, autonomy and exception risk without changing the aggregate market path.Disclosed unanchored scenario priors in `capabilities/futures/sim/horizon.ts`; each selected arena prints its values and evidence status in HTML and Markdown.
  17. Each structural chapter exposes the model transition that precedes it. The 2029 trace shows the explicit near-term-to-structural mapping; later traces report exact percentage-point changes between simulated states. These traces describe the equations, not observed real-world causal attribution.`buildHorizonTransitionTrace` in `capabilities/futures/sim/horizon.ts`; HTML and Markdown render the returned run values without recomputing or rewriting them.
  18. Each structural chapter opens with a deterministic authored institutional event selected from the actual branch, year and published model thresholds. The page exposes the exact selection rule and a trigger sentence with run values; the title, interpretation and consequence are scenario narration, not measurements or forecasts. The 512 range-covering structural draws also report how often every threshold-defined alternate event is selected; those shares diagnose rule sensitivity and are not event probabilities.`buildHorizonChapterEvent` and `simulateLongHorizonEnsemble` in `capabilities/futures/sim/horizon.ts`; the selected event and full event coverage are carried into HTML, Markdown and the narrator dossier with the evidence status `model-triggered authored event`.
  19. Long-horizon ribbons are conditional sensitivity bands, not probabilities or confidence intervals. For each branch, 512 paired seeded Latin-hypercube draws cover all nine disclosed unanchored structural ranges while holding the published 2029 branch handoff fixed; the page reports p10, p50 and p90 of the resulting model outputs. The same draws report the complete share distribution across all four purchase surfaces by arena and epoch; that coverage is a robustness and sensitivity diagnostic, not a probability. A published preset can sit outside its ribbon because the coverage design spans every range stratum rather than centering on that preset.`simulateLongHorizonEnsemble` in `capabilities/futures/sim/horizon.ts`, using the deterministic sampling primitives in `capabilities/futures/sim/sampling.ts`; generated bands and full surface distributions are rendered directly in the `/2040` frontier, companion, chapters, chart and Markdown.
  20. Physical agents are becoming a technically distinct frontier rather than an extension of browser automation: current embodied-reasoning systems can plan multi-step physical tasks, coordinate multiple robots and detect task completion. This is evidence for possible building blocks, not evidence of commercial diffusion or a 2040 adoption rate.Google DeepMind, `Gemini Robotics ER 2`, https://deepmind.google/models/gemini-robotics/embodied-reasoning/ and model card https://deepmind.google/models/model-cards/gemini-robotics-er-2/, retrieved 2026-08-24. The model card restricts safety-critical production uses; the simulation's physical-execution values remain unanchored priors.
  21. Current agent-payment specifications already distinguish human-present approval from human-not-present autonomous mandates, but delegation from one shopping agent to another remains explicitly outside the current AP2 specification. The gap between a secure purchase mandate and a durable economy of delegated agents is therefore still open.Google Agent Payments Protocol v0.2 specification, https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md, retrieved 2026-08-24.
  22. Emerging agent registries separate agent identity, reputation and task validation, suggesting that future machine counterparties may need trust infrastructure independent of a seller site. These are proposed standards, not measured adoption.ERC-8004 `Trustless Agents`, https://eips.ethereum.org/EIPS/eip-8004, retrieved 2026-08-24.
  23. The present Universal Commerce Protocol covers discovery profiles, checkout and asynchronous order lifecycle updates. Pooled demand, commissioned production and physical multi-operator outcomes go beyond that transaction-centered surface and are modeled here only as disclosed structural possibilities.Universal Commerce Protocol specification overview and roadmap, https://ucp.dev/2026-01-11/specification/overview/ and https://ucp.dev/documentation/roadmap/, retrieved 2026-08-24.
  24. Visa's 2025 surveys of 3,700 monthly online shoppers across the United States, Australia and New Zealand found stated willingness to substitute an AI shopping assistant across the buyer journey: 73% for discovery, 69% for evaluation, 62% for cart and checkout and 64% for post-purchase tasks; 85% said control over agent-accessible data was important.Visa, `Earning consumer trust in the age of agentic commerce`, https://corporate.visa.com/en/products/intelligent-commerce/earning-trust-report.html, retrieved 2026-08-25. These are survey responses to illustrated use cases, not observed transaction rates.
  25. PayPal's 2026 Agentic Commerce Pulse Report surveyed 498 U.S. merchants across small-business, mid-market and large-enterprise segments about preparation for AI-influenced shopping.PayPal, `What merchants really think about agentic commerce`, https://www.paypal.com/us/brc/article/agentic-commerce-pulse-report-findings, published 2026-04-27 and retrieved 2026-08-25. Merchant expectations are directional survey evidence, not measured adoption.
  26. The economic layer starts from $340.2 billion of seasonally adjusted U.S. retail e-commerce sales in Q2 2026, annualized to $1.3608 trillion. Census reported that quarterly e-commerce represented 17.1% of total U.S. retail sales. Only this baseline is observed; every later dollar value is a conditional scenario estimate.U.S. Census Bureau, `Quarterly Retail E-Commerce Sales`, https://www.census.gov/retail/ecommerce.html, released 2026-08-18 and retrieved 2026-08-25. The published figure is adjusted for seasonal variation but not price changes.
  27. McKinsey estimated that U.S. B2C retail could see $900 billion to $1 trillion of revenue orchestrated by agentic commerce in 2030, and $3 trillion to $5 trillion globally. The estimate covers goods, not services or B2B, and is shown only as an external comparison; it does not seed, calibrate or validate the simulation.McKinsey, `The agentic commerce opportunity: How AI agents are ushering in a new era for consumers and merchants`, https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants, published 2025-10-17 and retrieved 2026-08-25.
  28. A computer-using agent can operate existing web interfaces by looking at pages and using mouse-and-keyboard actions, including filling forms and ordering goods. Browser execution broadens merchant reach without requiring an API, but it inherits the brittleness and safety boundaries of human-facing pages.OpenAI, `Introducing Operator`, https://openai.com/index/introducing-operator/, published 2025-01-23 and updated 2025-07-17 when browser operation moved into ChatGPT agent; retrieved 2026-08-26. Product availability is evidence of a mechanism, not a commerce-adoption measurement.
  29. Trusted-agent recognition can apply to both merchant websites and APIs. Visa's specification uses signed, purpose-bound HTTP messages so a merchant can distinguish an approved commerce agent from an unknown bot and request consumer or payment information appropriate to the interaction.Visa Developer Center, `Trusted Agent Protocol` overview and merchant specification, https://developer.visa.com/capabilities/trusted-agent-protocol/overview and https://developer.visa.com/capabilities/trusted-agent-protocol/trusted-agent-protocol-specifications/, retrieved 2026-08-26. Visa labels parts of the product as in development; the simulation does not treat this as measured adoption.
  30. WebMCP defines a browser API through which a website can register structured tools for an agent to invoke in the context of that page. It can make an existing merchant surface more reliable than visual clicking while preserving the website as the origin, but it does not itself supply payment, portable authority or recourse.W3C Web Machine Learning Community Group, `WebMCP API`, Draft Community Group Report, https://webmachinelearning.github.io/webmcp/, 2026-08-26; Chrome for Developers, `WebMCP: Tools for web agents`, https://developer.chrome.com/docs/ai/agents, retrieved 2026-08-27. This anchors the mechanism only; the simulation's merchant coverage and adoption values remain disclosed priors.
  31. Anthropic's Commerce Agents blueprint makes a merchant-native agent architecture concrete: one shopper agent carries shared context across search, planning, cart, checkout and customer care; a separate merchant agent monitors analytics, catalog, inventory, pricing and campaigns; typed presentation tools render commerce UI; durable memory lives in merchant systems; and consequential consumer or merchant writes are staged behind code-enforced approval gates.Anthropic, `Building commerce agents with Claude`, https://claude.com/blog/claude-for-commerce-agents, and `A guide to the anatomy of effective commerce agents`, https://claude.com/blog/the-anatomy-of-effective-commerce-agents, published 2026-09-02; reference implementation https://github.com/anthropics/commerce-agents; retrieved 2026-09-03. Anthropic reports that some enterprise customers saw carts up to 35% larger and shoppers 60% more likely to complete a purchase, but does not disclose sample construction or a causal evaluation here. Those figures are vendor evidence only and do not seed, calibrate or validate this simulation.
Parameter ledger · 2 anchored, 72 assumed

Anchored values cite a measurement. Assumed values are our best guess with the range the uncertainty sweep samples. Lever rows are the only parameters that differ between scenarios.

parametervaluetagrangesource / note
baseIntents1,000,000assumed500000 – 2000000purchase intents routed through agents in 2026Q3, normalised unit
totalIntentsMultiple20assumed12 – 40total e-commerce intents as a multiple of agent-routed intents in 2026Q3; sets the GMV-share denominator
intentGrowthPerQ0.3assumed0.2 – 0.4quarterly growth of agent-routed intents (≈3.3× a year); the horizon check compares 2029Q2 GMV share with Bain 15–25% of US e-commerce by 2030
preForkTakeRate0.03assumed0.01 – 0.08platform share of gross agent GMV before the 2027Q3 fork; used only to report merchant-retained GMV
buyerPayment.none0.62assumed0.5 – 0.75buyers whose agent has no usable payment instrument
buyerPayment.card0.33assumed0.2 – 0.45buyers with a card agent token
buyerPayment.wallet0.05anchored—x402 ~69k agents vs ~165M txns, Apr 2026 (secondary tracker) · agents holding a crypto wallet are a small minority today
buyerRuntime.chatApp0.7assumed0.55 – 0.8share of agent purchases initiated from a chat product
buyerRuntime.browserAgent0.2assumed0.1 – 0.3share initiated by a browsing agent
buyerRuntime.apiAgent0.1assumed0.05 – 0.2share initiated by a headless API agent
sellerCapability.00.6assumed0.35 – 0.75share of commerce demand served by page-only sellers with no reliable machine checkout; scenario prior, not inferred from a readiness score
sellerCapability.10.25assumed0.15 – 0.4share served by sellers with machine-readable discovery but no dependable agent checkout
sellerCapability.20.12assumed0.05 – 0.25share served by sellers exposing a programmatic checkout surface
sellerCapability.30.03assumed0.01 – 0.1share served by agent-native sellers that can expose terms and settle directly
browserExecutionCoverage0.55assumed0.3 – 0.8share of card-enabled browsing-agent attempts that can reach a usable page flow; mechanism prior, not an observed adoption rate
sellerWebMcp.00.005assumed0 – 0.03share of page-only seller demand exposing useful site-scoped browser tools in 2026Q3
sellerWebMcp.10.04assumed0.01 – 0.12share of machine-readable seller demand also exposing useful site-scoped browser tools in 2026Q3
sellerWebMcp.20.12assumed0.04 – 0.25share of checkout-capable seller demand also exposing useful site-scoped browser tools in 2026Q3
sellerWebMcp.30.2assumed0.08 – 0.4share of agent-native seller demand also exposing useful site-scoped browser tools in 2026Q3
webMcpSuccess0.9assumed0.75 – 0.97completion reliability after a browser agent invokes a valid site-scoped commerce tool
webMcpAdoptBase0.008assumed0.002 – 0.02quarterly WebMCP adoption propensity without visible lost demand
webMcpAdoptLostSalesGain0.06assumed0.02 – 0.15extra WebMCP adoption propensity per unit of lost agent demand
webMcpAdoptPeerGain0.04assumed0.01 – 0.12extra WebMCP adoption propensity per unit of peer adoption
webMcpAdoptCostPenalty0.025assumed0.01 – 0.06WebMCP adoption propensity lost per unit of relative implementation cost above 1
sellerCapabilityConversion.00.15assumed0.05 – 0.3chance a browsing agent completes a purchase with a page-only seller once it reaches the flow
sellerCapabilityConversion.10.45assumed0.25 – 0.65chance of completion when discovery is machine-readable but page checkout is not dependable
sellerCapabilityConversion.20.8assumed0.6 – 0.95chance of completion when a programmatic checkout surface exists
sellerCapabilityConversion.31assumed0.9 – 1relative completion ceiling for an agent-native seller
railSuccess.x4020.92assumed0.85 – 0.97settlement success once a compatible rail is found
railSuccess.MPP0.9assumed0.85 – 0.97settlement success once a compatible rail is found
railSuccess.UCP0.85assumed0.75 – 0.95settlement success once a compatible rail is found
railSuccess.cardAgentToken0.8assumed0.7 – 0.9card tokens add issuer-side approval friction
railSuccess.platformCheckout0.88assumed0.8 – 0.95in-platform checkout, single vendor
interopBridgeSuccess0.75assumed0.5 – 0.95chance an interoperable router converts between a buyer instrument and a non-native seller rail after that rail is found
abandonRate0.08assumed0.04 – 0.15attempts abandoned after a compatible rail and checkout exist
adoptBase0.03assumed0.01 – 0.06quarterly rail-adoption propensity of a seller with no lost sales
adoptLostSalesGain0.35assumed0.2 – 0.6extra adoption propensity per unit of lost agent sales
adoptPeerGain0.15assumed0.05 – 0.3extra adoption propensity per unit of peer adoption
adoptCostPenalty0.04assumed0.02 – 0.08adoption propensity lost per unit of relative rail cost above 1
sellerCapabilityDiffusion0.06assumed0.02 – 0.14quarterly share of seller demand that moves up one capability level in response to lost sales
migrateToCardBase0.03assumed0.01 – 0.06quarterly share of no-instrument buyers that add a card token regardless of experience
migrateToCardGain0.2assumed0.1 – 0.4extra migration per unit of experienced success rate
migrateToWalletBase0.01assumed0.005 – 0.03quarterly share of buyers that add a wallet regardless of experience
migrateToWalletGain0.15assumed0.05 – 0.3extra wallet migration per unit of experienced success rate
open lever.railInterop1anchored—x402 Foundation (40 members, Jul 2026) and MPP share the 402 handshake; UCP published as an open spec Jan 2026 · rails accept each other
open lever.gatekeepProb0.05assumed0 – 0.15chance a chat runtime blocks a third-party rail
open lever.takeRate0.02assumed0.01 – 0.04platform take on an agent purchase
open lever.railCost.x4021assumed1 – 2relative integration cost
open lever.railCost.MPP1assumed1 – 2relative integration cost
open lever.railCost.UCP2assumed1 – 3relative integration cost
open lever.railCost.cardAgentToken2assumed1 – 3relative integration cost
open lever.railCost.platformCheckout3assumed2 – 3relative integration cost
open lever.webMcpCost1assumed1 – 1.8relative cost of exposing site-scoped browser tools
open lever.incumbentRail0assumed0 – 00 = x402 seeded at agent-native sellers
organic lever.railInterop0.45assumed0.2 – 0.7open specifications exist, but no ubiquitous router bridges every buyer instrument to every seller rail
organic lever.gatekeepProb0.15assumed0.05 – 0.3most runtimes permit third-party rails, with inconsistent policy and technical support
organic lever.takeRate0.04assumed0.02 – 0.08competition keeps take below a closed platform, but fragmentation adds intermediary cost
organic lever.railCost.x4021.8assumed1 – 2.5relative integration cost without a shared seller-facing coordination layer
organic lever.railCost.MPP1.8assumed1 – 2.5relative integration cost without a shared seller-facing coordination layer
organic lever.railCost.UCP1.5assumed1 – 2.5relative integration cost where commerce platforms bundle partial support
organic lever.railCost.cardAgentToken1.5assumed1 – 2.5relative integration cost where processors bundle partial support
organic lever.railCost.platformCheckout2assumed1.5 – 3platform checkout is convenient but not universally preferred
organic lever.webMcpCost1.5assumed1 – 2.4relative cost when browser-tool conventions and merchant implementations remain uneven
organic lever.incumbentRail2assumed2 – 22 = UCP seeded at checkout-capable sellers
walled lever.railInterop0assumed0 – 0platform tokens are exclusive; cross-rail attempts fail
walled lever.gatekeepProb0.45assumed0.3 – 0.6chance a chat runtime blocks a third-party rail
walled lever.takeRate0.12assumed0.08 – 0.2platform take on an agent purchase
walled lever.railCost.x4023assumed2 – 3relative integration cost
walled lever.railCost.MPP3assumed2 – 3relative integration cost
walled lever.railCost.UCP2assumed1 – 3relative integration cost
walled lever.railCost.cardAgentToken1assumed1 – 2relative integration cost
walled lever.railCost.platformCheckout1assumed1 – 2relative integration cost
walled lever.webMcpCost2.4assumed1.6 – 3relative cost when dominant runtimes privilege proprietary merchant integrations
walled lever.incumbentRail4assumed4 – 44 = platformCheckout seeded at agent-native sellers