Fill in history with the filters you run live.
Replay a range of past blocks into your database with the same filters you run live, then keep streaming new blocks as they land.
Every past block in your database, with the filters you already run.
One filter, past and present.
Backfills replay past blocks through the same Streams filters you run live, so history and live data always match.
Launch with full history, not just today’s blocks.
Load the range you need into your database, then keep streaming new blocks as they land. No one-off backfill script to maintain.
No gaps, no duplicates.
Backfills run in order and pick up where they left off, so your tables match the chain even if a job gets interrupted.
Query it where your team already works.
Query it in SQL, call it through an API, or get it delivered to your warehouse on a schedule, with lineage intact end-to-end.
Agent-ready
Agents use the same data and execution as your team, through MCP, and can pay per request with x402.
How agents use QuicknodeHow Dune grew from 16 to 91 chains.
Dune had no primary provider, so historical and live traces, logs, and receipts were patched by hand. It made Quicknode its primary data source, and went from 16 to 91 chains in 12 months.
“Quicknode became our primary provider because the consistency held.”
Make your first request.
# Use the API key from your dashboard, then add your filter and destination curl -X POST https://api.quicknode.com/streams/rest/v1/streams \ -H "x-api-key: your-api-key" -H "Content-Type: application/json" \ --data '{"name":"usdc-history","network":"ethereum-mainnet","dataset":"block", "start_range":19000000,"end_range":19100000,"destination":"webhook"}'
Response200 OK
{
"id": "6f2a…c91d",
"status": "active",
"start_range": 19000000
}Before you start.
Building something harder? Bring in an engineer.
Tell us where it’s stuck, and we’ll help you size it, migrate it, or fix it.