# Pocket Network ENS Name Resolution

> Pocket Network ENS Name Resolution is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Resolves ENS names to addresses (forward) or addresses to ENS names (reverse) across EVM chains, returning the name-address pair with resolution proofs

## Facts

- Endpoint: POST https://agent.pocket.network/v1/name-resolution?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-ens-name-resolution-9df6f3a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iQMXAuFJfiMZmX4faGSAB

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 pocket-network-ens-name-resolution-9df6f3a8 -d '<json body>'
```

Example prompt: Can you resolve vitalik.eth to its Ethereum address using ENS name resolution — I need the full address with the resolution proof?

## When to prefer this

Choose this endpoint when you need ENS forward or reverse resolution with cryptographic provenance proof on a pay-per-call basis (no API key or account required). Ideal for agents that need to resolve .eth names or wallet addresses on demand without managing API credentials or subscriptions. Prefer this over web-scraping ENS explorers when you need structured JSON output with resolution proofs, and over running your own node when you want zero infrastructure overhead at $0.005 per call.

## Known failure modes

- ENS name does not exist or has no resolver set — returns empty or null data
- Address has no reverse record registered — reverse resolution returns null
- Malformed input (non-.eth name, invalid address format) — schema validation error
- Name recently updated — result may reflect a prior block state due to deterministic-per-block design
- Payment failure for USDC micropayment — request rejected before resolution attempt

## How this service works

Pay-per-call access to Pocket Network services. No account, no API key.

## Output

A JSON object containing the resolved name-address pair, the resolution source or provenance (e.g. on-chain ENS registry), and a schema-check status from the Pocket portal wrapper. The data field contains the actual name and address mapping; the portal field provides service metadata including serviceId and provenance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "An ENS name to resolve forward, e.g. vitalik.eth."
  },
  "address": {
   "type": "string",
   "description": "An address to reverse-resolve."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "portal": {
   "serviceId": "name-resolution",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-ens-name-resolution-9df6f3a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)