# Base Basename Resolver (Forward & Reverse)

> Base Basename Resolver (Forward & Reverse) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-29).

Resolves a Base Basename (e.g. alice.base.eth) to an address, or reverse-resolves an address to its Base Basename, using the Base ENS registry.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/basename-resolve?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-basename-resolver-forward-reverse-517d3299
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CRoG2BWlrtr-bOaxIagJq

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 base-basename-resolver-forward-reverse-517d3299 -d '<json body>'
```

Example prompt: What wallet address does alice.base.eth resolve to on Base? And can you also check what Basename is linked to 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?

## When to prefer this

Use this endpoint when you need to resolve Base-specific Basenames (*.base.eth) to Ethereum addresses or reverse-resolve Base wallet addresses to their human-readable Basenames. It is purpose-built for the Base L2 ENS registry and does not perform L1 CCIP-read, making it faster and cheaper than a general ENS resolver for Base-native names. Prefer this over generic ENS APIs when the target name is known to be a Base Basename.

## Known failure modes

- Name not registered on Base registry → resolved: false
- Address has no reverse record set → resolved: false
- Both name and address sent simultaneously → validation error (send only one)
- Invalid address format → error response
- L1-only ENS names with CCIP-read dependency → not supported, resolved: false
- Payment not included or incorrect amount → 402 Payment Required (use /v1/sandbox/basename-resolve for free testing)

## How this service works

Call when an agent needs a Base Basename forward or reverse lookup. Send name (alice or alice.base.eth) or address, not both. Single labels become label.base.eth. Base registry only: no L1 CCIP-read. Unresolved is resolved false. Send JSON {"name":"alice.base.eth"}. Exact $0.005 USDC on Base. Try unpaid POST /v1/sandbox/basename-resolve first.

## Output

Returns a JSON object indicating whether the name or address resolved successfully (resolved: true/false), along with the resolved counterpart — either the Ethereum address for a forward lookup or the Basename for a reverse lookup. Unresolvable names/addresses return resolved: false.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "examples": [
    "alice.base.eth"
   ],
   "description": "Basename or ENS label. Example: alice.base.eth. A single label such as alice is read as alice.base.eth. Other ASCII .eth names are looked up on the Base registry only, with no L1 CCIP-read. Send name or address, not both."
  },
  "address": {
   "type": "string",
   "description": "Address to reverse-resolve on Base. Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Uses {address}.addr.reverse on the Base ENS registry. Send address or name, not both."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-basename-resolver-forward-reverse-517d3299/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)