# EVM Chain Reference Data — UnyKorn/Genesis402

> EVM Chain Reference Data — UnyKorn/Genesis402 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-01).

Returns reference data and metadata for a specified supported EVM chain

## Facts

- Endpoint: POST https://twin.unykorn.org/chain-info?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-chain-reference-data-unykorn-genesis402-ed941c6e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NcAzDfe1TYou4H2F6bUjZ

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 evm-chain-reference-data-unykorn-genesis402-ed941c6e -d '<json body>'
```

Example prompt: Can you pull up the reference data for the Base chain from the UnyKorn network?

## When to prefer this

Use this endpoint when you need authoritative, on-demand reference metadata for one of ten specific supported EVM chains (Ethereum, Base, Polygon, Arbitrum, Optimism, BSC, Avalanche, Gnosis, Linea, Scroll) and are operating in an x402 pay-per-call environment. Prefer this over free public chain registries when you need a receipted, auditable lookup with provenance tracking via the UnyKorn/Genesis402 network.

## Known failure modes

- Unsupported chain name returns validation error
- Payment not received or insufficient funds causes 402 rejection
- Network timeout from underlying chain data provider
- Malformed request body returns schema validation error

## How this service works

Reference data for a supported EVM chain — Genesis402 / UnyKorn Operator Network

## Output

A JSON object with ok status, chain type info, a receipt containing a transaction hash, USD amount paid, and a receipt ID, plus an ISO 8601 generation timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "chain": {
     "enum": [
      "ethereum",
      "base",
      "polygon",
      "arbitrum",
      "optimism",
      "bsc",
      "avalanche",
      "gnosis",
      "linea",
      "scroll"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "chain-info",
  "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/evm-chain-reference-data-unykorn-genesis402-ed941c6e/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)