What is a Spool?
The shared transaction object that holds terms, evidence, a verification plan, and lifecycle events.
Read the guideSpoolis learn
Verification, explained from first principles.
Think of Spoolis as the referee, not the bank: the referee decides what counted, the bank moves the money.
Start with the core idea
When to use Spoolis
Compare fit and verification responsibility across the full use-case matrix.
Read the guideFulfillment verification for agentic commerce
Why agents need an explicit way to decide whether purchased work met the agreement.
Read the guidePayments know when money moved. They don’t know whether it was earned.
A foundational essay: the history of the fulfillment gap, and why a general verification layer is finally possible.
Read the guideThe fulfillment layer between authorization and settlement
A foundational essay: the third question every payment system leaves unanswered, and why the layer that answers it should be independent of the rail.
Read the guideEvery payment system needs someone to decide what counted
An essay in analogies: market stalls, taxi meters, letters of credit, marketplaces, and CI, and whether the referee can become portable.
Read the guideThe agent economy: infrastructure, metrics, and market tracking
Spoolis research: what agents pay for today, how agent-native payments work, why verification is separating into its own layer, and where the institutional forecasts disagree.
Read the guideChoose the right verification model
LLM as judge vs verification
How one model judgment differs from an orchestrated, evidence-backed verification plan.
Read the guidePay per verified unit
How accepted units produce proportional earned value and explicit rejection reasons.
Read the guideWhen Spoolis decides and when you decide
How default policy and routing meet explicit adapter and capability choices.
Read the guideConnect verification to payment
Verification-gated settlement
How a passing verdict can authorize release through different payment rails.
Read the guideAuthorize the cap. Capture what was earned.
How a buyer’s payment stack can authorize $500, capture the $470 earned from a signed Outcome Receipt, and release $30.
Read the guideHow Spoolis routes a payment
How the payment referee selects a compatible configured path or refuses.
Read the guideA verified outcome in the loop
A worked LangGraph example where the graph gates its own payment step on a signed Outcome Receipt and uses verified earned value as the input.
Read the guideWorking with machine payment protocols: MPP and x402
What the in-development machine lanes support, and what they do not.
Read the guideUnderstanding settlement paths: Stripe, Tempo, and external settlement
How verification stays stable across different execution lifecycles.
Read the guideNext
See verification actually run
Watch a Spool compile, verify, and settle on what was earned.