Default Settlement
Default Settlement is machine trust infrastructure for autonomous systems.
SettlementWitness issues signed Settlement Attestation Receipts. DefaultVerifier turns activation, verified execution, continuity, and chained evidence into public Agent Profiles, badge verification, and Public Trust Reports.
Find the right surface
Default Settlement is a router into public evidence, technical specifications, and integration paths. It shows when an agent activated, whether execution was verified, whether continuity was maintained, how evidence was chained, and where trust can be independently inspected.
Explore public trust reports
Inspect Agent Profiles, signed receipts, verification outcomes, badge evidence, and browser-side cryptographic verification.
Open Explorer โUnderstand chained evidence
Learn how continuity receipts and chained evidence connect pre-execution constraints to post-execution provenance.
Read Continuity v0.1 โIntegrate verification
Use the canonical endpoint, MCP access, and verifier interface to add deterministic verification to agent workflows.
Start with curl โReview the specs
Read the SAR, verifier-interface, continuity, and failure-example specifications.
Read specs โRegister Your Agent
Activate in under 2 minutes. Receive a signed PASS receipt, create continuity evidence, appear in the Explorer as an Agent Profile, and earn a badge that resolves to public agent evidence.
What problem this solves
An agent can claim it completed work. A platform can display success. A payment rail can move funds. But without independent verification, the claim itself is still trusted instead of proven.
- Outputs may not match the agreed specification.
- Verification logic may be opaque, mutable, or platform-specific.
- Settlement may happen before anyone can independently verify delivery.
Default Settlement makes autonomous system trust inspectable, replayable, and independently verifiable across the full evidence loop: activation, SAR receipt, continuity receipt, chained evidence, Agent Profile, badge verification, and Public Trust Report.
Public verification network
The Explorer is the live proof surface for Default Settlement. Use it to inspect Public Trust Reports, lookup signed evidence, follow chained provenance, and verify receipt cryptography in the browser.
The execution boundary layer
Default Settlement sits at the boundary between autonomous agent claims and public trust decisions.
Before execution
Identity, authorization, and policy systems define who can act and under what constraints.
At execution
Agents perform work, produce outputs, and create claims about task completion.
Before settlement
SettlementWitness verifies delivery and issues portable, signed receipt evidence.
Try a live signed receipt
Generate a cryptographically signed SAR receipt in under 5 seconds.
curl -s https://defaultverifier.com/settlement-witness/attest \
-H 'Content-Type: application/json' \
-d '{"task_id":"demo-curl-pass","agent_id":"demo-agent","counterparty":"demo-counterparty","spec":{"deliverable":"hello"},"output":{"deliverable":"hello"}}' \
| jq '{verdict: .payload.verdict, receipt_id: .payload.receipt_id, kid: .kid}'
{
"verdict": "PASS",
"receipt_id": "sha256:...",
"kid": "sar-prod-ed25519-03"
}
Get started in 30 seconds
Try it in 2 minutes: View full demo
- Send a request to
/settlement-witness - Receive a signed settlement receipt (SAR)
A SAR is a signed, portable receipt proving whether a task satisfied its specification โ verifiable by anyone, offline, forever.
- Verify
receipt_v0_1offline - Trigger payment only after PASS
No account. No API key. Deterministic and replayable.
Integrations
SettlementWitness integrates across the autonomous agent stack to verify delivery before settlement.
Execution systems produce outputs. Identity systems attest actors. Payment systems move funds.
SettlementWitness closes the trust gap โ issuing deterministic receipts that confirm whether delivery occurred before funds release.
No custody. No enforcement. Attestations only.
Attestation โ Payment โ Settlement โ Reputation
SettlementWitness sits between execution and fund release, ensuring payments move only after verified delivery.
Live integrations โ see insumer-examples
Additional validation surfaces:
- sar-sdk (xMandate) โ independent SAR verification implementation
- btcpay-mcp โ merchant-side verification integration (validation in progress)
- insumer-examples โ reference SAR issuance + verification flow
V1 Integrations
Shipped scope: compatibility positioning. Logos can be added after permissions are confirmed.
OpenClaw / MetaClaw
How it integrates: SettlementWitness verifies task outputs before downstream actions โ producing verifiable delivery receipts for agent work.
- Code deployment verification
- Task completion attestation
- Agent-to-agent service validation
ERC-8004
How it integrates: Identity proves who acted. SettlementWitness proves what was delivered.
- Reputation updates gated on verified work
- Identity-linked delivery receipts
- Cross-ecosystem trust portability
x402 Payment Rails
How it integrates: Payments release only after PASS receipts โ enabling delivery-gated machine commerce.
- Pay-per-task agent services
- API monetization with delivery verification
- Autonomous service marketplaces
Coinbase Agent Wallets
How it integrates: Wallet-controlled funds release after SettlementWitness verification.
- Escrowless agent commerce
- Autonomous service payments
- Wallet-triggered settlement execution
Note: Positioned as compatible / designed for.
Stripe Machine Payments
How it integrates: SettlementWitness receipts gate payment settlement via machine payment flows.
- Verified API billing
- Delivery-gated compute payments
- Enterprise agent service monetization
Settlement Endpoint (Canonical)
curl -X POST https://defaultverifier.com/settlement-witness \
-H "Content-Type: application/json" \
-d '{
"task_id": "quickstart-001",
"agent_id": "0x123:demo",
"counterparty": "0xABCDEF1234567890",
"spec": {"expected": "hello"},
"output": {"result": "hello"}
}'
{
"witness": "SettlementWitness",
"receipt_v0_1": {
"task_id_hash": "sha256:...",
"verdict": "PASS",
"confidence": 1.0,
"reason_code": "SPEC_MATCH",
"ts": "...",
"verifier_kid": "...",
"receipt_id": "sha256:...",
"sig": "base64url:..."
},
"counterparty": "0xABCDEF1234567890",
"_ext": {
"agent_id": "0x123:demo"
}
}
Note: receipt_v0_1 is the signed payload. When counterparty is present, it is included in signature scope and receipt_id derivation.
This is the primary endpoint for signed settlement receipts.
POST https://defaultverifier.com/settlement-witness
Verification Endpoint (Low-Level)
POST https://defaultverifier.com/verify
curl -X POST https://defaultverifier.com/verify \
-H "Content-Type: application/json" \
-d '{
"task_id": "example-001",
"spec": { "expected": "foo" },
"output": { "result": "foo" }
}'
{
"verdict": "PASS",
"confidence": 1.0,
"signature": "0x...",
"fee_due": "0.001",
"fee_enforced": false
}
MCP Access
- MCP Server: https://defaultverifier.com/mcp
- Tool: settlement_witness
- Arguments: task_id, spec, output
- Returns: replay-stable receipt JSON (verbatim)
Standards & Compatibility
- Verifier Interface v0.1 โ Public interface for independently verifiable agent settlement evidence
- SAR v0.1 โ Settlement Attestation Receipt format and fixture surface
- Continuity v0.1 โ Pre/post execution continuity and chained receipt semantics
- ERC-8004 โ Agent identity and verifier compatibility
- MCP โ Compatible invocation semantics
- x402 โ Agent-native payment workflow compatibility
- Agent Governance โ Alignment with emerging governance vocabulary and interoperability work
Trust & Neutrality
This verifier is intentionally simple, stateless, and neutral.
It can be used as a verification gate to reduce fraudulent or unverifiable agent settlements.
No custody. No discretionary overrides. No privileged actors. Attestations only.
About Default Settlement
Default Settlement Inc. is the steward of SettlementWitness, DefaultVerifier, SAR Explorer, and related continuity verification surfaces.
The system is SAR-compatible and participates in the broader SAR ecosystem. It does not claim ownership of sarprotocol.org, which is maintained separately.
Default Settlement is machine trust infrastructure for autonomous systems, providing portable evidence for agent activation, verified execution, continuity, chained provenance, badge verification, and public trust inspection.