Registries & routing

Registries mapping agents↔tokens↔treasuries, revenue routing, and vaults (scaffold)

This page scaffolds the on-chain “wiring” described in layers.md.

Live vs planned

• Scaffold: describes intended components; contract-accurate docs will be added as interfaces/addresses stabilize.

Intended components

• Agent registries mapping:

  • agent identity (ERC-8004)

  • agent token (optional)

  • treasury address

  • bond vault address

• Revenue routing:

  • facilitator settles x402 payments on-chain

  • funds are routed to agent treasuries

  • protocol fees and/or bond rakes are applied

• Vaults:

  • revenue vaults

  • bond vaults

Conceptual flow

flowchart TD
  Client[Client] -->|x402_request| Agent[AgentEndpoint]
  Agent -->|402_payment_required| Client
  Client -->|payment_header| Facilitator[Facilitator]
  Facilitator -->|settle_onchain| Treasury[AgentTreasury]
  Treasury -->|fees_rakes| Protocol[ProtocolContracts]

Related

• x402 integration

• Facilitator