Compare
Free/shared vs authenticated managed Polygon RPC
Free and public Polygon RPC endpoints are useful for learning, prototypes, and occasional requests. Authenticated managed access adds account-specific authentication and published plan limits.
Current public plans do not include a dedicated Polygon node, reserved hardware, or an exclusive worker pool.
| Category | Free / shared access | Authenticated managed access |
|---|---|---|
| Best use case | Learning, simple scripts, low-frequency requests, and early prototyping. | Bots, apps, scrapers, and backend services that need authenticated access with published plan limits. |
| What you receive | Provider terms and limits vary by endpoint. | Plan-specific RPS, monthly request, trace, and API-key allowances. |
| How to choose | Keep using it while the workload and its limits fit. | Choose the lowest published plan that covers your workload; use listed add-ons when they fit. |
| Infrastructure model | Shared cloud pool and multi-tenant proxy access. | Managed BlazingNode infrastructure with account-specific authentication, quotas, and plan limits. |
Does each plan include a dedicated Polygon node?
No. Current plans use BlazingNode’s managed Polygon infrastructure with authenticated access and plan-specific RPS, monthly volume and trace allowances. Dedicated or reserved infrastructure is not currently included in these public plans.