# Foundry Basename Resolver

> Foundry Basename Resolver is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-01).

Resolves a .base.eth Basename to its corresponding Base (EVM) wallet address and resolver metadata.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/basename-resolve?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-basename-resolver-0b26c6ba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QUBo1A4S1BJtcusm1NHs_

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 foundry-basename-resolver-0b26c6ba -d '<json body>'
```

Example prompt: Can you look up the wallet address for jesse.base.eth on the Base network?

## When to prefer this

Use this endpoint when you need to convert a human-readable .base.eth Basename into a machine-usable Base network wallet address. Prefer it over generic ENS resolvers when the target is specifically on the Base (L2) network and you need the Base-specific resolver metadata alongside the address.

## Known failure modes

- Name not registered: returns null or empty address if the Basename has no on-chain registration
- Invalid format: input missing '.base.eth' suffix or malformed may return an error
- Network unavailability: Base RPC or resolver contract temporarily unreachable may cause timeout
- Unregistered subdomain: sub-names under base.eth that are not Basenames return no result

## How this service works

Basename resolver: a .base.eth name to its Base address. Input: 'jesse.base.eth'.

## Output

Returns a JSON object containing the resolved Basename (e.g. 'jesse.base.eth'), the corresponding Base wallet address (0x-prefixed hex string), the network identifier ('base'), and the resolver contract address used to perform the lookup.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "A Basename like 'name.base.eth'"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "jesse.base.eth",
  "address": "0x2211d1D0020DAEA8039E46Cf1367962070d77DA9",
  "network": "base",
  "resolver": "0xC6d566A56A1aFf6508b41f6c90ff131615583BCD"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-basename-resolver-0b26c6ba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)