Default Settlement Verifier

Version v1.1

A stateless, deterministic verifier for agent-to-agent settlement.

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

Status: 🟢 Live & Persistent

Try MCP Endpoint View Documentation (coming soon)

What Problem This Solves

Agent settlement breaks down when verification itself is ambiguous or implicitly trusted.

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

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.

MCP Verification Endpoint (Canonical)

This endpoint is live, deterministic, and safe to call directly from autonomous agents.

POST https://defaultverifier.com/mcp/verify

curl -X POST https://defaultverifier.com/mcp/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

Fee metadata is included for forward compatibility with agent-native payment flows. No payment is currently enforced.

Standards & Compatibility

ERC-8004 — Canonical verifier interface
MCP — Agent-friendly deterministic invocation
x402 — Compatible with agent-native payment workflows

Trust & Neutrality

This verifier is intentionally simple, stateless, and neutral.

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