# Vextorium ENS Resolve

> Vextorium ENS Resolve is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-15).

Resolves an ENS name to its Ethereum address, or reverse-resolves an Ethereum address to its ENS name

## Facts

- Endpoint: POST https://api.vextorium.com/v1/ens-resolve?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-ens-resolve-fc54570c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dXh2gGG5S9UNfj2sxqeg9

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 vextorium-ens-resolve-fc54570c -d '<json body>'
```

Example prompt: What Ethereum wallet address does vitalik.eth resolve to?

## When to prefer this

Use this endpoint when you need to bidirectionally resolve between ENS human-readable names and raw Ethereum 0x addresses in a pay-per-call, no-subscription model. Prefer it when building agents that handle ENS lookups alongside other on-chain data tasks via Vextorium's unified API, paying in USDC via x402.

## Known failure modes

- ENS name does not exist or is unregistered — address field returns null
- 0x address has no reverse ENS record set — ens_name field returns null
- Malformed query (invalid ENS format or invalid hex address) — validation error
- Network or RPC timeout causing resolution failure
- ENS name expired and no longer resolves to an address

## How this service works

558 pay-per-call data APIs for AI agents: Solana and EVM on-chain data, tokenized stocks, DeFi, Hyperliquid, economy and official statistics, FX, validation, web and developer tools. Pay in USDC via x402.

## Output

Returns a JSON object containing both the resolved Ethereum address (e.g. '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045') and the ENS name (e.g. 'vitalik.eth'). Either field may be null if no reverse record or ENS name is set for the given input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "ENS name (e.g. vitalik.eth) or 0x address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "ens_name": "vitalik.eth"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-ens-resolve-fc54570c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)