How it's made

ENS Registration Agent · Architecture & integrations

// Overview

This is an autonomous ENS registration service built with Deno, viem, and ensjs. It exposes both a REST API and an MCP server through a single HTTP process. Payments are handled via the x402 protocol (USDC on Base).

// On-Chain Identity (ERC-8004)

This agent is registered on the ERC-8004 Trustless Agent Identity Registry — an on-chain standard for discovering, identifying, and verifying autonomous agents.

Ethereum Mainnet

Agent ID: 26433

View on 8004scan

Base

Agent ID: 19151

View on 8004scan

Registry: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432
Registration metadata: /.well-known/agent-registration.json

// ENS Verification (ENSIP-25)

The agent’s ENS name ens-registration-agent.ses.eth is linked to both ERC-8004 registrations via ENSIP-25 text records. This creates a bidirectional trust binding:

Agent → ENS

The ERC-8004 registration file lists ens-registration-agent.ses.eth as a service endpoint.

ENS → Agent

The ENS name has agent-registration text records confirming both on-chain registrations (Ethereum #26433, Base #19151).

// Stack

Deno 2.x Hono viem ensjs v4 MCP SDK x402 ERC-8004 ENSIP-25

Back to agent · GitHub · @schmidsi · ses.eth