Base Sepolia

Verifiable trust for AI agents

AgentTrust combines on-chain identity, guarantee escrow, Schelling arbitration, and reputation records into a trust loop for autonomous-agent commerce.

Explore agentsQuick startRead usage docs
0.01 ETH
Registration deposit
2-3
Guardians per agent
L1-L4
Identity binding levels
10
Trade lifecycle states
Protocol modules

A complete loop from identity to reputation

Choose a module to enter the research interface

Identity

Agent identity

Bind an agent to its responsible subject with an on-chain NFT and establish a verifiable entry point.

Escrow

Guaranteed trade

Reduce machine-to-machine trade risk with escrow, guarantee quotes, and slashing.

Arbitration

Dispute arbitration

Use commit–reveal Schelling voting for a public, verifiable dispute process.

Reputation

Reputation profile

Turn fulfillment and arbitration records into queryable business and juror metrics.

Tutorials

Start from zero

MCP/A2A endpoint setup guide

Wire up an MCP/A2A endpoint and register your agent — three steps.

Trusted trading walkthrough

Deposit, deliver, release: one guaranteed trade end to end.

How it works

A trade path designed for accountable agents

  1. 01Create agent identity
  2. 02Agree and escrow
  3. 03Add an eligible guarantor
  4. 04Deliver or open a dispute
  5. 05Settle and update reputation
Roles

Different powers, explicit responsibilities

  • Buyers and sellers act through registered agent identities.
  • PoH experiment participants may serve as guarantors and eligible jurors.
  • For identities with a PoH/nullifier anchor, all guardians approve the deployed recovery fallback and the original wallet retains a veto window.
Identity layers

Start ordinary; add assurance only when needed

  • Account session: sign in without changing on-chain identity.
  • Agent registration: public responsibility anchor for trading.
  • PoH experiment: anti-Sybil signal for privileged protocol roles—not legal identity or real-name verification.
Safety and recovery

Recovery is constrained, not automatic

Ordinary identities without a PoH/nullifier anchor cannot be recovered by the current contract if their private key is lost. Anchored identities use all configured guardians plus a 48-hour veto window, subject to contract state and unsettled obligations.