Pricing
Simple Polygon RPC pricing with clear limits
Clear USDC plans for builders, bots, and production workloads that need predictable Polygon access.
Transparent usage expectations. No credit cards. Request a free 3-day trial when your workflow is ready.
Workload selector
Pick the pain stage that sounds most like your workflow
Best fit if your workflow relies on predictable execution and cannot tolerate random shared-RPC instability.
Free Trial
for 3 days
Best for
Evaluation and first testing
Evaluate the endpoint before committing.
- HTTP endpoint - full Polygon mainnet access
- 1 API key
- 5 RPS / 100,000 total requests across 3 days
- Automated onboarding: working API key in under 60 seconds
- RPC Checker and docs access included
- No WebSocket, no add-ons, no extensions during trial
- Support: documentation only
Prove the endpoint works for your workload before you pay anything.
Builder
per month
Best for
Builders fixing unstable public RPC behavior
Fix the instability. Stop debugging your infrastructure.
- 15 RPS
- 3 million requests / month
- Dedicated HTTP endpoint - your requests don't share capacity with anyone else
- 2 API keys
- Basic burst tolerance - traffic spikes from other users won't affect you
- No shared throttling - 429s from the public pool are no longer your problem
- No WebSocket (available as a paid add-on)
- Support: AI support agent + email queue (48-hour response target)
This tier removes public RPC instability. It is a fix tier, not a production-critical tier - serious operators typically move to Operator.
Operator
per month
Best for
Bots, active apps, and serious daily usage
Run your system reliably. This is the plan most serious operators stay on.
- 30 RPS
- 8 million requests / month
- Dedicated HTTP endpoint with higher burst tolerance
- 3 API keys
- Lower latency variance under active and bursty load
- Priority request handling
- 10% discount on one add-on product (Gas Oracle, Webhook Alerts, or WebSocket)
- Support: AI support agent + email queue (24-hour response target)
The commercial center of BlazingNode. Built for bots, active apps, and operators who need consistent execution - not just more headroom.
Pro
per month
Best for
Sustained automation and heavier workloads
For workloads where instability has a measurable cost.
- 60 RPS
- 20 million requests / month
- Dedicated HTTP endpoint with stronger sustained-load handling
- 6 API keys
- Higher routing priority
- Faster recovery under pressure
- 15% discount on up to two add-on products
- Monthly async architecture review: submit a structured request, receive a written response within 48 hours - no calls
- Support: priority support queue
Choose Pro when your system is production-sensitive, not just active. The architecture review is included - use it.
Enterprise
per month
Best for
Production-critical Polygon infrastructure
When failure has a real business cost.
- 100+ RPS
- 50+ million requests / month
- Dedicated HTTP endpoint, highest handling priority
- 10+ API keys
- Custom request limits on request
- SLA-ready positioning - formal SLA available when operationally confirmed
- 20% discount on full add-on catalog
- Support: structured escalation path - AI agent first, priority written escalation second
- Paid architecture sessions available separately ($79 / 30-minute async written review)
- No direct calls. No on-demand founder access.
For production-critical infrastructure. Support is structured and bounded - not unlimited access.
What changes as you move up
Higher plans are not just “more requests.” They are designed for workflows with higher sensitivity to instability, burst behavior, and operational risk.
Lower tiers
Light evaluation and lighter usage where occasional instability is less costly and the main goal is proving whether dedicated access changes the workflow.
Builder tier
Good when public RPC starts wasting development time and you need a cleaner, more reliable first paid step.
Operator tier
Better fit when workflows actively depend on predictable execution, steadier latest-block access, and less variance under daily load.
Pro / Enterprise
Built for systems that must stay consistent under heavier load, stronger contention, or higher operational risk.
The higher tiers are meant to reflect higher burst tolerance, better consistency under load, stronger request-handling priority during contention, and better suitability for sustained request flow. They are not promises of magical speed or outcome.
No compute units
No compute units. Clear usage expectations.
Many RPC providers use abstract “compute units” or more complex usage formulas that can make pricing harder to follow.
BlazingNode uses:
- clear monthly request limits
- clear RPS limits
- clear plan progression
You know what you are buying, when you need to upgrade, and why.
Decision guide
When should you actually pay for Polygon RPC?
Free / public RPC is usually fine if:
- you are learning
- you are testing simple scripts
- your workload is low-frequency
- occasional instability does not matter
A paid plan becomes rational when:
- requests fail randomly
- latency starts varying too much
- bots or apps behave unpredictably
- rate limits begin to appear
- debugging time increases because infrastructure quality is unclear
Final step
Validate fit before you commit
Start with a free 3-day trial, compare the behavior against your current setup, and upgrade only when the difference is real.