# Halowerk Identity Name Resolver

> Halowerk Identity Name Resolver is a paid API for AI agents from ident.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-13).

Resolves ENS, .base.eth, and .sol names to addresses (with owner and resolver), or reverse-resolves an address to its verified primary name across Ethereum, Base, and Solana name services.

## Facts

- Endpoint: POST https://ident.halowerk.com/v1/name-resolve?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-identity-name-resolver-7226e4e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UQ5ZhjizG5S5apQdVl0Xy

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 halowerk-identity-name-resolver-7226e4e4 -d '<json body>'
```

Example prompt: Can you resolve vitalik.eth to its Ethereum address and also tell me who the owner and resolver are?

## When to prefer this

Choose this endpoint when you need cryptographically-grounded name-to-address or address-to-name resolution across Ethereum (ENS), Base (.base.eth), and Solana name services with built-in forward-verification of reverse records. Unlike basic ENS resolvers, this endpoint explicitly catches and reports reverse record mismatches, making it trustworthy for identity verification rather than just convenience lookup. Prefer it when you need the owner and resolver metadata alongside the address, or when you need multi-chain name resolution in a single API.

## Known failure modes

- Name not registered or expired — returns null/not-found response
- Reverse record exists but forward resolution disagrees — mismatch flag returned instead of silently accepting
- Unsupported TLD or name service — error indicating unsupported namespace
- Network/RPC failure reading on-chain state — upstream error propagated
- Malformed address input for reverse resolution — validation error

## How this service works

HALOWERK identwerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

Returns the resolved address for forward lookups, plus the resolver contract address and owner. For reverse lookups, returns the primary name and a verification status indicating whether the forward resolution of that name agrees with the source address, reporting any mismatch explicitly rather than silently accepting unverified reverse records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 255,
   "description": "The name to resolve, e.g. vitalik.eth, jesse.base.eth or bonfida.sol. Either this or address."
  },
  "chain": {
   "enum": [
    "ethereum",
    "base"
   ],
   "type": "string",
   "default": "ethereum",
   "description": "Which chain to use for a reverse lookup."
  },
  "address": {
   "type": "string",
   "maxLength": 64,
   "description": "An address to resolve backwards to a name. Either this or name."
  },
  "text_keys": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 64
   },
   "maxItems": 10,
   "description": "ENS text records to read as well, e.g. [\"avatar\",\"url\",\"com.twitter\"]."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-identity-name-resolver-7226e4e4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ident.halowerk.com](https://www.zero.xyz/host/ident.halowerk.com/llms.txt)