# ENS Name Expiry Lookup

> ENS Name Expiry Lookup is a paid API for AI agents from x402.onchainexpat.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns the expiration date and registration status of an Ethereum Name Service (ENS) domain name

## Facts

- Endpoint: POST https://x402.onchainexpat.com/api/x402-crypto/ens-expiry
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-name-expiry-lookup-d0913127
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SA-N76xICcxGwc8GrUQCu

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 ens-name-expiry-lookup-d0913127 -d '<json body>'
```

Example prompt: When does vitalik.eth expire? Check the ENS registration expiry for that name.

## When to prefer this

Use this endpoint when you need a quick, pay-per-use lookup of an ENS domain's expiry date without setting up your own Ethereum node or ENS SDK integration. Ideal for agents that only occasionally need ENS expiry data and want to avoid infrastructure overhead. At $0.01 USDC per call via x402, it is cost-effective for low-volume lookups.

## Known failure modes

- Invalid or malformed ENS name returns an error
- ENS name not found or never registered returns empty or null expiry
- Payment failure via x402 protocol returns 402 status
- Network or blockchain RPC error causes timeout or 500 error
- ENS name with non-.eth TLD may not be supported

## How this service works

Pay-per-request AI, crypto, proxy, and utility APIs using x402 protocol

## Output

Returns a JSON object containing the expiration/expiry date and registration details for the queried ENS domain name, indicating when the name was last registered and when it will expire or become available for re-registration.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "addresses"
 ],
 "properties": {
  "addresses": {
   "type": "string",
   "description": "Comma-separated Ethereum addresses (max 10)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "properties": {
    "results": {
     "type": "array",
     "description": "ENS domain expiry data for each address"
    },
    "queried_at": {
     "type": "string",
     "description": "ISO timestamp of query"
    },
    "addresses_without_ens": {
     "type": "array",
     "description": "Addresses with no ENS domains"
    }
   }
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-name-expiry-lookup-d0913127/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.onchainexpat.com](https://www.zero.xyz/host/x402.onchainexpat.com/llms.txt)
