# ENS Namehash and Labelhash Calculator

> ENS Namehash and Labelhash Calculator is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Computes the ENS namehash and labelhash for a given Ethereum Name Service (ENS) domain name

## Facts

- Endpoint: POST https://twin.unykorn.org/eth-namehash?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-namehash-and-labelhash-calculator-746ef658
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yHG_DsqD7ebGNztveJJlv

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-namehash-and-labelhash-calculator-746ef658 -d '<json body>'
```

Example prompt: What is the ENS namehash and labelhash for vitalik.eth?

## When to prefer this

Use this endpoint when you need to programmatically compute ENS namehash or labelhash values without implementing the hashing logic locally, especially in agentic workflows that interact with ENS smart contracts on EVM chains. Prefer this over local computation when you want a trusted, pay-per-call reference implementation that removes the risk of encoding bugs.

## Known failure modes

- Invalid or malformed ENS name returns an error response
- Missing 'name' field in request body causes a 400-level error
- Payment failure or insufficient funds prevents the call from completing
- Network timeout on the UnyKorn endpoint
- Name with unsupported characters or encoding may produce unexpected results

## How this service works

ENS namehash and labelhash for a name — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object containing the ENS namehash and labelhash for the provided name, along with a payment receipt including transaction hash, amount paid in USD, and a receipt ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "name": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "eth-namehash",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.001,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-namehash-and-labelhash-calculator-746ef658/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)