# Cross-Chain Name Resolver (ENS / Bonfida SNS)

> Cross-Chain Name Resolver (ENS / Bonfida SNS) is a paid API for AI agents from api.anchor-x402.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Resolves human-readable blockchain names (ENS .eth, Bonfida .sol) to their underlying wallet addresses or records across chains

## Facts

- Endpoint: POST https://api.anchor-x402.com/v1/resolve/name
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-anchor-x402-com-c598ceda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BvTrGCJLcqK5RL6K1AFv3

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 api-anchor-x402-com-c598ceda -d '<json body>'
```

Example prompt: What wallet address does vitalik.eth resolve to? Also try looking up bonfida.sol for me.

## When to prefer this

Use this endpoint when you need to resolve a human-readable crypto name (ENS .eth or Bonfida .sol) to a wallet address or on-chain record, especially in a cross-chain context. Prefer it over rolling your own RPC calls when you need a single unified API that handles both ENS and Solana SNS without managing separate providers.

## Known failure modes

- Name not registered or expired — returns not found or null address
- Unsupported TLD or name format — returns validation error
- Network connectivity issues with ENS/SNS RPC nodes — returns upstream error
- Malformed name input (missing dot, invalid characters) — returns 400 bad request
- Name exists but has no resolver set — returns empty or null record

## How this service works

Cross-chain name resolver (POST wrapper, body: {name}) — $0.001 USDC

## Output

Returns the resolved wallet address or on-chain records associated with the given human-readable name (e.g. vitalik.eth → 0x..., bonfida.sol → a Solana public key), along with the name system and chain detected.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "name": "vitalik.eth"
  }
 }
}
```

## 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": {
     "required": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "description": "Human-readable name (e.g. vitalik.eth, bonfida.sol)."
      }
     }
    },
    "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"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "notes": null,
  "addresses": [
   {
    "chain": "ethereum",
    "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "ttl_hint_seconds": 3600
   }
  ],
  "resolved_at": 1746820000,
  "registry_used": "ENS",
  "supported_tlds": [
   ".eth",
   ".sol"
  ]
 }
}
```

## More

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