# Bittensor Epoch State API

> Bittensor Epoch State API is a paid API for AI agents from api.carbon-cashmere.de, paid per call via x402, $0.01/call, status down (last checked 2026-09-14).

Returns the current Bittensor epoch state including block number, finality status, peer count, sync status, epoch number, progress within epoch, and blocks until the next epoch boundary.

## Facts

- Endpoint: GET https://api.carbon-cashmere.de/v1/bittensor/epoch
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-carbon-cashmere-de-b937fadf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZdHvQMrz9snCN7OS8r_55

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 api-carbon-cashmere-de-b937fadf
```

Example prompt: What's the current Bittensor epoch number, how many blocks are left until the next epoch, and is the node fully synced right now?

## When to prefer this

Use this endpoint when you need precise, real-time Bittensor epoch timing data — specifically blocks_until_next_epoch and progress_pct — for scheduling weight-setting operations, triggering emission-window alerts, or monitoring subnet synchronization. Prefer this over generic block explorers when you need structured epoch boundary calculations in a single call.

## Known failure modes

- Node temporarily out of sync — is_syncing may be true and data may be stale
- Network unreachability to Subtensor node — 503 or timeout
- High finality lag indicating chain instability

## How this service works

Professional crypto market intelligence. Real-time prices, signals, and market scoring.

## Output

Returns a JSON object with 9 fields: block_number (current chain height), finalized_block (last finalized block), finality_lag_blocks (gap between head and finalized), peer_count (connected peers), is_syncing (boolean sync status), epoch_number (current epoch index), blocks_into_epoch (progress since epoch start), blocks_until_next_epoch (blocks remaining in 360-block epoch window), and progress_pct (0-100 percentage through current epoch).

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "block_number": 7995930,
  "epoch_number": 22210,
  "progress_pct": 58.33,
  "blocks_into_epoch": 210,
  "blocks_until_next_epoch": 150
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-carbon-cashmere-de-b937fadf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.carbon-cashmere.de](https://www.zero.xyz/host/api.carbon-cashmere.de/llms.txt)