# Blockscout Celo Epoch Details

> Blockscout Celo Epoch Details is a paid API for AI agents from api.blockscout.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-12).

Retrieves detailed information about a specific Celo epoch by number, including block range, timestamps, distribution data, and aggregated election rewards

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/celo/epochs/%7Bnumber%7D
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-celo-epoch-details-7a4417d7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vxFX1HdccAp1CNtpNqGj7

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 blockscout-celo-epoch-details-7a4417d7
```

Example prompt: Pull the details for Celo epoch number 1500 on Blockscout — I need the block range, timestamp, finalization status, and the aggregated election rewards.

## When to prefer this

Use this endpoint when you need structured, per-epoch data specific to the Celo blockchain, especially for validator election rewards, epoch block ranges, finalization status, or staking distribution audits. Prefer this over generic block explorers when you need Celo-native epoch semantics (Celo's epoch-based consensus model) rather than raw block data.

## Known failure modes

- Invalid epoch number returns 404 not found
- Invalid or unsupported chain_id returns an error or empty response
- Epoch number not yet processed returns incomplete or missing data
- Malformed path parameters return 400 bad request
- Rate limiting or payment failure returns 402 payment required

## How this service works

Explore crypto activities with Blockscout's multichain search. Find transactions, addresses, tokens, and dapps across top blockchain networks — your go-to explorer for cross-chain blockchain data

## Output

Returns a JSON object for the specified Celo epoch containing: epoch number, timestamp, start and end block numbers, start and end processing block hashes and numbers, finalization status (is_finalized), distribution details, and aggregated election rewards broken down by category.

## 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"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "number": {
       "type": "string"
      },
      "chain_id": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "type": "string",
  "number": 0,
  "timestamp": "string",
  "distribution": {},
  "is_finalized": true,
  "end_block_number": 0,
  "start_block_number": 0,
  "end_processing_block_hash": "string",
  "aggregated_election_rewards": {},
  "end_processing_block_number": 0,
  "start_processing_block_hash": "string",
  "start_processing_block_number": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-celo-epoch-details-7a4417d7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockscout.com](https://www.zero.xyz/host/api.blockscout.com/llms.txt)