# EVM Chain Current Block Height

> EVM Chain Current Block Height 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 the current block number for any of ten supported EVM-compatible blockchains via a pay-per-call endpoint.

## Facts

- Endpoint: POST https://twin.unykorn.org/evm-block-number?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-current-block-height-d95e7dac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lqVcQ7ZpufSrN0rL8l8Tu

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-current-block-height-d95e7dac -d '<json body>'
```

Example prompt: What's the current block height on the Base chain right now?

## When to prefer this

Use this endpoint when you need the current block height for any of ten major EVM chains (Ethereum, Base, Polygon, Arbitrum, Optimism, BSC, Avalanche, Gnosis, Linea, Scroll) in a pay-per-call model without managing your own RPC infrastructure. Prefer this over running your own node when cost-per-call ($0.001 USDC) is preferable to infrastructure overhead, or when you need multi-chain coverage from a single API surface.

## Known failure modes

- Invalid chain name not in the supported enum returns an error
- Network timeout if the upstream RPC node is unavailable
- Payment failure if insufficient USDC balance for the x402 micro-payment
- Malformed request body missing the params.chain field

## How this service works

Current block height on any of ten EVM chains — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok status, the type field 'evm-block-number', a receipt object containing a transaction hash, USD cost, and receipt ID, and a generated_at ISO8601 timestamp. The current block number for the requested chain is included in the response payload.

## 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": "evm-block-number",
  "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-current-block-height-d95e7dac/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)