Machine index
Use this index to find the current Spoolis contracts, agent instructions, Markdown documentation, and receipt verification material.
Spoolis provides the acceptance system between returned work and whatever acts next. Define what counts, provide evidence, and use your own judge or Spoolis checks. Spoolis returns accepted, rejected, and uncertain results, earned value, reasons, and a signed Outcome.
Start with POST /api/v1/verify for one-call acceptance.
Start with the concise index or skill file, then use the contract for the interface you are building.
The developer platform for outcome-based software: define what counts, accept evidence, apply a chosen judge, run outcome verification through the outcome API or MCP server, and send the signed Outcome to downstream systems.
The canonical Spoolis dataset for public Outcome definitions, prices, authority, finality, correction rules, guarantees, and remedies, served as JSON at /api/outcome-index for agents.
Concise index led by the one-call verify front door, followed by public, API, receipt, and agent resources.
Generated Markdown dump led by the one-call homepage and quickstart twins, followed by every registered public page.
Coding-agent workflow that starts with the keyless POST /api/v1/verify/x402 door, POST /api/v1/verify, or verify_result, then documents the bilateral lifecycle.
OpenAPI 3.1 contract with POST /api/v1/verify first, plus production and sandbox lifecycle routes.
Setup and tool reference led by verify_result, followed by the 14 lifecycle tools.
Markdown twin of the Learn index; every article has its own Markdown twin at the article path plus .md.
Each link serves the registered Markdown twin of its HTML documentation page.
Markdown twin led by one-call acceptance via POST /api/v1/verify, with the bilateral flow second.
Markdown twin of POST /api/sandbox/verify, offline receipt verification, and the bilateral sandbox lifecycle.
Markdown twin of the paste-in prompt that calls the unitized one-call sandbox endpoint and verifies its receipt.
Markdown twin for sellers who want buyers to check a unitized x402 delivery and receive a signed Outcome Receipt.
Markdown twin led by POST /api/v1/verify, followed by implemented lifecycle routes, authentication, and limits.
Markdown twin led by verify_result input and output, followed by the 14 lifecycle tools.
Markdown twin for connecting Claude, ChatGPT, or another remote MCP client to Spoolis.
Markdown twin of payment-path selection, refusal, and settlement boundaries.
Markdown twin of production wallet setup, bounded authority, expiry, and revocation.
Markdown twin of the criterion, evidence, verifier, result, and receipt model.
Markdown twin mapping external evaluators and review systems into the generic judge adapter contract.
Markdown twin for consuming accepted, retry, hold, continuation, and settlement exports.
Markdown twin of the field-by-field Outcome Receipt contract.
Markdown twin for named human decisions, counter-evidence, timeouts, and dispute finality.
Markdown twin for commercial-state discrepancies and their resolution.
Markdown twin for source contracts, immutable capsules, facts, jobs, and provenance.
Markdown twin for deterministic matching and fact resolution.
Markdown twin for deterministic historical replay under candidate vendor terms.
Markdown twin for grounded policy proposal and caller confirmation.
Markdown twin for comparing mapped invoice and record inputs.
Markdown twin of offline Outcome Receipt verification.
Markdown twin for verifying delegated agent work before a manager acts on it.
Use the schema to validate the receipt shape, then verify signatures against receipt entries your application trusts.
JSON Schema for the spoolis/outcome-receipt@1 receipt format.
Environment-separated public attestation keys and Outcome Receipt trust entries.
Receipt verifier package. requireOutcome() consumer policy checks ship in 0.1.3 and later.
Python receipt verifier (3.10+). Same verification contract, reason codes, and golden vectors as the npm package.
Runnable examples: LangGraph, smolagents, two-consumer, x402 buyer, twin receipt verifiers, plus the verify-before-action skill and Cursor rule.