Layer 1 (Core Protocols)

Layer 1 protocols Regent integrates (payments, identity, messaging, verifiable compute)

Layer 1 is the set of protocols Regent composes to make sovereign agents possible.

x402 (HTTP-native payments)

• Purpose: programmatic payments over HTTP (e.g. 402 Payment Required flows)

• Where Regent uses it:

  • regent-sdk x402 helpers

  • Facilitator verify/settle endpoints

• External references: coinbase/x402

ERC-8004 (identity, reputation, validation)

• Purpose: on-chain registries for agent identity + trust

• Where Regent uses it:

  • regent-sdk identity/discovery/reputation helpers

  • Facilitator agent registration + feedback auth

• Internal references:

  • regent-sdk ERC-8004 guide

  • Facilitator ERC-8004 docs

EigenCloud (EigenCompute + EigenAI)

• Purpose: verifiable compute + deterministic/verifiable inference

• How Regent references it (target):

  • verifiable task execution and/or inference attestations

  • part of Regent’s trust model for agents

• External references:

  • EigenCloud docs

  • EigenCompute overview

  • EigenAI overview

XMTP (messaging)

• Purpose: agent messaging + chat surfaces

• How Regent references it (target):

  • agent chat endpoints and/or discovery surfaces

• External references: XMTP docs

ENS (naming)

• Purpose: human-readable names (e.g. agent.base.eth)

• How Regent references it (target):

  • agent name resolution + discovery

• External references: ENS docs

OpenAI Evals (evaluation frameworks)

• Purpose: evaluation harnesses/benchmarks for agents

• How Regent references it (target):

  • standardized evaluations feeding validation/reputation flows

• External references: openai/evals