Marketplaces
Add explicit acceptance criteria and a verification result when fulfillment is more specific than an order status.
Platform partner brief
Add verification to transactions your platform already runs.
For marketplaces, agent frameworks, data platforms, and tool platforms that need to define what counts as success, verify delivered work, and record what was earned.
No account or production key is required for the demo. Demo artifacts do not move funds or authorize production settlement.
Who it is for
Use Spoolis when your platform needs to know whether the work actually passed.
The platform keeps its existing relationship with buyers, providers, tools, identities, and payment infrastructure. Spoolis handles what counted as success and what was earned.
Agent frameworks
Give agents a structured path from transaction intent to evidence-backed outcome.
Data platforms
Evaluate records individually and tie earned value to accepted units when work is unitized.
Tool platforms
Add verification-gated transactions while keeping your existing identity, authority, and payment layers.
What Spoolis does
From intent to a portable Outcome Receipt.
The verification layer sits between transaction intent and any payment action your platform chooses to take.
- 01
Intent
Start with the task, terms, value, parties, and any conditions already agreed.
- 02
Compiled checks
Turn the intent into a canonical Spool with acceptance criteria and a verification plan.
- 03
Verify
Run the plan against submitted evidence and keep the condition-level result.
- 04
Per-unit earned value
For unitized work, resolve each unit and calculate earned value from the accepted count.
- 05
Outcome Receipt
When signing is configured, issue a portable signed record of the result and what was earned.
- 06
Optional settlement
Let a configured settlement adapter act on the result, or keep payment execution in your platform.
Integration surfaces
Choose the interface that matches your platform.
Every surface below is implemented and documented in this repository.
REST API and OpenAPI
Use the bearer-authenticated v1 Spool resource for production. Import the OpenAPI 3.1 document for routes, request shapes, examples, and errors.
MCP server
Run the repository stdio server in demo mode without an API key, or configure a production key to use the v1 routes.
Scoped machine keys
Owner grants mint a verify-scoped key. A Spool initiator can also issue a 15-minute, single-use grant invitation that a machine exchanges without a Clerk session for a counterparty key bound to that Spool.
Zero-login sandbox
Mint a short-lived sandbox session with no account, compile an intent, submit evidence, and verify. Sandbox artifacts cannot move production funds.
Receipt verifier
Verify an Outcome Receipt outside the Spoolis API with @spoolis/receipt-verifier and a pinned trust set. No Spoolis account is required.
Machine twins
Use the machine index to find Markdown twins, llms.txt, skill.md, the receipt schema, trust material, and the OpenAPI document.
What Spoolis does not do
Different layers, designed to work together.
Identity, authority, wallets, payment protocols, and settlement answer other questions in the transaction stack. Spoolis answers what counted as success and what was earned.
Identity and authority
Spoolis is not a general-purpose identity or agent-authority system. Keep using the system that decides who an actor is and what it may do.
Wallets
Spoolis does not replace the wallet or payment authority that controls funds and signs payment instructions.
Custody
Spoolis is not a bank, escrow agent, money transmitter, or payment processor, and it does not hold funds.
Payment protocols
Spoolis does not replace a payment protocol or rail that moves money. It produces the fulfillment result that another layer may use.
Evaluation path
Evaluate the full path without a sales call.
Start with demo-only verification, inspect the contracts, test receipt portability, then choose production credentials.
- 1
Run the zero-login sandbox
Use the curl quickstart or paste the coding-agent prompt. The resulting artifacts are sandbox-only.
Open the sandbox quickstart - 2
Map your transaction shape
Compare your parties, value, deliverable, conditions, evidence, and actions with the v1 contract.
Read the API reference - 3
Verify the receipt independently
Pin the appropriate receipt trust entries and test the verifier outside the Spoolis API.
Read the receipt guide - 4
Move to production credentials
Create a full-scope key, use an owner grant for verify scope, or use a Spool invitation for counterparty scope.
Open API keys
Have a platform requirement this brief does not answer? Contact Spoolis.