# VNS Name Resolver (Forward & Reverse)

> VNS Name Resolver (Forward & Reverse) is a paid API for AI agents from theloopbreaker.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves VaultfireNameService (VNS) names to wallet addresses (forward) or addresses to VNS names (reverse) across Base, Arbitrum, and Polygon, with ERC-8004 identity registry fallback.

## Facts

- Endpoint: GET https://theloopbreaker.com/api/x402/trust/vns-resolve
- 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/theloopbreaker-com-28a992fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A4SiMNxCWKPXMPiqRT2bZ

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 theloopbreaker-com-28a992fc
```

Example prompt: What wallet address does the VNS name 'vaultfire.agent' resolve to on Base — and if it's not found in VNS, check the ERC-8004 registry too?

## When to prefer this

Use this endpoint when you need to resolve human-readable VNS names to wallet addresses (or vice versa) specifically within the Vaultfire ecosystem across Base, Arbitrum, and Polygon. Prefer this over generic ENS resolvers when working with AI agents registered via ERC-8004 or Vaultfire's name service, as the ERC-8004 fallback ensures full coverage for agents not yet in VNS.

## Known failure modes

- VNS name not registered on any supported chain — returns not-found or null result
- Address has no associated VNS name and no ERC-8004 entry — empty resolution result
- Unsupported chain specified — error indicating valid chains are Base, Arbitrum, Polygon
- Malformed address or name input — validation error
- Payment header missing or insufficient — 402 Payment Required
- Network RPC unavailability for a specific chain causing partial or failed resolution

## How this service works

Resolve VNS names to addresses (forward) or addresses to VNS names (reverse) across Base, Arbitrum, and Polygon. Falls back to ERC-8004 identity registry for full coverage.

## Output

Returns the resolved wallet address (for a forward lookup) or the VNS name/identity record (for a reverse lookup), including which chain the resolution was found on and whether the result came from VNS directly or the ERC-8004 fallback registry.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object"
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

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