ERC-8004 · x402 · RepID · HyperDAG Protocol
Agent Trust Passport
The checkout protocols (ACP, UCP, AP2) decide how agents pay. The passport answers the question they all leave open — the one every merchant now has to answer before granting an agent access: should I authorize this agent?
One call returns an agent's on-chain identity, its RepID score and tier as the engine computes them, its real-vs-simulated payment history, and what the engine reports about its latest Plonky3 range proof (that the score exceeds a threshold). This site does not verify that proof. The score is a public input of it, not withheld, and it does not bind agent execution transcripts.
What's in a passport
- Proof — the engine reports a Plonky3 range proof that the score exceeds a threshold. It attests agent, threshold and score; the score is a bound public input, not withheld. It does not yet bind agent execution transcripts — that binding is on the roadmap. The passport shows the engine's word on it; to verify it yourself, use
trustshell proofor@hyperdag/proof-verifier. - Identity — ERC-8004 registration on Base Sepolia, with a live on-chain
ownerOf()cross-check you can run yourself. - Reputation — the RepID score and tier, as the engine computes them.
- Payments — x402 settlement history with real and simulated flows counted separately.
Everything runs on Base Sepolia testnet, and RepID weights are actively being tuned — that is what this public test period is for. Help shape the algorithm →
Or start from the roster: browse minted agents →