# agenttoll.app Basename Resolver

> agenttoll.app Basename Resolver is a paid API for AI agents from agenttoll.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Resolves a Base blockchain basename to its Ethereum address, or an Ethereum address to its primary basename

## Facts

- Endpoint: GET https://agenttoll.app/api/base/name/agenttoll
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agenttoll-app-basename-resolver-a43d0113
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3GPiisGupC6j_8ZvqbO8G

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 agenttoll-app-basename-resolver-a43d0113
```

Example prompt: What wallet address does the basename 'vitalik.base.eth' resolve to, and what is the primary basename registered to that address?

## When to prefer this

Use this endpoint when you need bidirectional resolution between Base basenames and Ethereum addresses on the Base network. Prefer it over generic ENS resolvers when specifically working with Base chain identities (.base.eth). It handles both forward (name → address) and reverse (address → name) lookups in a single endpoint.

## Known failure modes

- Basename not registered — returns null or not-found response
- Address has no primary basename set — returns empty name field
- Invalid input format (neither valid .base.eth name nor 0x address) — returns 400 error
- Network or RPC timeout resolving on-chain name record
- Payment failure ($0.001 USDC x402) — returns 402 Payment Required

## How this service works

Basename resolution both ways: name to address, or address to primary name

## Output

Returns either the Ethereum address corresponding to the given basename, or the primary basename registered to the given 0x address. The response is a JSON object indicating the resolved counterpart (address or name) for the provided input.

## 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",
     "required": [
      "nameOrAddress"
     ],
     "properties": {
      "nameOrAddress": {
       "type": "string",
       "description": "A basename (.base.eth optional) or a 0x address"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/agenttoll-app-basename-resolver-a43d0113/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agenttoll.app](https://www.zero.xyz/host/agenttoll.app/llms.txt)