# Sift Web Tools – ENS Lookup

> Sift Web Tools – ENS Lookup is a paid API for AI agents from sift.srv1996466.hstgr.cloud, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-23).

Resolves an ENS name to its Ethereum address, or reverse-resolves an Ethereum address to its ENS name

## Facts

- Endpoint: GET https://sift.srv1996466.hstgr.cloud/v1/crypto/ens?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sift-web-tools-ens-lookup-ea78419c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ArdXIL-u7ftPdL5vFt5r3

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 sift-web-tools-ens-lookup-ea78419c
```

Example prompt: What Ethereum address does vitalik.eth resolve to?

## When to prefer this

Use this endpoint when an agent needs to resolve a human-readable .eth ENS name to an Ethereum wallet address (or vice versa) before executing a crypto transaction, enriching user profile data, or verifying identity in a Web3 context. Prefer it over querying Ethereum nodes directly because it is a simple pay-per-call REST GET with no Web3 library setup required.

## Known failure modes

- ENS name not registered or has no address set — may return null address or 404
- Invalid 0x address format — likely 400 bad request
- ENS name with no reverse record — reverse lookup returns no name
- Upstream ENS provider or RPC node unavailable — service error
- Rate limiting or payment failure — 402 or 429 response

## How this service works

ENS lookup: .eth name to address, or address to verified name. Resolves an .eth name to its address, or an address to its primary ENS name (only returned when the forward record matches).

## Output

Returns a JSON object containing the resolved ENS name and the corresponding Ethereum 0x address (e.g. {"name":"vitalik.eth","address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}). Works bidirectionally: pass either an ENS name or an 0x address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "q"
     ],
     "properties": {
      "q": {
       "type": "string",
       "description": ".eth name or 0x address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sift-web-tools-ens-lookup-ea78419c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sift.srv1996466.hstgr.cloud](https://www.zero.xyz/host/sift.srv1996466.hstgr.cloud/llms.txt)