Head to head
Iteradian vs Infura
Iteradian and Infura both run managed RPC. Infura bills in credits, with daily and per-second caps; Iteradian bills a fixed monthly plan price in requests, at $39 per month for 25,000,000 requests, $169 per month for 80,000,000 requests, with overage capped per billing period. Iteradian has a free plan, Free RPC, across all 12 networks.
Iteradian
- Bills in
- Requests — one call is one request
- Entry paid plan
- Developer RPC: $39/month for 25,000,000 requests
- Free option
- Free
- Bittensor
- Native Subtensor JSON-RPC, every plan
Infura
- Bills in
- credits, with daily and per-second caps
- Entry paid plan
- Developer — $50/month, 15M credits per day
- Free option
- Yes — the Core plan is free, with 1 API key, 3,000,000 credits per day and 500 credits per second.
- Bittensor
- Not listed on its pricing page
Every Infura figure on this page was read from www.infura.io/pricing on . Providers change pricing without notice — check the source before deciding. Infura is a trademark of its owner; Iteradian is not affiliated with Infura.
Why teams pick Iteradian over Infura
A month, not a day
The allowance runs over your billing period. A launch-day spike borrows from the month instead of exhausting a daily cap.
Keys without a quota
Create a key per service, per environment, per customer. No plan limits how many, and each one carries its own IP allowlist and network list.
Bittensor next to Ethereum
Subtensor mainnet sits in the same catalogue as your EVM networks. Infura does not list Bittensor.
Side by side
| Feature | Iteradian | Infura |
|---|---|---|
| Billing unit | Requests — one call is one request | credits, with daily and per-second caps |
| Heavy methods cost more? | No — every call counts as one request | Yes — cost depends on the method |
| Entry paid plan | Developer RPC: $39/month for 25,000,000 requests | Developer — $50/month, 15M credits per day · 4,000 credits/second, 5 API keys |
| Free option | Free | Yes — the Core plan is free, with 1 API key, 3,000,000 credits per day and 500 credits per second. |
| Past the allowance | $0.005 per 1,000 requests, capped at $150 per period, then HTTP 429 | Add-on packs: $200 per month for 55,000,000 additional credits. |
| Bittensor | Native Subtensor JSON-RPC, every plan | Not listed on its pricing page |
| Networks | 12 in the catalogue, all on every plan | Infura states access to 40+ networks |
| Per-key controls | IP allowlist (up to 50), allowed networks, rate limit and expiry on every key | Not stated on the pages we read |
| Failover | Health-checked; a failed read tries up to 3 nodes | Not stated on the pages we read |
How the bill is built
How Infura bills
Infura bills in credits and caps them per day and per second, not per month. A daily cap behaves differently from a monthly quota: an unusual traffic day can exhaust it even when your monthly total is well within budget.
How Iteradian bills
One JSON-RPC call is one request, whether it is eth_blockNumber or a heavy eth_getLogs range; a batch of N calls counts as N. Past the monthly allowance, requests keep being served and are billed per 1,000, up to a spend cap per billing period. Past the cap the gateway answers HTTP 429 and the bill stops — so the worst case is known before the traffic arrives.
Both price lists, unconverted
Units differ, so nothing here is converted into the other side’s currency. Compare against your own traffic.
Iteradian — live from the control plane
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Free RPC | $0/mo | 3,000,000 requests/month | 25 requests/second |
| Developer RPC | $39/mo | 25,000,000 requests/month | 250 requests/second |
| Professional RPC | $169/mo | 80,000,000 requests/month | 500 requests/second |
| Dedicated RPC | Custom | — | — |
Infura
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Core | $0/mo | 3M credits/day | 500 credits/second, 1 API key |
| Developer | $50/mo | 15M credits/day | 4,000 credits/second, 5 API keys |
| Team | $225/mo | 75M credits/day | 40,000 credits/second, unlimited API keys |
| Enterprise | Custom | Elastic auto-scaling | Burstable |
Where each one is strong
What Infura does well
- A free Core tier with 3M credits per day.
- High per-second ceilings on paid tiers — 40,000 credits per second on Team.
- Backed by Consensys, with a long operating history.
- Debug and Trace APIs from the $50/month Developer tier upward.
Where Iteradian differs
- Iteradian meters a monthly request allowance, not a daily credit cap, so a busy day draws on the month instead of hitting a wall at midnight UTC.
- Iteradian serves Bittensor, which Infura does not list.
- Iteradian does not limit the number of API keys on any plan; Infura allows 1 on Core and 5 on Developer.
Choose Infura when…
You want a free tier today, very high burst throughput, or your organization already standardizes on Consensys tooling such as MetaMask.
Choose Iteradian when…
You prefer a monthly request allowance over a daily credit cap, you need Bittensor, or you want many keys with per-key IP allowlists on an entry plan.
Start the trialQuestions people ask
Is Iteradian cheaper than Infura?
It depends on your method mix, because the two meter differently. Infura bills in credits, with daily and per-second caps, while Iteradian bills a fixed monthly plan price in requests: $39 per month for 25,000,000 requests, $169 per month for 80,000,000 requests. Past the allowance, overage is capped per billing period, after which the gateway returns HTTP 429 — so the worst-case bill is known in advance. Compare against your own traffic before switching.
Does Infura have a free tier?
Yes — the Core plan is free, with 1 API key, 3,000,000 credits per day and 500 credits per second.
Does Infura support Bittensor?
On the pages we read: Not listed on its pricing page. Iteradian serves Bittensor’s native Subtensor JSON-RPC on every plan, alongside the other networks in its 12-network catalogue.
When should I choose Infura over Iteradian?
You want a free tier today, very high burst throughput, or your organization already standardizes on Consensys tooling such as MetaMask.