# ENS Text Record Resolver

> ENS Text Record Resolver is a paid API for AI agents from x402.professorsausages.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Fetches arbitrary ENS text records for a given ENS name

## Facts

- Endpoint: GET https://x402.professorsausages.com/ens-resolve/text/:name
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-text-record-resolver-a09f916e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_939Mgrq14FepPmBdVWcW1

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-resolver-a09f916e
```

Example prompt: Can you look up the ENS text records for vitalik.eth — specifically the avatar and url fields?

## When to prefer this

Use this endpoint when you need to retrieve specific ENS text record fields (avatar, url, email, com.twitter, description, keywords, notice, etc.) for a known ENS name. Prefer this over the sibling reverse-resolver endpoint when you already have the ENS name and want its metadata rather than resolving an Ethereum address to a name.

## Known failure modes

- ENS name does not exist or is unregistered — returns not found error
- Requested text record key has no value set — returns empty or null
- ENS resolver contract unreachable due to RPC issues — returns service error
- Malformed ENS name (e.g. missing .eth suffix) — returns invalid input error
- Name exists but has no text records at all — returns empty result

## How this service works

Arbitrary ENS text records for a name

## Output

Returns the value of an arbitrary ENS text record for the given ENS name, such as social handles, website URLs, avatars, email addresses, or any custom key stored on-chain or via ENS off-chain resolvers.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-text-record-resolver-a09f916e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.professorsausages.com](https://www.zero.xyz/host/x402.professorsausages.com/llms.txt)
