Pricing

Every billable method call costs exactly 1 response unit, eth_blockNumber costs the same as debug_traceTransaction on an archive node. No compute units, no method multipliers, no archive surcharge.

On activated WebSocket networks, each native head notification written to a paid-plan or PAYG connection also costs 1 response unit. HTTP calls, WS calls and pushed heads share the same allowance, rate and burst limits. Subscribe/unsubscribe acknowledgments and connection controls are free. There is no separate WebSocket price. Free/public access remains HTTPS-only. All WS traffic is outside monetary SLA credits. See WebSocket availability and recovery.

Quota windows, limits, and current prices come from the live plan catalog below. Supported networks, full and archive routes, and listed trace/debug methods use the same response-unit model.

Solid is the plan most production teams land on.

Solid and Rocksolid include automatic next-invoice credits under Covered Request Availability.

Authenticated responses include a live quota snapshot. Reset is a number of seconds, not a timestamp:

X-Quota-Limit: 10000000
X-Quota-Used: 420001
X-Quota-Remaining: 9579999
X-Quota-Reset: 1555200
X-Quota-Window: month

During overage, used continues above the included limit while remaining stays at zero. An upstream 5xx is refunded and does not increase these billable totals.

Further RPC calls are blocked at the response-unit quota unless overage billing is enabled. Blocked calls get HTTP 402 with your usage in the body:

{
  "error": "Monthly response quota exceeded",
  "used": 10000000,
  "limit": 10000000,
  "message": "You have used all responses included in your plan. Upgrade to continue."
}

Upgrade, enable overage where the active plan permits it, or wait for the reset reported in the response headers. A 402 is not retryable. Back off until that reset.

Overage billing is opt-in, per account, on the Billing page in the dashboard. It requires an eligible active subscription. While enabled, traffic beyond the included quota continues to be served instead of returning 402.

Extra response units are billed at your plan's effective rate: plan price divided by plan quota.

How it is invoiced:

• Each time your unbilled overage reaches one full plan capacity, one full plan price is invoiced immediately and auto-charged.
• The remainder is settled as a separate one-off invoice when your billing period rolls over. Remainders under $0.50 are written off.
• Overage invoices are always separate one-off Stripe invoices, never absorbed into your renewal.
• If an overage charge fails, overage billing is automatically disabled, further RPC calls are blocked at the plan limit again (402), and you get an email.

PAYG is a standalone billing mode you can enable from authenticated Billing without buying a fixed plan. It has no request quota. The default PAYG rate is $3.00 per 1M billable JSON-RPC method calls, an account-wide sustained limit of 300 response units/s with burst capacity 1,500, 5 API keys, email support, and no monetary SLA. Account-specific pricing and limits shown in Billing control when they differ from these defaults.

An approved price change applies to calls authorized after the change. Earlier calls keep the price captured when they were authorized. This lets a billing period contain usage at more than one price without repricing calls that already happened.

Enabling PAYG opens Stripe Checkout in card setup mode. You must accept the displayed PAYG terms and expressly authorize SolidRPC to save the card and charge it off session in USD. PAYG activates only after a signed Stripe webhook confirms the SetupIntent succeeded and the consented card was saved. Returning to the dashboard is not proof of activation. Prices are before tax.

Automatic collection works as follows:

• The first threshold is $5 of new unpaid usage. After each successful threshold payment, the next threshold is $10, $20, $40, $80, then $160 maximum.
• The next threshold persists across periods and later re-enrollment, advances only after payment, and can be disabled for mid-cycle collection without resetting the ladder.
• At the end of the UTC activation-anniversary period, or when PAYG is disabled, closed after a payment failure, or switched to a paid plan, SolidRPC subtracts prior threshold charges and invoices every positive remainder. The final invoice is at least $1. Zero remaining usage creates no final invoice.
• A failed threshold or final collection immediately removes PAYG access and returns the account to its effective fallback. Stripe retries continue, while PAYG and paid-plan overage remain blocked until all PAYG debt is paid or an administrator records a separate audited waiver. Late payment restores eligibility but never silently reactivates PAYG.

Disabling PAYG switches new traffic immediately. Final settlement waits until in-flight calls finish and metering is reconciled. If you buy a paid plan, PAYG remains active while Checkout is pending, abandoned, or failed. Only a confirmed paid initial plan invoice activates that plan and closes PAYG. Any final PAYG invoice is separate, and plan overage starts disabled but eligible.

What gets billed? One valid proxied JSON-RPC method call is one unit, including each method in a batch. Gateway rejections (including 402 and 429), malformed or blocked calls, gateway 5xx, and upstream 5xx are not billed. Proxied HTTP 200–499 responses, including node-returned JSON-RPC errors, are billed.

Can I request more throughput? File an email-support ticket with recent traffic, peak calls/s, expected growth, and 429 evidence. Support escalates the evidence for review. An increase is not guaranteed.

Can I update my card? Use Replace PAYG card in authenticated Billing. Stripe setup designates the replacement card under your existing PAYG authorization. Your existing card remains in use until a signed succeeded SetupIntent swaps it. The general Stripe portal does not select a PAYG card, and SolidRPC never falls back to an arbitrary attached card.

If SolidRPC gives you a promo code, redeem it in the Promo credit box on the Billing page. The amount is added to your account as prepaid credit and applied automatically to your next invoices: a plan purchase, plan renewals, pay as you go threshold and final invoices, and overage. You do not choose which invoice it covers, and the credit never expires.

Credit does not replace a payment method. Enabling pay as you go or buying a plan still requires a card in Stripe Checkout; the card is charged only for whatever the credit does not cover. Each code can be redeemed once per account, some codes carry a redeem-by date, and credit cannot be converted to cash or moved between accounts.