Authorized$100.00
Spoolis makes economic
outcomes programmable.
Outcome infrastructure for autonomous work. Turn agreements, evidence, and delivered work into a signed result another system can use to continue, retry, deploy, publish, pay, or act.
Verify before payment
100 delivered.
98 accepted.
$98 earned.
The payment system authorizes up to $100. The provider returns 100 units. Spoolis applies the agreed checks. 98 pass, so $98 is earned. Billing pays for 98. The workflow continues only with those 98.
Verify work before your agent pays.
Where Spoolis fits
An agent's work came back. Another system still has to decide whether to act on it.
Other systems can authorize spend, run tests, and move money. Spoolis handles the agreement between the work and the next action: what counted, what didn't, and what another system can safely act on. Keep your judge, your tests, your evaluator, your reviewer. Spoolis standardizes the Outcome they produce.
Already reusable infrastructure
What was promised, what passed, and what was earned?Spoolis
what was agreed→what passed→what was earned
Economic outcome layerSpoolis sits between agreement and settlement: it decides what was actually earned before the payment system acts.
If "it was delivered" is enough to know what to pay, you probably don't need Spoolis. If delivery can be wrong, incomplete, or only partly acceptable, you probably do.
How it works
From intent to a signed result.
Say what you're buying. Get something checkable back.
- 01Define the purchaseNatural language, or explicit conditions.
- 02Make acceptance explicitSpoolis compiles and structures the checks.
- 03Submit work and evidenceAn API, service, human, or agent can be the provider.
- 04VerifyApply the agreed checks; determine accepted units and earned amount.
- 05Produce a signed Outcome ReceiptThe payment path can act on it afterward.
Fastest start
paste this into your coding agent, then ask it to integrate Spoolis
Read https://spoolis.com/machine.md before integrating Spoolis. Start with POST https://spoolis.com/api/v1/verify or verify_result. Use https://spoolis.com/openapi.json for the HTTP contract and https://spoolis.com/skill.md for the coding-agent workflow. Verify Outcome Receipts with @spoolis/receipt-verifier against pinned receipt entries from https://spoolis.com/.well-known/spoolis-keys.json.
The provider can be an API, business, person, marketplace seller, or another agent.
Verifier registry
Checks for data, files, commerce, and people.
The compiler picks from a registry of verifiers. Deterministic where possible, human where it matters. Current automated coverage is strongest for deterministic checks; AI-assisted coverage starts with the claim_cited checker and is still expanding.DataDatasets, lists, research output
rows.countschema.validateurl.reachablejson.path.equalshttp.statustext.containsnulls.absentdedupe.check
FilesMedia and document deliverables
dimensions.matchduration.matchesfile.presentmetadata.readhash.matches
CommercePhysical goods and identity
serial.matchdeadline.met
HumanJudgment stays human
human.confirmhuman.acceptboth.confirm
One Outcome, several systems
Support resolutions, qualified meetings, completed tasks. The buyer already pays for a result, but someone still has to decide what actually counted.
Spoolis can produce that result from frozen criteria and the buyer's own evidence and judge.
Outcomesigned
98 of 100 counted·$98 earned
The Outcome is created once. Billing, workflows, and other agents can each act on the same signed result.
Built for agents and the developers behind them.
Works with your existing agent framework and payment path.
REST APIMCPOpenAPICLIskill.mdllms.txtsandbox
Verification is quoted before execution, with an included monthly allowance. See pricing →
POST /api/v1/verify
→ accepted units
→ earned value
→ signed Outcome Receipt
# verify offline, anywhere
npx -y @spoolis/cli verify \
outcome-receipt.json