Skip to main content
An organization’s plan defines which products and features it can use, which networks it can use them on, and its monthly usage limits. The Billing page lists all three. When an action needs something the plan doesn’t include, the dashboard shows an upgrade prompt and the API returns an error instead of running it. To add a feature, network, or capacity, contact our sales team.

​
Features not included in your plan

The dashboard marks a feature the plan doesn’t include in one of three ways:
  • A product page you can’t open, for example Node RPCs without Node RPC in the plan, shows what the product does and a contact button such as Contact us for Node RPC.
  • An option inside a form carries an Unlock access badge. In Create Virtual Environment, for example, Network mirror and Bridge show the badge when the plan doesn’t include them. Clicking the badge opens a dialog describing the feature, with Contact us to upgrade and Maybe later.
  • A create button for a resource whose count limit is reached, such as projects or Node RPCs, opens a dialog titled “To create more …, upgrade your plan” with the current limit.
Network mirror option with the Unlock access badge in Create Virtual Environment Upgrade dialog for Network Mirror opened from the Unlock access badge Over the API, a request for a feature the plan doesn’t include returns HTTP 403 with the quota_limit_reached error slug:
Some endpoints return a more specific message, such as “Your plan does not include API simulations. Upgrade your plan or contact support to run simulations via the API.” or “Your plan does not include bundle simulations. Upgrade your plan or contact support to run simulation bundles.”

​
Networks not included in your plan

Network pickers group networks into MY NETWORKS, the networks in the Network entitlements table, and ALL NETWORKS. A network outside the plan carries an Upgrade tag. Create new Node network picker with the Upgrade tag on a network outside the plan Selecting it opens a dialog titled “Network isn’t included in your plan”: “To add this network, your plan needs additional network access. Contact us to add it.” Contact us to upgrade starts the request; Maybe later closes the dialog without creating anything. When both the product and the network are missing, the dialog lists the two together, for example “To create a Node on Network, your plan needs:” followed by the add-on and the network access. Mainnet isn't included in your plan dialog The network check applies to creating Node RPCs, Virtual Environments (including forks and clones), alerts, Web3 Actions, wallets, contracts, and bundle simulations. Over the API, these requests return HTTP 403 with the insufficient_permissions slug and the message “Your account is not entitled to use the selected network.” Creating a Virtual Environment returns “Your account is not entitled to create virtual testnets on the selected network.” A network on a trial shows Trial and its expiry date in the Network entitlements table; after that date it’s treated like any other network outside the plan.

​
Usage limits

Monthly usage limits, per-second rate limits, and Virtual Environment write limits are separate from feature and network restrictions, and return their own errors. See Usage limits, rate limits, and write limits.

​
Member permissions are separate from the plan

Plan restrictions apply to the whole organization. What an individual member can do inside it, such as creating projects or managing billing, is set by their member permissions. A member without the required permission sees Limited Access instead of an upgrade prompt.