# Vextorium ENS Batch Resolver

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

Resolves up to 20 ENS names to Ethereum addresses, or Ethereum addresses to their primary ENS names, in a single batch call.

## Facts

- Endpoint: POST https://api.vextorium.com/ens-resolver-lote-pago?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-ens-batch-resolver-9a2ed30d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CgNeGxpZEIP3ZH_NfM3FJ

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-batch-resolver-9a2ed30d -d '<json body>'
```

Example prompt: Can you resolve these ENS names to their Ethereum addresses in one go: vitalik.eth, ens.eth, and uniswap.eth? Also do a reverse lookup on 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 to find its primary ENS name.

## When to prefer this

Choose this endpoint when you need to resolve multiple ENS names or addresses in a single API call rather than one at a time, saving on latency and cost. Ideal for enriching datasets, attributing wallet addresses to human-readable identities, or verifying ENS ownership in bulk. Prefer this over single-item resolvers when batch efficiency matters, and over general blockchain explorers when you specifically need ENS forward and reverse resolution without extra blockchain data.

## Known failure modes

- ENS name does not exist or has no address record set — returns null address
- Ethereum address has no primary ENS name set — returns null name
- Batch exceeds 20 entries — likely rejected or partially processed
- Network/RPC connectivity issues causing resolution failure
- Malformed address or ENS name in the input array — returns null fields for that entry

## How this service works

Resolve up to 20 ENS names to addresses, or addresses to their primary ENS name, in one call.

## Output

Returns a JSON object with the count of successfully resolved entries and an array of result objects. Each result includes the original query string, the resolved Ethereum address, and the primary ENS name (if available via reverse lookup). Fields may be null when resolution is not possible for a given entry.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "nombres": {
   "type": "array",
   "items": {
    "type": "string"
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "resueltos": 2,
  "resultados": [
   {
    "nombre": null,
    "consulta": "vitalik.eth",
    "direccion": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
   },
   {
    "nombre": "vitalik.eth",
    "consulta": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "direccion": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-ens-batch-resolver-9a2ed30d/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)