RPC for Indexers, Subgraphs & Data Pipelines
Indexers hammer eth_getLogs and historical reads — the exact calls public endpoints rate-limit or block outright. A backfill that should take hours ends up taking days.
Where public RPC falls short
- Public RPCs block or throttle eth_getLogs and trace_* — your backfill crawls.
- Some providers bill heavy methods at premium per-call rates, with surprise overage invoices at month-end.
- Running a different provider per chain means stitching together rate limits and auth.
How NodeFlare handles it
Heavy methods included
eth_getLogs, trace_*, and debug_* work on every plan — even the free tier.
Compute-unit billing
Pay for what you use via compute units, with no per-method premiums and no surprise overages.
All chains, one key
Index across all 23 supported chains with a single key and one endpoint pattern.
Recommended chains
FAQ
Is eth_getLogs rate-limited?
Heavy methods are unlocked on every plan, including free. Usage is metered by compute units (getLogs weighs more than a simple read), not blocked or per-call surcharged.
Can I do historical / archive reads?
Yes — our nodes serve historical reads needed for indexing and backfills across the supported chains.
How does billing work for indexing workloads?
Compute units per month, with heavier methods weighing more. No per-chain fees and no overage invoices — you stay within your plan's CU budget.
Free key, first call in under a minute
Every chain, multi-region failover, no throttling — no credit card.