Skip to main content
Use this page to size a workload against the limits shown for the pass or rental your application uses. The standard tiers are Flash, Classic, Elite, and Prime; limits can also be customized for a specific access.
Prices, locations, and limits can change. Read them from the dashboard for the access you will use; do not copy values from a screenshot or another access.

​
Check capacity for a workload

1

Select the pass or rental

Choose the exact active access your application will use. Do not assume two accesses with the same tier label have identical current configuration.
2

Choose a product and location

Open Endpoints for the selected access and choose from the products and locations shown there.
3

Read activity and published capacity

Open Usage for current activity and Limits for the values shown for the selected access.
4

Test the intended configuration

Obtain the target and credential after selecting the access, network, and location, then run one low-impact operation.
Run a low-impact test, then keep the workload within the limits shown in the dashboard.

​
Understand the monthly and live limits

ThorEdge RPC has no monthly request cap. Throughput and concurrency limits still apply. Live constraints still apply: The dashboard can show additional product-specific constraints. Read Usage and Limits for the selected access instead of encoding a tier table into application logic. RPC rate and subscription caps apply per active location token where the published table says so. Creating extra clients, credentials, reconnect loops, or location targets does not increase the entitlement attached to an access.

​
Check the selected access

Products, locations, and capacity vary by pass or rental. Use the options and limits shown for the selected access; RPC access does not automatically include every streaming or transaction-routing product.

​
Operate below the live limits

  • Leave headroom for bursts and retries instead of targeting the displayed ceiling.
  • Bound concurrency and use exponential backoff with jitter for retryable throttling.
  • Reuse WebSocket and streaming connections where the protocol permits.
  • Keep Yellowstone filters narrow and close streams that are no longer needed.
  • Review Usage and Limits after releases or material traffic changes.
  • Contact ThorNode support before a traffic increase needs more capacity.
For a 429, rejected subscription, or other capacity symptom, use the limit troubleshooting table.

​
Next steps