# Solana Epoch Progress

> Solana Epoch Progress is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-01).

Returns the current Solana epoch progress, including epoch number, slot position, and timing data

## Facts

- Endpoint: POST https://twin.unykorn.org/solana-epoch?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/solana-epoch-progress-d7ca5c67
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_czVy6ofvvx9nknoTNkZ0O

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 solana-epoch-progress-d7ca5c67 -d '<json body>'
```

Example prompt: What's the current Solana epoch and how far along is it — like how many slots have passed and how many are left?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call lookup of the current Solana epoch state without running your own Solana RPC node. It is ideal for agents that need epoch timing for staking, validator operations, or conditional workflows triggered by epoch transitions, and that want a verifiable payment receipt attached to each response.

## Known failure modes

- Solana RPC node unavailable or rate-limited, returning a non-ok response
- Payment via x402 protocol fails or is rejected, blocking the call
- Network timeout if the upstream Solana RPC is congested
- Malformed response if the epoch data cannot be fetched at query time

## How this service works

Solana epoch progress — Genesis402 / UnyKorn Operator Network

## Output

A JSON object containing the current Solana epoch number, slot progress metrics (elapsed and remaining slots), epoch completion percentage, and a signed receipt with transaction hash, USD amount paid, and a unique receipt ID — along with a generated_at ISO8601 timestamp.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "solana-epoch",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.002,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/solana-epoch-progress-d7ca5c67/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)