Our thesis
Agents are beginning to become economic actors.
See evidence: condition 1, are agents transactingPayment rails move money, but that alone does not establish whether the purchased work satisfied the agreement.
See evidence: condition 2, what agents buyAs agents buy more data, research, code, and completed outcomes, fulfillment becomes something that must be judged.
See evidence: condition 2, what agents buySome payment methods let buyers fix problems after payment; others are harder to reverse, which moves more of the decision about what counted and what was earned earlier in the transaction.
See evidence: condition 3, the market gapA fulfillment layer needs explicit acceptance criteria, evidence, verification, and an earned-value result.
See evidence: condition 3, the market gapThat result should be portable and independent of whichever wallet, marketplace, or payment rail moves the money.
See evidence: what it unlocksIf other systems consume verified outcomes, they can eventually inform payment, routing, reputation, pricing, and other economic systems.
See evidence: what it unlocksSpoolis is the bet that fulfillment verification becomes this missing layer.
See evidence: how large it could becomeSee how the verification layer works on a transaction.
See a Spool runEvidence
As agents move from buying simple API calls to buying data, research, code, and completed tasks, a payment status can no longer confirm the work was delivered to specification. Fulfillment verification becomes a distinct infrastructure layer. That is the Spoolis thesis.
Each condition reads strengthening, weakening, flat, or tracking. The thesis strengthens only when several conditions improve and none materially weakens. Evidence is sourced and dated, and may be revised. Methodology and evidence log
Last updated: . This is the newest stored observation or derived read available to the page.
Suggested citation: Spoolis, “The Spoolis thesis,” https://spoolis.com/thesis, snapshot 2026-09-30.
Strengthening. The latest available stored x402 transaction and volume signals increased by at least 5% on average.
Excludes dust bursts: facilitator-day rows averaging under $0.001 per transaction.
Source: Dune Analytics · as of Sep 11, 2026
HTTP 402 · coverage shown in stored provenance
Source: Dune Analytics · as of Sep 11, 2026
Built for high-frequency microtransactions.
Dashboard totals · network coverage not established
Source: MPPscan by Merit Systems · as of Sep 30, 2026
Built for higher-value utility purchases.
Sources use different coverage and should not be compared as complete protocol totals.
Machine commerce is measurable, but this page will not call its scale meaningful until the real series supports that conclusion.
If this activity does not become economically meaningful, nothing downstream matters.
Tracking. Tracking until measured purchasing or spend composition is available.
e.g. Exa · Brave · OpenRouter
Payment status confirms the call succeeded.
e.g. Apollo · Firecrawl · 2Captcha
Was it complete, valid, and accurate?
emerging · few named services yet
Did it meet the criteria, and what was earned?
Share of listed services in the catalog snapshot, not transactions or spend.
Source: x402 Bazaar discovery · as of Sep 30, 2026
Spend composition remains unmeasured. The transition is important enough to track and too important to invent.
Verification becomes valuable only when agents increasingly buy things whose fulfillment must be judged.
Tracking. Upstream infrastructure keeps shipping; outcome judgment still exists in pieces, and no broadly portable outcome layer has clearly emerged.
Spoolis is testing a reusable implementation of this outcome layer.
Upstream is becoming infrastructure
Authorization and execution are becoming infrastructure; none of it defines whether delivered work satisfied the agreement or what was earned.
Adjacent attempts exist
Pieces exist; what remains fragmented is portable agreement-to-outcome judgment another system can consume as earned value.
The problem is recognized independently
Payment rails are designed to settle payment, not to adjudicate fulfillment. Wallets sit on one side of the transaction, and marketplaces that can adjudicate do it inside their own walls. And verification is only possible against an agreement explicit enough to check, which most transactions never produce; that is why Spoolis compiles the agreement first.
The first mile is becoming infrastructure. The last mile remains fragmented across systems: what was promised, what happened, and what was earned.
If a rail, wallet, marketplace, or protocol takes ownership of the outcome question in a portable way, Spoolis risks becoming a feature. If none does, the outcome layer has to exist independently.
This is category and problem validation, not demand validation.
Tracking. Tracking because the visible calculator is illustrative and does not explain a directional market signal.
Illustrative · current introductory pricing
Verification: 100 deterministic checks
Cost: $0.020000
Verification can be economically negligible for some machine-native work, while more complex verification can support higher pricing.
If verification scales with transaction value, it becomes a tax on commerce. If it stays inexpensive relative to the work it enables, it can become infrastructure.
Unavailable or unexplained condition states remain tracking.
The evidence for the thesis strengthened this month.
2030 scenario forecast using external market anchors plus explicit Spoolis assumptions. Not company guidance.
Agent-mediated commerce grows materially; outcome verification becomes useful in a meaningful subset of result-shaped workflows.
Market anchor$400B agent-transacted US e-commerce in 2030 · Morgan Stanley base and the middle of Bain’s range, US 2030. Sources: Morgan Stanley, Bain.
Spoolis assumptions
Smaller outcomes mean verification is cheap enough for smaller work, so the same activity produces more outcome decisions.McKinsey estimates up to $1T of US commerce could be agent-orchestrated by 2030 under a broader definition. McKinsey. Kept outside the three cases because it is a broader definition.
Company scenario
Charge for determining the outcome. Today: usage-based adoption pricing. Later: predictable complexity classes.
Mature per-outcome pricing is a scenario input, not observed.Platforms pay to make outcome verification part of their stack.
Committed usage · platform controls · enterprise contracts.One verified outcome can inform future decisions.
Routing · limits · procurement · accelerated settlement.Potential pricing: per decision or read; permissioned; facts only.The wedge is verification. The venture-scale outcome depends on platform adoption and verified outcomes becoming reusable economic infrastructure.
Scheduled ingestion gathers observations from the primary sources listed below and stores each series with its source, observation time, and available provenance. The observatory derives only the explainable condition states described on the page. “Last updated” means the newest stored source observation or derived read rendered in this snapshot, not the time a reader opened the page.
A verified outcome can become useful far beyond the transaction that created it. If software can reliably know what was promised, what actually happened, and what was earned, other systems can act on that result.
Potential consumers
Portable primitive · illustrative receipt · as of Aug. 14, 2026
Could enable
The wedge is fulfillment verification. The larger opportunity is making economic outcomes programmable.
If outcomes become structured, signed, portable, and widely consumed, they could become inputs to reputation, routing, pricing, marketplaces, and other economic systems. Once software can determine what work was actually worth, financial products could attach to the outcome instead of merely the transaction. That is speculation, not something the data shows yet.L1 Availability. Did it respond. A commodity signal anyone can observe.
L2 Criterion satisfaction. Did the delivered work satisfy the agreed criteria under the recorded verification method. This is what the signed receipt captures today. Read how the fulfillment layer works.
L3 Downstream economic success. Did the work create the value the buyer hoped for. Today this is implicit human judgment. Whether it becomes a recorded, portable signal is an open question we track, never something we can extract.