# EVM Block Number Lookup

> EVM Block Number Lookup is a paid API for AI agents from agent-chain-kit-solana.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-10).

Returns the current block number for a specified EVM-compatible blockchain network (Ethereum, Base, Arbitrum, or Polygon).

## Facts

- Endpoint: GET https://agent-chain-kit-solana.vercel.app/v1/block-number?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-block-number-lookup-276d5ca5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1xxjxs4gbUgwfoPhTFSZE

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-block-number-lookup-276d5ca5
```

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

## When to prefer this

Choose this endpoint when you need the current block height for Ethereum, Base, Arbitrum, or Polygon without managing your own RPC node or API key. It is ideal for AI agents that need quick, pay-per-call blockchain reads without provisioning infrastructure. Prefer it over self-hosted RPC when low-setup cost matters and sub-second latency is acceptable.

## Known failure modes

- Unsupported network value returns a validation error
- Missing or malformed query parameter causes 400 Bad Request
- Payment not provided or invalid results in 402 Payment Required
- Upstream RPC node temporarily unavailable causing 503 or timeout
- Network congestion may cause slightly stale block number

## How this service works

Global current weather, hourly forecasts, foreign-exchange rates, EVM reads, and deterministic utilities for AI agents. Pay per call with MPP or x402; no API key.

## Output

A JSON object containing the current block number as a decimal integer, its hexadecimal representation, and the queried network name. Example: {"hex":"0x20f85d2","network":"base","block_number":34567890}.

## 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",
     "properties": {
      "network": {
       "enum": [
        "ethereum",
        "base",
        "arbitrum",
        "polygon"
       ],
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hex": "0x20f85d2",
  "network": "base",
  "block_number": 34567890
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-block-number-lookup-276d5ca5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-chain-kit-solana.vercel.app](https://www.zero.xyz/host/agent-chain-kit-solana.vercel.app/llms.txt)