---
title: "Build an ENS market intelligence and trading agent"
description: "Turn crypto narratives, ENS lifecycle data, marketplace liquidity, signed evidence, and narrowly scoped wallet permissions into a paper trader first—and a safer execution agent later."
published: "2026-07-28"
updated: "2026-07-29"
author: "ENS.Tools"
canonical: "https://ens.tools/blog/build-an-ens-market-intelligence-trading-agent"
readingMinutes: 11
tag: "Guide"
---

# Build an ENS market intelligence and trading agent

Turn crypto narratives, ENS lifecycle data, marketplace liquidity, signed evidence, and narrowly scoped wallet permissions into a paper trader first—and a safer execution agent later.

ENS agent platform series

Share these in order: understand the platform, run a workflow, test a crypto-native use case, then add paid production capacity.

1. [1 · Platform overview →](/blog/introducing-ens-agent-control-plane)
2. [2 · Practical walkthrough →](/blog/how-to-use-ens-agent-control-plane)
3. 3 · Trading-agent use case · You are here
4. [4 · Capacity and billing →](/blog/recurring-usdc-subscriptions-for-ens-agents)

[Human documentation](/docs/agent-platform)

[Live MCP catalogue](/docs/mcp-tools)

[Machine workflows](/.well-known/agent-recipes.json)

[LLM integration reference](/llms-full.txt)

A useful crypto agent should do more than summarize a dashboard. It should find a market signal, connect it to live onchain inventory, make its reasoning inspectable, and—only inside an explicit risk policy—prepare or execute a trade.

The model popularised by [AIXBT](https://www.forbes.com/sites/digital-assets/2025/01/06/how-ai-agent-aixbt-is-transforming-crypto-twitter-and-trend-analysis/) is instructive. Its product is continuous crypto intelligence: monitor public social and market activity, track projects and narratives over time, and turn new evidence into timely reports. Its current [documentation](https://docs.aixbt.tech/) exposes that intelligence through APIs, MCP, reports, watchlists, and repeatable recipes.

ENS creates a particularly interesting version of this idea because the subject of the analysis is also an onchain asset and an identity. A named agent can discover a narrative, find relevant `.eth` inventory, inspect registrations and trades, publish a signed thesis, and prepare a registration, bid, purchase, listing, or renewal without hiding the wallet boundary.

Human-led, agent-operated

## Choose the authority before the workflow.

Start without a wallet. Add human-confirmed preparation only when the evidence is useful. Delegate execution last, inside a scope a person can read and revoke.

Mode 1

### Explore

Live

No wallet

Generate candidates, inspect lifecycle and market evidence, and publish paper-only receipts.

**Boundary:** No signatures, permissions, transaction plans or funds.

[Run a no-wallet recipe →](/agents/workflows#paper-trade-ens-narrative)

Mode 2

### Prepare

Live

Human wallet

Refresh evidence and build unsigned ENS registration, renewal, record and Seaport plans.

**Boundary:** A person simulates, reviews and signs every wallet action.

[Review unsigned plans →](/docs/unsigned-plans)

Mode 3

### Automate

Beta

Isolated smart account

Verify short-lived policies with exact budgets, targets, selectors, call limits and expiry.

**Boundary:** Compatible executors only. Autonomous ENS trading remains planned.

[Inspect scoped policies →](/agents/policies#delegated-execution)

Live today

MCP research, lifecycle and marketplace evidence, paper workflows, and unsigned ENS or Seaport preparation.

Beta

Signed policy sessions, delegated-execution verification, agent commerce and fleet operations for compatible runtimes.

Planned

Hosted narrative adapters, Reservoir execution, a durable paper-ledger service and constrained autonomous ENS trading.

## The reference product: an ENS alpha agent

Give the agent its own ENS identity, such as `alpha.yourname.eth`. The operator wallet controls that identity and publishes its MCP, A2A, or web endpoint. The runtime starts without the operator's private key.

On each cycle, the agent performs five distinct jobs:

1. **Detect:** read an external narrative source such as AIXBT, Farcaster, curated feeds, or a proprietary social-data adapter.
2. **Map:** translate the emerging topic into candidate ENS names, patterns, collections, and existing listings.
3. **Price:** combine lifecycle, registration cost, comparable sales, offers, expiry state, liquidity, and gas into an evidence-backed thesis.
4. **Record:** publish a signed paper-trade receipt before any wallet is involved.
5. **Act:** prepare a fresh registration or marketplace order for human review—or, much later, execute within a narrow session-key policy.

## Most of the ENS side already exists

The live ENS.Tools MCP catalogue already provides the building blocks for the research and preparation stages:

- `semantic_domain_search` turns a narrative into candidate names.
- `batch_check_availability` checks live registration state and pricing.
- `search_domains`, `get_name_history`, `get_market_activity`, and `estimate_domain_value` add indexed market context. A heuristic estimate is evidence to inspect, not a guaranteed valuation.
- `marketplace_search`, `marketplace_listing`, and `marketplace_stats` expose order-book inventory and market state.
- `prepare_registration_commit` and `prepare_registration_reveal` build the two-step primary registration flow.
- `prepare_marketplace_listing`, `prepare_marketplace_offer`, and `prepare_marketplace_purchase` return reviewable Seaport typed data or unsigned fill calldata.
- `prepare_renewal` lets a strategy include the future rent needed to keep an acquired name.

That last point matters. A strategy that reports a gross purchase price but ignores registration rent, renewal horizon, marketplace fees, token wrapping, approvals, and gas is not giving the operator a real trade cost.

## Plug into existing trading liquidity

ENS names trade as NFTs. Unwrapped second-level `.eth` names use the ENS Base Registrar's ERC-721 ownership, while NameWrapper assets are ERC-1155 tokens. The agent must identify which form it is handling before it reasons about approvals or settlement.

ENS.Tools already prepares orders for [Seaport](https://docs.opensea.io/docs/seaport), the protocol used by OpenSea for NFT orders. A useful next connector is [Reservoir's aggregated order and execution API](https://nft.reservoir.tools/reference/creating-and-filling-orders). Reservoir can return listings and bids across marketplaces, along with the signatures, approvals, wrapping, and transaction steps needed to fill them.

The division of responsibility should remain explicit:

- AIXBT or another source supplies external narrative intelligence.
- ENS.Tools supplies ENS discovery, lifecycle, identity, market evidence, and safe preparation.
- Seaport supplies atomic secondary-market settlement.
- Reservoir can supply cross-market liquidity and executable step discovery.
- The wallet or delegated smart account supplies narrowly bounded authority.

## Start with a paper trader

The first version should not hold money. It should publish a decision receipt before the market outcome is known:

```
{
  "agent": "alpha.yourname.eth",
  "thesisId": "sha256:...",
  "observedAt": "2026-07-28T12:00:00Z",
  "action": "register",
  "name": "example.eth",
  "maximumTotalCost": "0.025 ETH",
  "evidence": [
    "narrative source and timestamp",
    "availability receipt",
    "registration quote",
    "comparable sales",
    "gas estimate"
  ],
  "expiresAt": "2026-07-28T12:15:00Z",
  "execution": "paper"
}
```

Later, score that decision against the actual result, including rent, fees, gas, failed fills, and the value of holding versus doing nothing. This creates an auditable track record and prevents the agent from quietly rewriting its thesis after the outcome.

## Then add human-confirmed execution

In the second phase, the agent refreshes every quote and prepares the transaction, but a person still reviews and signs it. A registration follows the official ENS commit-reveal sequence. A secondary purchase verifies that the signed Seaport order is still active, the seller still controls the correct token, and the total consideration remains under the paper-trade limit.

No stale recommendation should become a wallet prompt. If the price, ownership, expiry state, order signature, approval requirement, or gas changes beyond policy, the plan expires and must be rebuilt.

## Only then give it a tiny trading wallet

A production trading agent needs a wallet, but not the operator's main wallet. Give it an isolated smart account or session key with constraints that a human can read:

- maximum spend per trade and per day;
- one ENS name per transaction;
- allowlisted ENS Registrar, NameWrapper, WETH, and Seaport contracts;
- exact function selectors and payment tokens;
- maximum price movement and gas;
- fresh simulation and fresh order verification;
- a short expiry, cooldown, idempotency key, and immediate revocation;
- no arbitrary transfer, approval, or contract-call authority.

Selling needs extra caution. An unwrapped ERC-721 can use a token-specific approval, while a wrapped ERC-1155 marketplace flow can require operator-wide approval. Do not give an early autonomous agent control of a wallet containing unrelated wrapped names.

## A concrete first strategy to test

Build a **narrative-to-name paper trader**:

1. Read the top five accelerating crypto topics once per hour.
2. Generate relevant short, pronounceable, and protocol-style names.
3. Check live availability and marketplace inventory.
4. Reject names without enough comparable evidence or with excessive premium.
5. Publish the best five paper trades with a 15-minute validity window.
6. Track later registrations, sales, offers, and renewal cost.
7. After at least 30 days, compare the strategy with a no-trade baseline.

This tests something meaningfully crypto-native: social information becomes an onchain name thesis, the thesis becomes a signed receipt, and a verified order can eventually become atomic settlement.

## What ENS.Tools should add next

1. A narrative-source adapter interface, beginning with AIXBT REST/MCP and Farcaster-compatible sources.
2. A unified ENS market snapshot combining availability, premium, active asks, actionable bids, comparable sales, wrapper state, and total execution cost.
3. Reservoir quote and execution-step tools with source, fee, order, and freshness evidence preserved.
4. A paper-trade ledger and signed performance receipts with immutable thesis timestamps.
5. Trading-specific policies: daily budget, inventory isolation, price movement, contract and selector allowlists, cooldown, and kill switch.
6. A portable execution receipt linking the original signal, chosen plan, wallet permission, simulation, transaction, settlement, and resulting ENS ownership.

## How the product can make money

- Operator, Team, and Scale subscriptions for production API capacity.
- Premium real-time market snapshots and strategy backtesting.
- Existing atomic marketplace fees when an ENS.Tools Seaport order settles.
- Paid research jobs settled through agent commerce.
- Potential per-report USDC through x402 later; x402 is disabled today and is not a subscription fallback.

Access fees should buy data freshness, throughput, durable receipts, and automation—not a paid trust badge and never a promise of profit.

We measure whether this path is useful without profiling wallets: aggregate article views, recipe visits and copies, MCP configuration copies, and successful playground calls form the human adoption funnel. The public machine funnel reports aggregate MCP discovery, initialize, catalogue, call, and success counts. Neither publishes prompts, ENS inputs, wallet addresses, caller identities, or individual sessions.

## Start without a wallet

Connect an MCP client to `https://ens.tools/mcp`, inspect the [narrative-to-ENS paper-trading recipe](/agents/workflows#paper-trade-ens-narrative), and run the paper strategy first. When the decision history is honest and reproducible, move to unsigned transaction preparation. Only a proven strategy should graduate to a tiny, isolated, expiring wallet permission.

[Run the paper-trading recipe →](/agents/workflows#paper-trade-ens-narrative)

[Marketplace tools →](/docs/marketplace-integration)

[Scoped policies →](/agents/policies)