# ENS Text Record Lookup

> ENS Text Record Lookup is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Reads a specified text record key from an ENS (Ethereum Name Service) name and returns its value

## Facts

- Endpoint: POST https://twin.unykorn.org/ens-text?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-text-record-lookup-f72ac24a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XCPqn7OCDG_foBU6Mmk_3

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ens-text-record-lookup-f72ac24a -d '<json body>'
```

Example prompt: What is the 'url' text record stored for vitalik.eth on ENS?

## When to prefer this

Use this endpoint when you need to fetch a specific text record (e.g. avatar, url, email, com.twitter) from an ENS name without running your own Ethereum node or ENS resolver. It is ideal for agents that need lightweight, pay-per-call ENS text resolution without managing Web3 infrastructure, and is particularly useful when enriching user profiles or verifying identity metadata attached to .eth names.

## Known failure modes

- ENS name does not exist or is not registered
- Requested text record key has no value set for the given ENS name
- Malformed ENS name or unsupported TLD causes resolution failure
- Network or RPC error reaching Ethereum mainnet
- Payment failure via x402 protocol results in 402 response before lookup is attempted

## How this service works

Read a text record from an ENS name — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, the type 'ens-text', the resolved text record value for the given ENS name and key, plus a receipt containing a transaction hash, USD amount charged, and a unique receipt ID with an ISO 8601 timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "key": {
     "type": "string"
    },
    "name": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "ens-text",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.25,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-text-record-lookup-f72ac24a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)