Name Resolution ENS and DNS

blockchain

Serving

ENS and reverse name resolution across EVM chains: name and address pairs with resolution proofs. POST /v1/name with a {name} to resolve forward (or an address to reverse-resolve) and get the pair and source as one JSON object. Deterministic per block. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/name-resolution/v1/name
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/name-resolution/v1/name \
  -H 'content-type: application/json' \
  -d '{"name":"vitalik.eth"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Name Resolution ENS and DNS accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/name`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "Provide a name to resolve forward or an address to reverse-resolve.",
  "properties": {
    "name": {
      "type": "string",
      "description": "An ENS name to resolve forward, e.g. vitalik.eth."
    },
    "address": {
      "type": "string",
      "description": "An address to reverse-resolve."
    }
  },
  "required": [
    "name"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/name, a JSON object with the resolved name/address pair, the source, and a resolution proof. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}