Comparisons
Same traffic. Different bill.Pick the one you can predict.
Iteradian is a managed RPC gateway with native Bittensor support, request-based billing and a hard ceiling on overage. Here is how that stacks up against Alchemy, Infura, QuickNode, Ankr and dRPC — every competitor figure read from its own pages and linked, including the places where they are ahead.
- request, whatever the method
- 1 call = 1
- most overage can add on Developer RPC
- $150
- nodes tried before a read fails
- 3
What one call actually costs you
Most providers price calls in weighted units, so the same traffic costs more when it leans on heavy methods. Iteradian counts requests.
eth_blockNumbereth_getBalanceeth_calleth_getLogsdebug_traceTransaction- Iteradianrequests
Every call counts as one request
- Alchemycompute units
Weighted by method: cost follows a multiplier table
- Infuracredits per day
Weighted by method: cost follows a multiplier table
- QuickNodeAPI credits
Weighted by method: cost follows a multiplier table
- AnkrAPI credits
Flat per call, priced by chain family
- dRPCrequests (flat CU)
Flat per call, priced per request
Four things you get on the entry plan
None of these are enterprise add-ons. They are how the gateway works for every organization.
Subtensor
native Bittensor JSON-RPC
Bittensor next to your EVM chains
Subtensor mainnet over the Substrate JSON-RPC the Bittensor SDK, miners and validators speak — on the same key, dashboard and bill as Ethereum or Base. None of the five providers here list native Subtensor RPC.
How it works1 = 1
call to request
A bill that follows your traffic
A block number and a log range cost the same. Past the allowance, overage is billed per 1,000 requests up to a cap printed on the pricing page; past the cap the gateway answers 429 instead of invoicing more.
How it works50
IP ranges per key
Controls on every key
Each API key carries its own IP allowlist, allowed networks, rate limit and expiry. Create as many keys as you have services — no plan caps the count.
How it works3
nodes tried per read
Failover you don’t configure
Nodes are health-checked, and a failed read moves to the next healthy node automatically. Transaction submissions go to one node and are never replayed, so a retry can never double-send.
How it works
Tick what you need. See who fits.
Scored from each provider’s own documentation. If someone else fits your list better, it says so — we would rather lose a deal than a customer.
Who fits
- 01IteradianStrong fit6 / 6
- Native Bittensor (Subtensor) RPC: YesNative Subtensor JSON-RPC, every plan
- Billed per request, not weighted units: YesOne call is one request
- Fixed monthly price with a spend cap: YesFixed plan price; overage stops at a cap
- 02dRPCPartial fit4 / 6
- Native Bittensor (Subtensor) RPC: PartlyBittensor EVM only, paid tier
- Billed per request, not weighted units: YesFlat 20 CU per method
- Fixed monthly price with a spend cap: PartlyPrepaid balance, no monthly plan
- 03AnkrWeak fit2 / 6
- Native Bittensor (Subtensor) RPC: Not listedNot on its chain list
- Billed per request, not weighted units: PartlyPer request, priced by chain family
- Fixed monthly price with a spend cap: PartlyPrepaid balance; Deal subscriptions
- 04AlchemyWeak fit1 / 6
- Native Bittensor (Subtensor) RPC: Not listedNot on its supported-chains list
- Billed per request, not weighted units: NoCompute units, weighted by method
- Fixed monthly price with a spend cap: PartlyUsage-based; you can set a usage limit
- 05InfuraWeak fit1 / 6
- Native Bittensor (Subtensor) RPC: Not listedNot on its pricing page
- Billed per request, not weighted units: NoCredits, capped per day
- Fixed monthly price with a spend cap: PartlyFixed tiers with a daily credit cap
- 06QuickNodeWeak fit1 / 6
- Native Bittensor (Subtensor) RPC: Not listedNot on its chains page
- Billed per request, not weighted units: NoAPI credits, weighted by method
- Fixed monthly price with a spend cap: PartlyFixed tiers; overage billed, no cap stated
Pick your matchup
Each page puts both price lists side by side, with the sources and the date they were read.
- Bills in
- compute units (CU)
- Entry
- Pay as You Go — $0.525 per 1M CU, no monthly fee
- Bittensor
- Not listed on its supported-chains page
- Bills in
- credits, with daily and per-second caps
- Entry
- Developer — $50/month, 15M credits per day
- Bittensor
- Not listed on its pricing page
- Bills in
- API credits
- Entry
- Build — $49/month, 80M API credits
- Bittensor
- Not listed on its chains page
- Bills in
- API credits, priced per request by chain family
- Entry
- Pay-as-you-go — prepaid, from a $10 deposit
- Bittensor
- Not listed on its chain list
- Bills in
- compute units, sold per million requests
- Entry
- Growth — pay-as-you-go, $6 per 1M requests
- Bittensor
- Bittensor EVM (chain 964) on the paid tier; native Subtensor RPC not documented
Where the others are ahead
Better you hear it here than after a migration. If one of these is a must-have today, one of the providers above is the better call.
A focused catalogue
12 networks in the catalogue, against 100+ at the largest providers. We add chains when we can run them properly.
SLA on Dedicated only
No uptime percentage is published for shared plans. Dedicated contracts carry agreed SLA terms.
Move one workload this week.
Start the 7-day trial with no card, point one service at the gateway, and read the bill line by line. If it doesn’t beat what you pay now, you have lost an afternoon.
Competitor figures are read from each provider’s own pricing pages and documentation; every matchup page links its sources and the date they were read. Product names and trademarks belong to their owners. Iteradian is not affiliated with any provider listed.