# GPUOps Block Data Endpoint

> GPUOps Block Data Endpoint is a paid API for AI agents from chain.gpuops.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Retrieves block-level data for a specified block number on one of 7 supported blockchain networks

## Facts

- Endpoint: POST https://chain.gpuops.io/v1/block
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gpuops-block-data-endpoint-1ff0f4a2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Gk-da7IXJ6TQ9oyMVFP0I

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 gpuops-block-data-endpoint-1ff0f4a2 -d '<json body>'
```

Example prompt: Fetch the block data for block number 20000000 on Ethereum using GPUOps — I need the block header details and transaction count.

## When to prefer this

Choose this endpoint when you need raw block-level data (header, metadata, transaction count) for a specific block number on one of the 7 supported chains and want pay-per-call pricing with no subscription commitment. Ideal for agents that infrequently need precise historical or current block data without maintaining a full node connection.

## Known failure modes

- Invalid or unsupported chain identifier returns an error
- Block number does not exist yet (future block) returns not found
- Malformed blockNumber string causes validation error
- Payment failure via x402/USDC results in 402 response before data is returned
- Network timeout if the underlying chain node is slow to respond

## How this service works

Multi-chain blockchain data API. 7 chains. x402 pay-per-call with USDC on Base.

## Output

Returns structured block-level data for the requested chain and block number, including fields such as block hash, parent hash, timestamp, transaction count, gas used, gas limit, miner/validator address, and other block header fields as available for the specified chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string"
  },
  "blockNumber": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gpuops-block-data-endpoint-1ff0f4a2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain.gpuops.io](https://www.zero.xyz/host/chain.gpuops.io/llms.txt)