---
title: "Launch an ENS-native agent"
description: "Prepare identity records and optional ERC-8004 registration."
canonical: "https://ens.tools/docs/launch-agent"
section: "Agent platform"
stability: "experimental"
version: "launch workflow v1 · server 3.0"
verifiedAt: "2026-07-29"
owner: "ENS.Tools Agent Identity"
---

# Launch an ENS-native agent

Prepare identity records and optional ERC-8004 registration.

## Overview

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.

## What this covers

- 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.

## 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

## How to use it

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. **Choose a controlled ENS name.** Wait for the preflight to confirm ownership and wrapper path.
3. **Describe the agent.** Write public context, use a boundary-aware template when helpful, and add only HTTPS endpoints operated for this identity.
4. **Review before activation.** Confirm the controller, identity, endpoints, and registry choices together before preparing anything.
5. **Prepare phase one.** Write ENSIP-26 records and, if requested, mint the ERC-8004 identity using the bootstrap registration file.
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. **Complete the binding.** Update agentURI and publish the ENSIP-25 agent-registration record, then verify both directions.

## Do not guess an ERC-8004 agent ID

> The registry assigns agentId during mint. The final registration file and ENSIP-25 key must use the confirmed value.

## Related guides

- [Agent identity standards](https://ens.tools/docs/agent-identity-standards)
- [Agent directory and profiles](https://ens.tools/docs/agent-directory)
- [Safety, simulation, and signing](https://ens.tools/docs/safety-and-signing)