SettlementWitness

Version v1.2

Verifiable settlement layer for autonomous agents.

Designed for x402-compatible workflows • ERC-8004 aligned • MCP-compatible

Status: 🟢 Live & Persistent

Try Settlement Endpoint View Documentation

What Problem This Solves

Outputs don’t strictly match agreed specifications
Verification logic is opaque or stateful
Trust is assumed instead of explicitly verified

Given the same input, this verifier will always return the same result.

How It Works

Get Started in 30 Seconds

Send a request to /settlement-witness
Receive a signed settlement receipt (SAR)

A SAR is a signed, portable proof that a task was completed correctly — verifiable by anyone, offline, forever.

Verify receipt_v0_1 offline
Trigger payment only after PASS

No account. No API key. Deterministic and replayable.

An agent submits a task specification and output
The verifier evaluates deterministically
A signed verdict is returned (PASS / FAIL)
Settlement proceeds or halts based on that verdict

The verifier does not custody funds, maintain state, or make settlement decisions.

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

Insumer (pre-transaction) → x402 (payment) → SettlementWitness (delivery) → TrustScore (reputation)

SettlementWitness sits between execution and fund release, ensuring payments move only after verified delivery.

Live integrations — see insumer-examples

V1 Integrations

Shipped scope: compatibility positioning (text tiles). Logos can be added after permissions are confirmed.

Agent Execution Layer

OpenClaw

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

Agent Identity Standard

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

Machine Payment Infrastructure

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

Agent Wallet Infrastructure

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 (conceptual, architecturally aligned).

Enterprise Payment Infrastructure

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

Expanding Ecosystem Support

Coming soon (preview only):

Nanoclaw — Lightweight agent execution
Heurist Mesh — Facilitator coordination
.molt Domains — Agent identity + wallets
QuickNode x402 — RPC payment settlement
Agent escrow systems — Dispute resolution markets

Compliance note: SettlementWitness provides verification attestations only. It does not custody funds, enforce settlements, or coordinate payments.

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. counterparty is optional and not signed.

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
}

Fee-aware, currently zero-enforced

MCP Access

MCP Server: https://defaultverifier.com/mcp
Tool: settlement_witness
Arguments: task_id, spec, output
Returns: replay-stable receipt JSON (verbatim)

Standards & Compatibility

ERC-8004 — Canonical verifier interface
MCP — Compatible invocation semantics
x402 — Agent-native payment workflow compatibility

Trust & Neutrality

This verifier is intentionally simple, stateless, and neutral.

Can be used as a verification gate to prevent fraudulent or malicious agent settlements.

No hidden logic. No discretionary overrides. No privileged actors.