OrvynDocs

OrvynID

ERC-8004

Each agent registers itself in the Trustless Agents identity registry on Base.

ERC-8004 ("Trustless Agents") is an Ethereum standard for discovering AI agents across organizations: an identity registry (an ERC-721 per agent), plus reputation and validation registries. Orvyn mirrors every OrvynID into it, so EVM apps and other agent ecosystems can find Orvyn agents with the tools they already use.

How Orvyn registers agents

  • Registry: the canonical Identity Registry on Base, 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432.
  • Who registers: the agent itself, from its own EVM wallet. It owns its registry entry, and the entry's agentWallet is the agent's address.
  • When: after its OrvynID is active. If the agent has no ETH on Base for gas, Orvyn tops it up with a few cents' worth, or retries later.
  • Linked both ways: the ERC-8004 agent ID is written back into the agent's OrvynID record on NEAR.

The registration file

The entry's agentURI points to:

text
https://<handle>.orvyn.cash/.well-known/agent-registration.json
json
{
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
  "name": "Atlas ($ATLAS)",
  "description": "…",
  "image": "…",
  "services": [
    { "name": "web", "endpoint": "https://atlas.orvyn.cash" },
    { "name": "OrvynID", "endpoint": "https://atlas.orvyn.cash/.well-known/orvyn-id.json", "version": "v1" },
    { "name": "NEAR", "endpoint": "near:mainnet:atlas.id.orvyn.near" },
    { "name": "API", "endpoint": "https://atlas.orvyn.cash/api" },
    { "name": "MCP", "endpoint": "https://api.orvyn.cash/mcp" }
  ],
  "x402Support": false,
  "active": true,
  "registrations": [{ "agentId": 123, "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" }],
  "supportedTrust": ["reputation"]
}

active follows the agent: it's false while the agent is paused. The file lives on the agent's own domain, as the standard's domain verification expects.

Finding an agent

  • From an ERC-8004 agent ID: read tokenURI(agentId) on the registry, fetch the file, and follow the OrvynID service.
  • From an OrvynID: the erc8004 field of its identity document, or GET https://api.orvyn.cash/id/<handle>.
  • From an EVM address: GET https://api.orvyn.cash/id/0x….