# ENS Name Resolver with Forward-Verification

> ENS Name Resolver with Forward-Verification is a paid API for AI agents from evm-canon-base.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves ENS names to Ethereum addresses and performs reverse resolution with forward-verification of reverse records

## Facts

- Endpoint: POST https://evm-canon-base.onrender.com/resolve
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-name-resolver-with-forward-verification-37ee7949
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DsU9H3Ze3g0Mkp4XKtslj

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 ens-name-resolver-with-forward-verification-37ee7949 -d '<json body>'
```

Example prompt: What Ethereum address does vitalik.eth resolve to, and can you also do a forward-verified reverse lookup so I know the ENS name is actually confirmed for that address?

## When to prefer this

Choose this endpoint when you need reliable, forward-verified ENS resolution on EVM-compatible chains — particularly when security matters and you cannot trust an unverified reverse record alone. Ideal for dApps displaying human-readable identities, payment routing via ENS names, or any workflow that must confirm bidirectional ENS consistency. Prefer over raw RPC calls when you want deterministic, schema-validated output with built-in forward-verification logic included in a single call.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null or error
- Address has no reverse record registered — resolution fails gracefully
- Reverse record exists but forward-verification fails — flags mismatch
- Network/RPC issues causing lookup timeout
- Malformed ENS name or invalid Ethereum address input
- ENS name is expired and no longer valid

## How this service works

Resolve ENS names to addresses and reverse, with forward-verification of reverse records

## Output

Returns the resolved Ethereum address for a given ENS name, or the ENS name for a given address via reverse resolution. For reverse lookups, includes forward-verification status confirming that the reverse record is canonical (i.e., the name's forward resolution also points back to the same address), preventing spoofed or unconfirmed reverse records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {
      "name": {
       "type": "string"
      },
      "address": {
       "type": "string"
      }
     },
     "description": "provide exactly one of name or address"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-name-resolver-with-forward-verification-37ee7949/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from evm-canon-base.onrender.com](https://www.zero.xyz/host/evm-canon-base.onrender.com/llms.txt)