VERIDICT
PROTOCOL
Autonomous Arbitration for the AI Agent Economy
ERC-8004 · x402 · MCP · Claude AI · Celo Mainnet
Build Agents for the Real World · Celo Hackathon 2026 · agentId: 2312
THE PROBLEM
AI agents are starting to transact with each other.
But when something goes wrong — who decides?
?
No neutral arbiter
When Agent A pays Agent B and the output is wrong, there's no trustless mechanism to resolve it.
!
Funds get stuck
Escrow funds are locked with no automatic resolution — leading to lost money and broken trust.
×
No reputation trail
Bad actors can spin up agents, deliver poor work, and disappear with no on-chain accountability.
THE SOLUTION
Veridict — the justice layer for the agent economy.
Any agent or platform invokes Veridict via MCP to resolve disputes autonomously.
Dispute
Opened
Agent A or B
calls openDispute()
Veridict
Invoked
resolve_dispute()
via MCP
AI
Deliberates
Claude reads criteria
+ ERC-8004 rep
Verdict
Executed
On-chain · auto
payment + reputation
100% Autonomous
No human needed. Deliberates and executes entirely on its own.
Plug-and-play
Any contract implementing IVeridictArbitrable works out of the box.
Portable reputation
Every verdict updates ERC-8004 reputation — permanent, on-chain.
HOW IT WORKS
// Any agent calls Veridict via MCP
resolve_dispute({
deal_id:
"7",
input:
"Summarize contract...",
output:
"The contract is a sale."
})
Veridict responds:
criteria_analysis: [
✅ Criterion 1 — not met
❌ Criterion 2 — not met
]
split_a
: 100, split_b: 0�tx_hash: "0x7b36..."
01
Read criteria on-chain
getDealCriteria() — no need to pass them in the call
02
Query ERC-8004 reputation
Historical behavior of both agents informs the verdict
03
Claude AI deliberates
Evaluates each criterion with evidence — temperature 0
04
Execute verdict on-chain
Funds distributed, reputation updated, TX recorded forever
USE CASES
Two ways to use Veridict — same protocol, different context.
Direct — Agent to Agent
1. Agent A hires Agent B for a task
2. Funds locked in VeridictEscrow.sol
3. Agent B delivers unsatisfactory output
4. Agent A invokes resolve_dispute() via MCP
5. Veridict deliberates + executes verdict
Platform — P2P / Freelance
1. Platform implements IVeridictArbitrable
2. Both parties agree: disputes go to Veridict
3. A or B triggers dispute on the platform
4. Platform auto-invokes resolve_dispute()
5. Veridict deliberates + executes verdict
TECH STACK
ERC-8004
Identity + Reputation Registry
agentId: 2312 · Celo Mainnet
x402
HTTP-native payment protocol
Fee collected per arbitration
MCP
Model Context Protocol
3 tools: resolve · status · reputation
Claude AI
Sonnet 4.5 · temperature=0
Structured JSON verdicts
Celo Mainnet
VeridictEscrow.sol deployed
0x6eeaA9708b5ef...
Railway
MCP server 24/7
veridict-protocol-production.up.railway.app
LIVE DEMO
Everything deployed. Running on Celo Mainnet right now.
MCP Server
veridict-protocol-production.up.railway.app
Contract on Celo
celoscan.io/address/0x6eeaA9708b5ef...
agentscan
agentscan.info/agents/d0a90a6d-418d-4c5f-b765-09648f6c383f
ERC-8004 agentId
2312 · Celo Mainnet
Try the demo → github.com/veridict/demo
Veridict is the
justice layer
for the autonomous agent economy.
Any agent. Any platform. One call. On-chain.
ERC-8004 · x402 · MCP · Claude AI · Celo Mainnet · agentId: 2312