sseMITupdated 1mo ago
Resolve ENS names to ETH addresses and reverse -- avatar URLs included. Identity layer for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
What can you do with ENS Resolver API?
ENS Resolver API
Resolve ENS names to ETH addresses and reverse -- avatar URLs included. Identity layer for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"ens-resolver": {
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl -X POST "https://ens-resolver.api.klymax402.com/api/resolve" \
-H "Content-Type: application/json" \
-d '{}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
crypto_resolve_ens |
POST | /api/resolve |
$0.005 | Resolve ENS name to Ethereum address or reverse-resolve address to ENS name |
crypto_resolve_ens
Use this when you need to resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name. Returns resolution data in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
name |
string | no | ENS name to resolve (e.g. vitalik.eth) |
address |
string | no | Ethereum address for reverse resolution (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045) |
Returns
address-- resolved Ethereum address (0x...)ensName-- ENS name (e.g. vitalik.eth)avatar-- avatar URL associated with the ENS name (if set)resolvedDirection-- "forward" (name to address) or "reverse" (address to name)
Example response:
{"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","ensName":"vitalik.eth","avatar":"https://...","resolvedDirection":"forward"}
When to use: sending funds to an ENS name to verify the correct address. Essential for identity resolution and human-readable wallet lookup.
Not for: wallet balances (use wallet_get_portfolio), token safety (use token_check_safety), NFT metadata (use crypto_get_nft_metadata).
Example agent prompts
- "Resolve an ENS name to an Ethereum address, or reverse-resolve an address to its ENS name"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Install
Add ENS Resolver API to your client. Pick the one you use.
claude mcp add --transport sse ens-resolver-api https://ens-resolver.api.klymax402.com/mcpcodex mcp add ens-resolver-api --url https://ens-resolver.api.klymax402.com/mcp{
"mcpServers": {
"ens-resolver-api": {
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"ens-resolver-api": {
"type": "sse",
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"ens-resolver-api": {
"url": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"ens-resolver-api": {
"serverUrl": "https://ens-resolver.api.klymax402.com/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
1 tool
ENS Resolver API exposes one tool to a connected agent.
- crypto_resolve_ens
- POST
Score
76 / 100
Good
- Documentation22/25
- Maintenance25/25
- Trust13/20
- Capability4/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 25 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 1 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.1.0Latest | May 16, 2026 |
| 1.0.1 | Apr 23, 2026 |
| 1.0.0 | Apr 13, 2026 |