# Basename Resolver

> Basename Resolver is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves Base L2 Basenames to Ethereum addresses (forward) or Ethereum addresses to their primary Basename (reverse) using the Base L2 Resolver.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/basename
- 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/basename-resolver-912d1211
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6iLbtpSHPJKK7JORFclLE

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 basename-resolver-912d1211
```

Example prompt: What Ethereum address does jesse.base.eth resolve to on Base?

## When to prefer this

Use this endpoint when you need to resolve Basenames (*.base.eth) specifically on the Base L2 network, as opposed to generic ENS resolution on Ethereum mainnet. It requires no API key, supports both forward and reverse resolution in a single endpoint, and uses the canonical Base L2 Resolver for authoritative results. Prefer it over general ENS libraries when your agent is already operating in the Base ecosystem.

## Known failure modes

- Name not registered — Basename has no associated address
- Address has no primary Basename set — returns null or empty
- Invalid input format — malformed address or non-.base.eth name
- Network or resolver timeout — Base L2 RPC unavailable
- Payment failure — $0.01 USDC x402 payment not processed

## How this service works

Forward + reverse Basename resolution read from the Base L2 Resolver: turn jesse.base.eth into an address, or an address into its primary Basename. No API key required.

## Output

Returns either the resolved Ethereum address (for a forward Basename lookup) or the primary Basename string (for a reverse address lookup), pulled directly from the Base L2 Resolver on-chain.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "query"
     ],
     "properties": {
      "query": {
       "type": "string",
       "description": "Basename or address"
      }
     }
    }
   },
   "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/basename-resolver-912d1211/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)