Head to head
Iteradian vs Ankr
Iteradian and Ankr both run managed RPC. Ankr bills in API credits, priced per request by chain family; 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
Ankr
- Bills in
- API credits, priced per request by chain family
- Entry paid plan
- Pay-as-you-go — prepaid, from a $10 deposit
- Free option
- Yes — Freemium with 200M API credits a month, at about 1,800 requests per minute.
- Bittensor
- Not listed on its chain list
Every Ankr figure on this page was read from www.ankr.com/docs/rpc-service/service-plans/ on . Providers change pricing without notice — check the source before deciding. Ankr is a trademark of its owner; Iteradian is not affiliated with Ankr.
Why teams pick Iteradian over Ankr
No balance to babysit
A plan, not a prepaid wallet. Nothing suspends at −$5; the allowance resets with the billing period.
Bittensor native
Subtensor mainnet over its own Substrate JSON-RPC, next to your EVM networks. Ankr does not list Bittensor.
Every network, every plan
The entry plan reaches the whole network catalogue. No network is held back for a higher tier.
Side by side
| Feature | Iteradian | Ankr |
|---|---|---|
| Billing unit | Requests — one call is one request | API credits, priced per request by chain family |
| Heavy methods cost more? | No — every call counts as one request | No — every call costs the same |
| Entry paid plan | Developer RPC: $39/month for 25,000,000 requests | Pay-as-you-go — prepaid, from a $10 deposit · Up to ≈1,500 requests/second per endpoint |
| Free option | Free | Yes — Freemium with 200M API credits a month, at about 1,800 requests per minute. |
| Past the allowance | $0.005 per 1,000 requests, capped at $150 per period, then HTTP 429 | Pay-as-you-go draws down a prepaid balance with no auto top-up; the account is suspended when it passes −$5. Enterprise usage above the committed volume is billed at contract rates. |
| Bittensor | Native Subtensor JSON-RPC, every plan | Not listed on its chain list |
| Networks | 12 in the catalogue, all on every plan | Ankr states 80+ chains on Premium (75+ on its chain list) |
| Per-key controls | IP allowlist (up to 50), allowed networks, rate limit and expiry on every key | IP, domain and contract whitelists |
| Failover | Health-checked; a failed read tries up to 3 nodes | Not stated on the pages we read |
How the bill is built
How Ankr bills
Ankr sells API credits at $0.10 per 1M and charges each request a fixed number of them by chain family: 200 credits for an EVM request, 500 for Solana, 700 for the Beacon Chain. It is effectively a per-request price that depends on the chain, not the method.
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 | — | — |
Ankr
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Freemium | $0/mo | 200M API credits per month | ≈1,800 requests/minute |
| Premium (pay-as-you-go) | $0.10 per 1M API credits, $10 minimum deposit | Prepaid balance | Up to ≈1,500 requests/second per endpoint |
| Deal | $500–$3,000/mo | +20% extra API credits | Up to ≈1,500 requests/second per endpoint |
| Enterprise | Custom | Committed volume | Custom; 99.9% uptime SLA |
Where each one is strong
What Ankr does well
- A clear per-request rate, split by chain family.
- High throughput at a low entry price: about 1,500 requests per second on pay-as-you-go.
- 75+ chains, and gRPC alongside RPC and REST.
- A 99.9% uptime SLA with service credits on Enterprise.
Where Iteradian differs
- Ankr’s paid tier is a prepaid balance that scales with traffic. Iteradian charges a fixed monthly plan price with capped overage.
- Iteradian serves Bittensor, which Ankr’s chain list does not include.
- Iteradian includes every supported network on every paid plan; Ankr’s free tiers cover a subset of chains.
Choose Ankr when…
You need 75+ chains, the lowest published per-request rate, gRPC, very spiky traffic that suits pure pay-as-you-go, or an uptime SLA with service credits.
Choose Iteradian when…
You want a predictable monthly bill instead of a prepaid balance, you need Bittensor, or you want per-key IP allowlists and network lists on an entry plan.
Start the trialQuestions people ask
Is Iteradian cheaper than Ankr?
It depends on your method mix, because the two meter differently. Ankr bills in API credits, priced per request by chain family, 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 Ankr have a free tier?
Yes — Freemium with 200M API credits a month, at about 1,800 requests per minute.
Does Ankr support Bittensor?
On the pages we read: Not listed on its chain list. Iteradian serves Bittensor’s native Subtensor JSON-RPC on every plan, alongside the other networks in its 12-network catalogue.
When should I choose Ankr over Iteradian?
You need 75+ chains, the lowest published per-request rate, gRPC, very spiky traffic that suits pure pay-as-you-go, or an uptime SLA with service credits.