Tools
Polygon RPC pricing calculator
Estimate your monthly Polygon RPC volume, peak RPS, trace usage, and the BlazingNode plan or add-ons that fit your workload.
Last updated: July 8, 2026.
Who this page is for
- Users comparing Builder, Operator, Pro, and Business
- Teams confused by RPS versus monthly request volume
- Buyers considering add-ons instead of permanent upgrades
- Visitors coming from comparison pages and fix guides
Calculator
Estimate your workload
All BlazingNode paid plans include dedicated state-pinned WebSocket connections for real-time `newHeads`, `logs`, and pending mempool streams.
Recommended BlazingNode plan
Operator
99 USDC / month • 45M requests • 300 RPS peak (75 RPS sustained) • 50K traces • 8 WSS sockets
- Operator covers your peak RPS requirement with an unthrottled 300 RPS baseline (75 RPS sustained).
- Operator includes 45,000,000 monthly requests, which fits your estimated volume.
- Operator includes 50,000 trace/debug calls.
- Operator includes 8 WebSocket connections for real-time mempool and block subscriptions.
Your estimated workload
Monthly requests
45,000,000
Average sustained RPS
17.4
Peak burst RPS
300
Trace calls
50,000
Modular Headroom Strategy
Add-on & Upgrade Recommendations
Recommended Path:
Keep your recommended plan baseline. If volume overflows during an occasional backfill or market volatility, modular 20M packs (39 USDC) bridge the gap without forcing a higher tier.
Spike & Trace Planning:
Your trace/debug usage is close to the included allowance. If trace volume grows faster than normal requests, plan for trace bundles or the next tier.
Workload Sizing Architecture: Sustained RPS vs Monthly Volume
A common misconception in blockchain infrastructure is sizing solely by headline RPS. When your bots run continuously 24/7, even modest sustained RPS consumes significant volume on a monthly basis:
10 RPS sustained (24/7)
25.9M requests
Builder covers ~8 days
25 RPS sustained (24/7)
64.8M requests
Fits Builder tier (20M)
75 RPS sustained (24/7)
194.4M requests
Fits Operator tier (45M)
150 RPS sustained (24/7)
388.8M requests
Fits Pro tier (90M)
💡 Key Principle: If your bots fire only during specific arbitrage blocks, your sustained RPS will be low while peak RPS is high (ideal for Builder or Operator with 300 RPS burst). If your service polls every block round-the-clock, select your tier based on total monthly volume.
Compare pricing models
How to estimate monthly RPC requests
Start with average RPS, then multiply across a 30-day month. Sustained traffic adds up quickly. A workload that feels small by peak RPS can still consume tens of millions of requests.
How to estimate trace and debug volume
Separate occasional debugging from recurring operational use. Bots, incident response flows, and indexer investigations can make trace usage grow much faster than normal reads.
When extra 20M request packs make sense
Use extra volume (20M requests for 39 USDC) for temporary backfills, seasonal traffic, one-time migrations, or uneven months. It is a bridge, not the default answer for a recurring workload.
When upgrading makes more sense
Upgrade when the same extra volume keeps returning every month, when trace demand grows alongside requests, or when higher peak RPS becomes permanent.
When a burst pass makes sense
Use burst for a game event, mint, claim window, campaign push, or trading spike. Burst is not a replacement for monthly volume.
Explore pricing & modular add-ons
Related links
FAQ
How many monthly requests is 30 RPS?
Thirty sustained requests per second for a 30-day month is about 77.76M requests. That is why peak RPS and monthly volume should be evaluated separately.
What is the difference between RPS and monthly requests?
RPS is the peak rate your endpoint must handle at a moment in time. Monthly requests describe the total workload runway across the billing period.
Should I buy extra request packs or upgrade?
Use extra packs for temporary backfills or uneven months. Upgrade when the same extra volume repeats every month or when trace and RPS needs grow together.
How are trace calls counted?
Treat traces as a separate planning dimension. Paid plans include trace allowances, and trace-heavy workloads may need a higher plan or trace bundles.
What if my traffic spikes temporarily?
That is usually a burst question, not a monthly volume question. A +100 RPS 72h Burst Pass ($30 USDC) can make more sense than a permanent upgrade when the spike is temporary.
Can I test before paying?
Yes. Use the calculator to estimate fit, then validate the recommendation with a 72-hour mainnet trial before changing your main provider path.