# PennyRail EVM Block Number Lookup

> PennyRail EVM Block Number Lookup is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns the current block number of an EVM-compatible blockchain chain via a paid x402 micro-settlement endpoint

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/nano/chain.block-number--evm-block-number
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-evm-block-number-lookup-6be0d2e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N0OY4UiFdYbHRXdJR5iRq

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 pennyrail-evm-block-number-lookup-6be0d2e1 -d '<json body>'
```

Example prompt: What is the current block number on Ethereum mainnet right now?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call lookup of the current EVM block number without managing your own RPC node infrastructure. Ideal for agents that need occasional chain height checks without a persistent Web3 provider setup. Prefer over free RPC endpoints when reliability and micro-payment settlement via x402 are acceptable trade-offs.

## Known failure modes

- Unsupported or unrecognized EVM chain identifier returns an error or empty response
- Network connectivity issues to the target chain node result in a timeout or 5xx error
- Payment of $0.001 USDC not fulfilled via x402 protocol causes a 402 Payment Required response
- Malformed input object causes validation failure

## How this service works

Machine-readable settlement service

## Output

Returns the current block number (block height) of the specified EVM-compatible blockchain network as a numeric value, representing how many blocks have been produced on that chain up to the moment of the request.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

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