Platform errors
Credits & usage
Each catalogued RPC method has a credit cost. Usage is recorded when the gateway accepts and accounts the call (after RPS allow). Credits are flushed to billing asynchronously. Importantly: the node gateway does not currently return a dedicated “credits exhausted” JSON-RPC / HTTP error when the included pool is used up.
Causes
- Confusion with other providers that hard-block when credits hit zero.
- Expecting HTTP 402/429 for overage when RpcNode instead tracks included vs overage in billing.
- High-credit methods (debug_trace*, large block payloads) draining the monthly pool quickly.
How to fix
- Monitor usage in the dashboard; prefer cheaper methods where possible (see Credits badges in docs).
- Upgrade the plan for a larger included credit pool and higher RPS.
- Do not treat credit balance as a realtime gate — design clients around RPS (-32005) and method availability (-32601) instead.
Notes
- Requests rejected for RPS or IP allowlist do not consume credits.
- Plan marketing: usage beyond included credits is not billed as overage on current plans — still watch the pool for capacity planning.
- Webhook deliveries spend the same credit pool as RPC (methods webhook:tx / webhook:block in usage). Address slots remain a hard plan cap. Block webhooks bill at that network’s full get-block rate.