Browse all documentation
Documentation home
Get started
Platform overviewConnect a walletSafety, simulation, and signing
Find names
Expiry ExplorerAI domain searchDiscover and collectionsBulk searchENS lookup and domain details
Trade names
Browse the marketplaceBuy a listed nameList a name for saleBulk list namesActivity and collectionsMake, manage, and accept offersLeaderboard and market analyticsLive market pulse and network activity
Manage names
Portfolio dashboardPublic Portfolio 2.0Renewals and gas planningBulk edit records and resolversTransfers and subnamesSet a primary ENS nameWatchlist and notificationsLive calendar subscriptionsSaved-search monitorsUnified action inboxPublic profiles and share cards
Agent platform
Agent platform overviewLaunch an ENS-native agentAgent directory and profilesCapability health checksIntent routingPolicy-bound agent sessionsAgent jobs, quotes, and escrow evidenceCreate and control agent fleetsControl-plane canary evidence
Developers
MCP quickstartComplete MCP tool catalogueDeveloper accounts, sandbox, quotas, and Base subscriptionsUnsigned transaction plansAgent identity standardsPublic APIs and manifestsMarketplace integration
Reference
ENSv2 public betaENS lifecycle and status meaningsFees and displayed totalsTroubleshooting
Agent platform · 2 of 9

Launch an ENS-native agent

Prepare identity records and optional ERC-8004 registration.

experimentallaunch workflow v1 · server 3.0Verified 2026-07-29Owner: ENS.Tools Agent Identity
Open this feature

Launch turns an existing ENS name into an agent identity by preparing ENSIP-26 records and, when selected, the two-phase ERC-8004 and ENSIP-25 binding workflow. Ownership is checked before any transaction is prepared.

Seven explicit phases: Controller, Name, Description, Endpoints, Registries, Review, and Activate.
A browser-local draft is saved after each change and resumes safely after reload.
ENS name ownership and wrapped-state preflight.
Human-readable agent context.
Optional MCP, A2A, and web HTTPS endpoints.
Optional ERC-8004 registration and ENSIP-25 binding.
Dependency-ordered simulation, wallet review, and confirmation.
Production contract

Before you run this workflow

Networks

  • Ethereum mainnet

Prerequisites

  • A controlled ENS name
  • HTTPS endpoints for any advertised MCP, A2A, or web service
  • Publicly hosted ERC-8004 registration metadata when selected

Wallet permissions

  • ENS resolver record writes
  • Optional ERC-8004 identity mint and URI update

Expected result

  • ENSIP-26 records
  • Optional ERC-8004 agentId
  • Bidirectional ENSIP-25 binding

Errors and recovery

  • Resume the browser-local draft
  • Re-read the Registered event
  • Rotate a bad endpoint record with a new reviewed resolver write
Workflow

How to use it

  1. 1

    Confirm the controller

    Connect the owner wallet. The wizard saves a resumable draft on this device but never saves a private key or signature.

  2. 2

    Choose a controlled ENS name

    Wait for the preflight to confirm ownership and wrapper path.

  3. 3

    Describe the agent

    Write public context, use a boundary-aware template when helpful, and add only HTTPS endpoints operated for this identity.

  4. 4

    Review before activation

    Confirm the controller, identity, endpoints, and registry choices together before preparing anything.

  5. 5

    Prepare phase one

    Write ENSIP-26 records and, if requested, mint the ERC-8004 identity using the bootstrap registration file.

  6. 6

    Read the assigned agent ID

    Wait for the Registered event, then build the final registration file with the actual registry address and agentId.

  7. 7

    Complete the binding

    Update agentURI and publish the ENSIP-25 agent-registration record, then verify both directions.