# TokenGuard ENS Resolver

> TokenGuard ENS Resolver is a paid API for AI agents from eltociear-tokenguard.hf.space, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Resolves an ENS (Ethereum Name Service) domain name to its underlying Ethereum address and record type

## Facts

- Endpoint: POST https://eltociear-tokenguard.hf.space/ens
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tokenguard-ens-resolver-f193e1db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5aGj-X1cjrUWCx-1ainL1

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 tokenguard-ens-resolver-f193e1db -d '<json body>'
```

Example prompt: What Ethereum wallet address does vitalik.eth resolve to? I need the actual 0x address and want to know if it's a forward resolution.

## When to prefer this

Use this endpoint when you need to resolve a human-readable .eth ENS name to its underlying Ethereum address as part of a crypto transaction, identity verification, or on-chain analytics workflow. It is part of a broader 65-route crypto/DeFi API, making it convenient when you already rely on TokenGuard for other DeFi data. Prefer dedicated ENS libraries for high-volume batch resolution.

## Known failure modes

- ENS name does not exist or is unregistered — likely returns an error or null address
- ENS name has no forward record set — may return empty or error response
- Invalid ENS format (missing .eth or malformed) — likely returns a 400-style error
- Payment failure via x402 micropayment — returns 402 Payment Required
- Upstream ENS resolver or RPC node timeout — may return 5xx error

## How this service works

ENS resolution: name->address (forward) or address->primary name (reverse). Ethereum mainnet.

## Output

Returns a JSON object containing the ENS name queried, the resolution type (e.g. 'forward'), and the resolved Ethereum wallet address (0x hex format).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "ENS name or 0x address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "type": "forward",
  "address": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tokenguard-ens-resolver-f193e1db/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from eltociear-tokenguard.hf.space](https://www.zero.xyz/host/eltociear-tokenguard.hf.space/llms.txt)