Spoolis docs

Documentation

Name: Spoolis
Brand: Spoolis

Spoolis compiles transaction intent, verifies delivered work, and issues a signed Outcome Receipt that records what was earned. The receipt is the public, portable artifact for independent verification.

View as Markdown

Spoolis is the referee for the payment rail.

It decides what passed and what was earned. Your wallet, marketplace, or payment system moves the money.

The canonical receipt flow

A buyer pays for 100 enrichment records at $1.00 per accepted record. Spoolis verifies the delivery, accepts 98 records, rejects 2 with reasons, and signs an Outcome Receipt for $98.00 earned. Verify the receipt offline, optionally check its status, then let the payment stack act on the earned amount under its own policy.

flow.txt

1. Compile
2. Verify
3. Read the signed Outcome Receipt
4. verifyReceipt offline
5. Optionally GET /api/receipts/{id}/status
6. Act on earned

Offline signature verification remains sufficient.

The portable artifact

An Outcome Receipt uses schema spoolis/outcome-receipt@1. A third party can verify it with @spoolis/receipt-verifier and pinned receipt keys from the public trust set. The signed attestation remains the lower-level in-band verdict that the receipt builds on. Receipt validity does not authorize or settle a payment.

Payment integration boundary

Spoolis determines earned value and signs the Outcome Receipt. A wallet, marketplace, payment system, or configured integration may verify and consume it, then act under its own authorization and settlement policy.

Get started

QuickstartRun the zero-login sandbox, then continue to the canonical Outcome Receipt.Read section Coding-agent quickstartPaste one prompt into Claude Code or Codex to run the unitized sandbox example.Read section API referenceCreate and read Spools, inspect events, and use lifecycle actions.Read section MCP serverConnect the stdio server and use the implemented Spool tools.Read section How verification worksFollow a criterion from evidence and verifier to result, earned value, and receipt.Read section Outcome Receipt specificationRead every field, method status, signature rule, and a unitized worked example.Read section Verify a receiptVerify an outcome receipt offline with the zero-dependency package and pinned trust material.Read section Payment pathsUnderstand path selection, refusal, payment layers, and configured adapters.Read section

Agent resources

Use llms.txt for the concise index, llms-full.txt for the complete public-page dump, and skill.md for the agent workflow. Every registered public content page has a Markdown twin at <path>.md, including these docs pages.