RPC Pricing Index — monthly snapshot of public provider prices
Last updated:
The index — October 2026
One row per provider: its cheapest paid plan, the unit it bills in, what the price includes and the request rate it allows. Triport's row is ours and is marked as such.
2× burst buffer, included. Finite request-rate limits show sustained RPS and short burst capacity. A full buffer at 20 RPS can absorb up to 40 requests at once and refills at 20 requests per second. There is no quota on the number of bursts and no extra charge for them. Size ongoing traffic to sustained RPS. Categories with no per-category cap have no numeric burst ceiling. How burst capacity works.
| Provider | Entry paid plan | Price | Billing unit | Included volume | RPS at that price |
|---|---|---|---|---|---|
| Alchemy[1] | Pay As You Go[1] | Usage-based: $0.525 per 1M compute units[1] | Compute units — about 27 compute units per standard call (provider's average)[1] Alchemy's own average estimate of 27 compute units per request; real method weights vary. | None — pay per use[1] | 300 req/s[1] 10,000 CU/s, which Alchemy describes as starting from 300 requests/s. |
| Ankr[2] | Pay-as-you-go[2] | Usage-based: $0.10 per 1M API credits[2] | API credits — 200 per Ethereum call, 500 per Solana call[2] 200 API credits per EVM request, 500 per Solana request: the spread is the chain, not the method. | None — pay per use[2] | Ethereum 1,500 req/s · Solana 4,000 req/s[2] Up to about 1,500 requests/s on EVM chains and 4,000 on Solana; $10 minimum deposit. |
| Chainstack[3] | Growth[3] | $49/mo[3] | Request units — 1 request unit per standard call[3] 1 request unit per full-node request, 2 per archive-node request: the spread is the node type, not the method. | 20M request units / month[3] | 250 req/s[3] |
| Helius[4] | Developer[4] | $49/mo[4] | Credits — 1 per Solana call[5] 1 credit per standard RPC call; getProgramAccounts and DAS calls are 10, so costs here are a lower bound. | 10M credits / month[4] | Solana 50 req/s[4] 50 RPC requests/s; 5 sendTransaction/s, 10 DAS requests/s, 25 getProgramAccounts/s. |
| Infura[6] | Developer[6] | $50/mo[6] | Credits — 80 per Ethereum call, 160 per Solana call[7] 80 credits per basic Ethereum call (eth_call, eth_getBalance, eth_blockNumber), 160 per Solana request; heavier Ethereum methods cost more (eth_getLogs 255, trace_* 300). | 450M credits / month[6] | Ethereum 50 req/s · Solana 25 req/s[6] 4,000 credits/s: 50 basic Ethereum calls/s at 80 credits, 25 Solana requests/s at 160. |
| QuickNode[8] | Build[8] | $49/mo[8] | API credits — 20 per Ethereum call, 30 per Solana call[9] 20 API credits per standard EVM call and 30 per Solana call (the spread is the chain); trace and debug calls cost 2x, replay 4x. | 80M API credits / month[8] | 50 req/s[8] |
| Triton One[10] | Pay-As-You-Go (shared)[10] | Usage-based: $10.00 per 1M calls (Solana)[10] | Per call — no credit conversion[10] $10 per 1M standard calls plus $0.08 per GB of bandwidth; DAS calls are $50 per 1M. Bandwidth is not included in these figures. | None — pay per use[10] | Not published[10] |
| Triport (our plans)[11] | Basic[11] | $20/mo[11] | Flat monthly price — no credits or compute units[11] The limit is requests per second per method category and network. | No request allowance — limited by req/s[11] | Ethereum 20 RPS sustained · up to 40 burst · Solana 60 RPS sustained · up to 120 burst[11] Standard read calls, sustained RPS; short burst capacity is 2× these finite limits, included at no extra cost. The buffer refills at sustained RPS. Heavier method groups have their own lower limit. |
Effective price per 1M requests at sustained load
Each cell is the cheapest published plan whose request rate covers the load, run for a 30-day month (2,592,000 seconds): 25 req/s is 64.8M requests, 100 req/s is 259.2M. The monthly cost and its arithmetic are printed under the price. This is the same calculation as the cost tables on our Ethereum and Solana comparison pages. A whole month at a fixed rate is the worst case for metered plans and the best case for flat ones.
| Provider | Ethereum, 25 req/s sustained | Ethereum, 100 req/s sustained | Solana, 25 req/s sustained | Solana, 100 req/s sustained |
|---|---|---|---|---|
| Alchemy[1] | $14.18 per 1M[1] $919/mo on Pay As You Go: 64.8M requests × 27 compute units = 1,749.6M; 1,749.6M compute units × $0.525 per 1M | $14.18 per 1M[1] $3,674/mo on Pay As You Go: 259.2M requests × 27 compute units = 6,998.4M; 6,998.4M compute units × $0.525 per 1M | $14.18 per 1M[1] $919/mo on Pay As You Go: 64.8M requests × 27 compute units = 1,749.6M; 1,749.6M compute units × $0.525 per 1M | $14.18 per 1M[1] $3,674/mo on Pay As You Go: 259.2M requests × 27 compute units = 6,998.4M; 6,998.4M compute units × $0.525 per 1M |
| Ankr[2] | $20.00 per 1M[2] $1,296/mo on Pay-as-you-go: 64.8M requests × 200 API credits = 12,960M; 12,960M API credits × $0.1 per 1M | $20.00 per 1M[2] $5,184/mo on Pay-as-you-go: 259.2M requests × 200 API credits = 51,840M; 51,840M API credits × $0.1 per 1M | $50.00 per 1M[2] $3,240/mo on Pay-as-you-go: 64.8M requests × 500 API credits = 32,400M; 32,400M API credits × $0.1 per 1M | $50.00 per 1M[2] $12,960/mo on Pay-as-you-go: 259.2M requests × 500 API credits = 129,600M; 129,600M API credits × $0.1 per 1M |
| Chainstack[3] | $3.07 per 1M[3] $199/mo on Pro: 64.8M requests × 1 request unit = 64.8M; $199 (80M request units included) | $3.82 per 1M[3] $990/mo on Enterprise: 259.2M requests × 1 request unit = 259.2M; $990 (400M request units included) | $3.07 per 1M[3] $199/mo on Pro: 64.8M requests × 1 request unit = 64.8M; $199 (80M request units included) | $3.82 per 1M[3] $990/mo on Enterprise: 259.2M requests × 1 request unit = 259.2M; $990 (400M request units included) |
| Helius[4] | Not listed for Ethereum[12] | Not listed for Ethereum[12] | $4.98 per 1M[4] $323/mo on Developer: 64.8M requests × 1 credit = 64.8M; $49 + (64.8M − 10M) credits × $5 per 1M | $5.00 per 1M[4] $1,295/mo on Business: 259.2M requests × 1 credit = 259.2M; $499 + (259.2M − 100M) credits × $5 per 1M |
| Infura[6] | Not computable from published prices[7] | Not computable from published prices[7] | Not computable from published prices[7] | Not computable from published prices[7] |
| QuickNode[8] | $10.53 per 1M[8] $682/mo on Scale: 64.8M requests × 20 API credits = 1,296M; $499 + (1,296M − 950M) API credits × $0.53 per 1M | $9.03 per 1M[8] $2,341/mo on Business+ Tier 2: 259.2M requests × 20 API credits = 5,184M; $1,999 + (5,184M − 4,500M) API credits × $0.5 per 1M | $15.42 per 1M[8] $999/mo on Business: 64.8M requests × 30 API credits = 1,944M; $999 (2,000M API credits included) | $13.07 per 1M[8] $3,387/mo on Business+ Tier 3: 259.2M requests × 30 API credits = 7,776M; $2,999 + (7,776M − 7,000M) API credits × $0.5 per 1M |
| Triton One[10] | Not listed for Ethereum[10] | Not listed for Ethereum[10] | $10.00 per 1M[10] $648/mo on pay as you go: 64.8M calls × $10 per 1M | $10.00 per 1M[10] $2,592/mo on pay as you go: 259.2M calls × $10 per 1M |
| Triport (our plans)[11] | $3.84 per 1M[11] $249/mo flat on Pro (100 req/s Ethereum read limit): 64.8M requests | $0.96 per 1M[11] $249/mo flat on Pro (100 req/s Ethereum read limit): 259.2M requests | $0.31 per 1M[11] $20/mo flat on Basic (60 req/s Solana read limit): 64.8M requests | $0.96 per 1M[11] $249/mo flat on Pro (200 req/s Solana read limit): 259.2M requests |
Download the October 2026 index as CSV — every cell above, the numbers behind it, and each cell's source URL and verification date.
Flat-RPS products elsewhere
Some providers also sell a flat request-rate product: a fixed monthly price for a requests-per-second limit, with no units. These are add-ons or separate products rather than entry plans, so they are not in the index above. They are listed here only when the provider's own pricing page shows the tiers; an offer known only from third-party write-ups is left out. Per 1M requests assumes the full rate for a 30-day month.
| Offer | Rate | Monthly price | Per req/s per month | Per 1M at full use | Source |
|---|---|---|---|---|---|
| Chainstack Unlimited Node add-on | 25 req/s | $149 + $49 Growth = $198 | $7.92 | $3.06 | chainstack.com, read October 13, 2026 |
| Chainstack Unlimited Node add-on | 100 req/s | $649 + $49 Growth = $698 | $6.98 | $2.69 | chainstack.com, read October 13, 2026 |
| Chainstack Unlimited Node add-on | 250 req/s | $1,649 + $49 Growth = $1,698 | $6.79 | $2.62 | chainstack.com, read October 13, 2026 |
| Chainstack Unlimited Node add-on | 500 req/s | $3,199 + $49 Growth = $3,248 | $6.50 | $2.51 | chainstack.com, read October 13, 2026 |
| Tatum Dedicated API key plans | 10 req/s | $99 | $9.90 | $3.82 | tatum.io, read October 13, 2026 |
| Tatum Dedicated API key plans | 25 req/s | $249 | $9.96 | $3.84 | tatum.io, read October 13, 2026 |
| Tatum Dedicated API key plans | 50 req/s | $509 | $10.18 | $3.93 | tatum.io, read October 13, 2026 |
| Tatum Dedicated API key plans | 100 req/s | $1,049 | $10.49 | $4.05 | tatum.io, read October 13, 2026 |
Caveats as the pages state them: Chainstack Unlimited Node add-on: no per-request charge within the rate; the page does not say which chains it covers; Tatum Dedicated API key plans: they do not consume plan credits; the page does not say which chains they cover.
History
| Provider | September 2026 | October 2026 |
|---|---|---|
| Alchemy | Pay As You Go: Usage-based: $0.525 per 1M compute units | Pay As You Go: Usage-based: $0.525 per 1M compute units |
| Ankr | Pay-as-you-go: Usage-based: $0.10 per 1M API credits | Pay-as-you-go: Usage-based: $0.10 per 1M API credits |
| Chainstack | Growth: $49/mo | Growth: $49/mo |
| Helius | Developer: $49/mo | Developer: $49/mo |
| QuickNode | Build: $49/mo | Build: $49/mo |
| Triton One | Pay-As-You-Go (shared): Usage-based: $10.00 per 1M calls (Solana) | Pay-As-You-Go (shared): Usage-based: $10.00 per 1M calls (Solana) |
| Triport (our plans) | Basic: $20/mo | Basic: $20/mo |
| Infura | Not in the index | Developer: $50/mo |
Methodology
- What is compared. Each provider's entry paid plan: the cheapest fixed monthly subscription above $0, or its pay-as-you-go plan when it sells no subscription. Free tiers and trials are not paid plans and are left out.
- Units. Credits, compute units and request units turn one request into a number of units by a per-call weight; the plan includes a monthly number of units and charges past it. The billing-unit column gives each provider's own unit and its weight for a standard read call. A flat plan sells a requests-per-second limit instead and has no units. How the models differ is explained in RPC credits, compute units and flat pricing.
- Effective price. Requests per month = rate × 2,592,000. For a metered provider: units = requests × its per-call weight on that network; cost = the plan price plus its published overage rate for units past the allowance, on the cheapest plan whose request rate covers the load. For a flat plan: cost = the price of the cheapest plan whose limit covers the load. Effective price = cost ÷ requests in millions.
- Which providers. Only providers whose pricing page was re-read within 45 days of the snapshot date (October 13, 2026) and whose every cell has a source. The snapshot is regenerated from the same data as our comparison pages, and a test fails if the two disagree.
- Triport. Our row comes from our own plan configuration, the same figures as the Triport pricing page. Rows are alphabetical and Triport's is last; there is no ranking or score.
What the index does not compare
- Only standard read calls. On metered plans heavier methods — archive reads, getProgramAccounts, DAS — cost more units per call; on Triport's flat plans heavier method groups have their own, lower request-rate limit.
- Some weights are the provider's own average rather than a per-method rate, and some request-rate limits are stated in units per second rather than requests; the note under each cell says which.
- Bandwidth fees, add-ons (streaming, gRPC, dedicated nodes), annual-billing discounts and taxes are excluded.
- Rate limits are defined differently from one provider to the next, for example with or without a burst allowance. Triport's limits are per method category and per network.
- Networks other than Ethereum and Solana, and features such as archive depth or WebSocket access, are on the comparison pages instead.
- The index is about price only. It has no latency, uptime or other performance figures.
Not in this month's index
- Allnodes — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- Blockdaemon — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- Coinbase Developer Platform — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- Moralis — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- NOWNodes — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- OnFinality — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- PublicNode — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- Shyft — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
- Tatum — Pricing page not re-read for this snapshot; no sourced per-call weight to price sustained load.
Sources
- https://www.alchemy.com/pricing — read October 13, 2026
- https://www.ankr.com/docs/rpc-service/service-plans/ — read October 13, 2026
- https://chainstack.com/pricing/ — read October 13, 2026
- https://www.helius.dev/pricing — read October 13, 2026
- https://www.helius.dev/docs/billing/credits — read October 13, 2026
- https://www.infura.io/pricing — read October 13, 2026
- https://docs.infura.io/get-started/pricing/credit-cost/ — read October 13, 2026
- https://www.quicknode.com/pricing — read October 13, 2026
- https://www.quicknode.com/api-credits — read October 13, 2026
- https://triton.one/pricing — read October 13, 2026
- https://triport.io/pricing — read October 13, 2026
- https://www.helius.dev/ — read October 13, 2026
FAQ
- How often is the RPC Pricing Index updated?
- Monthly. Each month is saved as its own snapshot; this page shows the latest (October 2026) and adds a history table once there is more than one month.
- Where do the numbers come from?
- From each provider's own public pricing and documentation pages. Every cell links its source and the day it was read. Triport's row comes from our own plan configuration, the same figures as the Triport pricing page.
- Why are only some providers in the index?
- A provider is priced only when its pricing page was re-read within 45 days of the snapshot and it publishes the per-call weight needed to price sustained traffic. This month that is 7 providers; the others are listed on the page with the reason.
- How are the rows ordered?
- Alphabetically, with Triport's row last and labelled as ours. The index gives no score; the prices and their arithmetic are shown so you can compare them for your own traffic.
- Can I reuse the data?
- Yes. The CSV download carries every cell with its source URL and verification date, under the CC BY 4.0 licence: credit Triport's RPC Pricing Index and link this page.
- Why 25 and 100 requests per second?
- Two fixed loads make every row comparable on the same footing. The same arithmetic works at any rate: multiply the rate by 2,592,000 seconds for a month's requests, then apply the provider's per-call weight and price list.