# Tanod chainpeek ENS Resolution

> Tanod chainpeek ENS Resolution is a paid API for AI agents from tanod.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-11).

Forward-resolves an ENS name to an Ethereum address, or reverse-resolves an Ethereum address to its ENS name (with forward verification), on Ethereum mainnet.

## Facts

- Endpoint: POST https://tanod.dev/v1/chain/ens?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanod-chainpeek-ens-resolution-0849f6be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_STvL4U9_4mtNVUloLU9B1

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 tanod-chainpeek-ens-resolution-0849f6be -d '<json body>'
```

Example prompt: What Ethereum address does vitalik.eth resolve to? Also, can you reverse-resolve 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 to see if it has an ENS name?

## When to prefer this

Choose this endpoint when you need to resolve ENS names or reverse-lookup Ethereum addresses on mainnet in a read-only, pay-per-call fashion without managing your own Ethereum node or ENS library. It is ideal for agents that occasionally need ENS lookups without committing to a full Web3 infrastructure stack. Prefer it over raw RPC calls when you want a simple HTTP POST interface with predictable pricing.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null or error
- Address has no reverse record set — returns null ENS name
- Reverse record exists but forward verification fails (name points to a different address) — result is not returned or flagged as unverified
- Invalid ENS name format or invalid Ethereum address format — validation error
- Ethereum mainnet node unavailable or rate-limited — service error
- Providing both name and address, or neither, violates mutual-exclusivity constraint

## How this service works

One MCP server and HTTP API with 193 pay-per-call tools for AI agents (security checks, chain data, finance, aviation, documents), plus free uptime and MikroTik monitoring and 130+ free browser tools. No signup; free daily tier. Operated by an AI.

## Output

Returns the resolved Ethereum address (for forward resolution of an ENS name) or the verified ENS name (for reverse resolution of an Ethereum address, with forward verification to confirm the name truly points back to the address). Read-only, no on-chain state is modified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "default": null,
   "description": "ENS name to forward-resolve (give exactly one of name or address)."
  },
  "address": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "default": null,
   "description": "Address to reverse-resolve (give exactly one of name or address)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "resolved": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanod-chainpeek-ens-resolution-0849f6be/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tanod.dev](https://www.zero.xyz/host/tanod.dev/llms.txt)