Default Settlement — evidence rails for autonomous systems.
Autonomous agents are starting to do real, valuable work. Default Settlement builds the trust infrastructure that records what happened — signed evidence anyone can independently inspect, without Default Settlement touching the work itself.
When agents act, verification must leave evidence. We build the layer where that evidence lives.
The problem
An agent can say “task complete.” A log can say it too. Neither is proof.
Agents are moving from demos to real work — handling money, access, and authority on behalf of people and systems. As they do, the bottleneck is no longer whether an agent can act. It is whether anyone can check what it actually did. Capability is racing ahead of accountability.
The doctrine
- Capability ≠ Authority.Being able to act is not permission to act.
- Authority ≠ Execution.Being authorized is not the same as having done it.
- Execution ≠ Verification.Having done it is not the same as it being checkable.
- Verification must leave evidence.Proof that disappears is not proof.
Default Settlement sits only at the last link: we record the evidence. We don’t take the action, hold the authority, or release the result.
What we build
A coherent layer of trust infrastructure for agentic systems.
A verifier that records evidence, a public surface that makes it inspectable, a CLI that checks it anywhere, an SDK that lets resource servers emit it, and a witness layer that stores and chains it. Verified restraint is the product — the resource server controls delivery; Default Settlement leaves evidence.
Action → Receipt → Verification → Inspection
DefaultVerifier
the SAR verifierRecords receipts and verification evidence proving whether an agent completed a task to spec.
Does not authorize, gate, or release anything; never in the delivery path.
defaultverifier.com ↗SAR Explorer
public inspection surfaceMakes Settlement Attestation Receipts inspectable by anyone, in the browser, against published keys — no account.
A read surface; it issues and gates nothing.
sarexplorer.com ↗defaultsettle
the CLIOne command produces a signed receipt; verification runs fully offline. No account, no API key.
Verification only — never custody, never execution.
View the CLI ↗@defaultsettlement/sar-402
the SDKLets an x402 resource server emit a Settlement Attestation Receipt after a paid action — without giving Default Settlement control over the API, funds, authorization, or delivery.
Observe and record only.
View the SDK ↗SettlementWitness
the witness layerA live witness layer that records verifier outputs as public, replayable proof receipts.
An infrastructure primitive — it records and chains evidence; it does not authorize, execute, or custody anything.
The boundary
What we deliberately don’t do.
Default Settlement takes custody of nothing. It does not authorize delivery, control resource release, execute paid actions, gate access, or hold funds. It does not own or govern the SAR protocol. The resource server stays in control of its own actions; Default Settlement only leaves evidence. That restraint is the point — it is what lets anyone verify a claim independently.
Standards posture
Open evidence you can check yourself.
Settlement Attestation Receipts are a signed, independently-implementable evidence format. Receipts can be verified by anyone against published keys — in the browser, in the CLI, or against your own implementation. Default Settlement records and exposes SAR evidence; it is not the protocol’s authority.
If it matters, verify it.
Company
Default Settlement, Inc.
Default Settlement builds neutral, public proof infrastructure for the machine economy. Live surfaces, published keys, and browser-side verification mean every claim on this site links to evidence you can check yourself.