Products / Checkpoint StreamsNew

Replay every checkpoint since genesis, then keep going.

One gRPC connection carries you from any starting checkpoint to the live tip and stays there. Ordered, exactly-once, and standard SubscribeCheckpoints on the wire.

mainnet-grpc.inodra.com:443
SUBSCRIBE FROM HISTORY
meta: {
'x-api-key': 'indr_pat_qsVO...',
'x-inodra-start-checkpoint': '50000000',
'x-inodra-end-checkpoint': '50100000', // optional
}
for await (const { cursor, checkpoint }
of stream.responses) { index(checkpoint) }

What people actually build on it.

01

Bootstrap an indexer from zero

Point a fresh indexer at genesis and let it run to the live tip on one connection. There is no separate archive job to build and no gap to stitch at the seam.

start-checkpoint: 0
02

Rebuild a pipeline after a bad deploy

Set a start and an end checkpoint and replay an exact range. You get a clean completion, so a backfill after an incident is reproducible rather than approximate.

start and end checkpoint
03

Feed a warehouse without a firehose

Adaptive pacing keeps historical replay flowing steadily instead of bursting and stalling, so a downstream consumer sees a stream it can keep up with.

SubscribeCheckpoints

You pay for bytes, so field masks pay off.

A checkpoint stream is billed by volume, not by checkpoint count. Ask for only the fields you index and the bill falls with the payload.

WHAT IS METERED
DETAIL
CREDITS
Checkpoint data streamed
Metered by volume across the whole replay, live or historical
1 per 50 KB
Minimum per message
A floor, so a tiny checkpoint still counts as one
1
Field mask
Selecting fewer fields sends fewer bytes and costs fewer credits
billed by size

A backfill is priced by what you actually pull down.See what every call costs on the pricing page ->

One connection, no seam.

Start anywhere in history

Open from genesis, from last week, or from one checkpoint ago. There is no pruning horizon and no from-now-onwards limitation to work around.

Backfill flows into live

The same connection runs from your start checkpoint to the tip and keeps going. There is nothing to stitch and no gap where the archive ends and the subscription begins.

Ordered, exactly-once, resumable

Checkpoints arrive in strict sequence, no gaps, no duplicates. Every message carries a cursor, so reconnecting is one header away.

How hard you can push it.

Free10 RPS
Team50 RPS
Growth100 RPS
Professional200 RPS
Business500 RPS
Enterprise1,000+ RPS

A replay is bounded by your monthly credits, not by RPS. Compare every plan ->

Pick a checkpoint and press play.

Get your API key

Standard SubscribeCheckpoints, so your existing indexer client works unchanged.