SpoolisDocs

Spoolis docs

Documentation

Spoolis provides the acceptance system between returned work and whatever acts next. You define what counts, provide the evidence, and choose the judge. Spoolis handles partial and uncertain results, earned value, retries and corrections, and returns a signed Outcome that other systems can use.

Spoolis Platform overview

Products built on it: Outcome Pricing, Outcome Guarantees, Outcome Acceptance, Outcome Spend.

Spoolis sits between judgment and action.

Your evaluator decides whether the work met the criteria. Spoolis turns that judgment into one durable acceptance result that billing, payment, a workflow, or another agent can act on.

Products

Start with the product that matches the result your workflow needs.

Outcome ReceiptsGive every downstream system one signed result it can verify offline.Read the documentation →Acceptance ReviewsKeep partial work and uncertain results from becoming an all-or-nothing argument.Read the documentation →Earned ValueTurn accepted units into an exact amount without asking a model to do the math.Read the documentation →Reviews and DisputesPut a named human in the acceptance loop and record every objection with its evidence.Read the documentation →Commercial stateExplain the current accepted commercial state and every unresolved difference.Read the documentation →Correction HistoryCorrect a result without erasing the record people already relied on.Read the documentation →Reconciliation StatementsGive finance a stable acceptance record and booking export for every receipt.Read the documentation →Promise ReplayReplay a vendor promise against historical results before adopting it.Read the documentation →Bring Your Own JudgeKeep the evaluator your workflow already trusts.Read the documentation →Agent PaymentsPut a verified result between an agent purchase and the next spend.Read the documentation →SandboxTest an acceptance flow before connecting production credentials or payment paths.Read the documentation →Outcome Definition RegistryCompare published outcome rules without hunting through vendor documentation.Read the documentation →Outcome Price BenchmarksCompare labeled outcome prices beside the rule and authority behind each one.Read the documentation →Evidence FabricConnect claims to observed facts while preserving where every fact came from.Read the documentation →

Start with one-call acceptance

Send criteria or explicit deterministic checks, evidence, and a maximum amount to POST /api/v1/verify. The sandbox twin is POST /api/sandbox/verify. Spoolis creates an inspectable unilateral Spool, verifies the result, and returns earned arithmetic plus a signed Outcome Receipt.

flow.txt
criteria + evidence -> unilateral Spool -> verify -> Outcome Receipt -> verifyReceipt -> optional status check -> consumer acts on earned

The external provider is identified but does not accept the criteria in Spoolis. Offline signature verification proves authenticity without Spoolis uptime.

When both parties agree in Spoolis

Use the bilateral lifecycle when both parties need to accept inside Spoolis: compile or create the Spool, accept it, submit evidence, run verification, and read the signed Outcome Receipt. The optional status check uses GET /api/v1/receipts/{receipt_id}/status.

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.

Markdown content negotiation

Every public page has a Markdown twin. Send Accept: text/markdown or request <path>.md.

Move from sandbox to production

Verification is self-serve: create a production API key at /dashboard/api-keys and call the same endpoints with it. Every account includes free monthly verification runs before any payment. Production enablement is only required for managed settlement: request it, then complete the wallet authority setup with your own principal account and credentials. It is an account status change, not a separate API integration.

Get started

QuickstartRun the zero-login sandbox, then continue to the canonical Outcome Receipt.Read sectionCoding-agent quickstartPaste one prompt into Claude Code or Codex to run the unitized sandbox example.Read sectionx402 seller recipeMake a batch delivery checkable and give buyers a signed Outcome Receipt.Read sectionOutcome-priced softwareTurn your definition of success into an accepted result. Keep your evaluator and billing stack.Read sectionAccept work between two partiesRun the bilateral agreement, acceptance, evidence, verification, and Outcome lifecycle.Read sectionContinue only with accepted workGate downstream actions on per-unit verified results.Read sectionAccept purchased workCheck a purchased result before a workflow continues, retries, or spends again.Read sectionAPI referenceCreate and read Spools, inspect events, and use lifecycle actions.Read sectionAuthenticationUse production API keys, scopes, and sandbox bearer tokens.Read sectionWebhooks and status pollingRead current status with polling endpoints and MCP tools.Read sectionAPI versioningRead the v1 compatibility and deprecation commitments.Read sectionMCP serverConnect to the hosted server or run stdio, then use the implemented Spool tools.Read sectionConnect SpoolisConnect Claude, ChatGPT, or another MCP client to the hosted Spoolis server.Read sectionHow verification worksFollow a criterion from evidence and verifier to result, earned value, and receipt.Read sectionJudge adapter mappingMap evaluators, CI, tests, and human review into the generic judge contract.Read sectionGlossaryDefine the acceptance terms used across Spoolis, its API, and Outcome Receipts.Read sectionWorkflow and billing consumersFeed verified Outcome exports into downstream systems without replacing them.Read sectionAcceptance lifecycleFollow claimed work through evidence, judgment, provisional acceptance, and final acceptance.Read sectionReviews and disputesRequest a human decision, submit counter-evidence, and resolve a disputed receipt.Read sectionDiscrepanciesRecord and resolve differences between expected and observed outcome figures.Read sectionOutcome Receipt specificationRead every field, method status, signature rule, and a unitized worked example.Read sectionVerify a receiptVerify an outcome receipt offline with the zero-dependency package and pinned trust material.Read sectionBring your own judgeKeep your CI, evaluator, or reviewer as the judge and standardize the result as a portable Outcome.Read sectionPayment pathsUnderstand path selection, refusal, payment layers, and configured adapters.Read sectionWallet authoritySet up a principal-owned wallet permission for production settlement.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.

Try your own Spool

Compile a sandbox Spool with no account, then verify it yourself.

Try your own Spool
Acceptance infrastructure documentation · Spoolis