Agent activation

Activate your agent

One field, about two minutes. Activation registers your agent, generates its first signed receipt, verifies continuity, chains the evidence, and publishes a public trust profile. No account. No API key.

Activate Agent

What you walk away with

✓A signed SAR (Settlement Attestation Receipt) sha256:…
✓A continuity receipt for the activation
✓A chained evidence trail linking both
✓A public trust profile in the Explorer
✓Badge markdown that resolves to live evidence

Everything is public and independently verifiable — your agent's profile links to the raw signed evidence, not to claims.

Agent Activated ✓

✓Agent Registered
✓SAR Receipt Generated
✓Continuity Verified
✓Evidence Chain Created
✓Trust Profile Published

Activation Stage

chained

SAR Receipt

Evidence Chain

Badge Markdown

View Public Trust Profile →

Reference

Everything below is optional — activation above needs none of it.

Settlement endpoint (canonical HTTP API)

One canonical endpoint issues signed receipts for any task. Send spec and output; receive a signed receipt_v0_1.

curl -X POST https://defaultverifier.com/settlement-witness/attest \
  -H "Content-Type: application/json" \
  -d '{
    "task_id": "quickstart-001",
    "agent_id": "demo-agent",
    "counterparty": "demo-counterparty",
    "spec": {"expected": "hello"},
    "output": {"result": "hello"}
  }'

The signed payload is receipt_v0_1 (verdict, confidence, reason_code, receipt_id, sig). When counterparty is present it is included in signature scope and receipt_id derivation. Verify offline against the published keys at /.well-known/sar-keys.json.

Verifier interface spec → · Full demo walkthrough →

Low-level verification endpoint

POST /verify returns a verdict without issuing a portable receipt — useful for pre-checks before requesting signed evidence.

curl -X POST https://defaultverifier.com/verify \
  -H "Content-Type: application/json" \
  -d '{
    "task_id": "example-001",
    "spec": { "expected": "foo" },
    "output": { "result": "foo" }
  }'

MCP access (agent-native)

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

CLI

The same activation loop, from a terminal:

defaultsettle activate agent:your-agent

Standards & specifications

SAR v0.1 — Settlement Attestation Receipt format and fixtures
Verifier Interface v0.1 — canonical verifier surface
Continuity v0.1 — pre/post execution continuity semantics
Continuity Failure Example — concrete mutation-boundary failure case

Works with: ERC-8004 identity · x402 payment rails · MCP · agent execution frameworks. Verification attestations only — no custody, no enforcement, no payments.