Back to Browse
Halowerk Identity Name Resolver
x402
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.
Price / call$0.002
Success—
StatusUnknown
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.
Example use cases
ENS forward resolution for payments
“I need to send ETH to nick.eth — can you resolve that ENS name to its actual Ethereum address so I know where I'm sending funds?”
Reverse resolve wallet address to name
“Take this address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 and find its primary ENS name, and please verify the forward record actually matches so I know the name is legitimate.”
Verify .base.eth name ownership
“Look up jesse.base.eth — I want to know what address it resolves to, who owns it, and which resolver is being used.”
Technical details
Endpoint
POSThttps://ident.halowerk.com/v1/name-resolve?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| name | string | The name to resolve, e.g. vitalik.eth, jesse.base.eth or bonfida.sol. Either this or address. |
| chain | string | Which chain to use for a reverse lookup. |
| address | string | An address to resolve backwards to a name. Either this or name. |
| text_keys | array | ENS text records to read as well, e.g. ["avatar","url","com.twitter"]. |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"