Pricing
One number matters: response units per billing window. Supported networks, archive access, and tracing are included on every plan.
How billing works
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.
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.
Plans
| Plan | Price | Response units | Rate limit | Burst capacity | API keys | Support | SLA |
|---|---|---|---|---|---|---|---|
| Free | $0 | 10K/day | 2 RPC method calls/s | 10 calls | 1 | — | No monetary SLA |
| Builder | $25/mo | 10M/mo | 120 RPC method calls/s | 600 calls | 10 | Email (~30 min replies) | No monetary SLA |
| Solid | $349/mo | 150M/mo | 600 RPC method calls/s | 3,000 calls | 25 | Email (~30 min replies) | 99.9% · 1–5 selected |
| Rocksolid | $999/mo | 600M/mo | 6,000 RPC method calls/s | 30,000 calls | 100 | Live chat (instant) | 99.9% · 1–15 selected |
| Enterprise | Custom | Custom | Custom | Custom | Custom | Live chat (instant) | Custom allowance and SLA configuration |
Solid is the plan most production teams land on.
Solid and Rocksolid include automatic next-invoice credits under Covered Request Availability.
What counts toward quota
- Each billable JSON-RPC method call consumes 1 response unit, including every call inside a batch.
- A method that reaches the nodes counts even if it returns a JSON-RPC error, a revert or a bad parameter still did the work.
- Gateway rejections are never billed: 401, 402, 403, 429, and blocked methods cost nothing. See the error reference.
- Upstream HTTP 5xx failures and timeouts are not billed. They remain visible in error-rate and latency analytics.
Quota response headers
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| Header | Meaning |
|---|---|
X-Quota-Limit | Included response units |
X-Quota-Used | Billable response units used |
X-Quota-Remaining | Included response units left |
X-Quota-Reset | Seconds until reset |
X-Quota-Window | day or 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.
When you hit your quota
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
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.
| Plan | Overage rate |
|---|---|
| Builder | ≈ $2.50 per 1M response units |
| Solid | ≈ $2.33 per 1M response units |
| Rocksolid | ≈ $1.67 per 1M response units |
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.
Enterprise
Custom quotas, dedicated infrastructure, and a custom SLA. Contact us and tell us about your workload.
Is there a free plan?
Yes. Every account starts on Free: $0, 10K/day, 2 RPC method calls/s with burst capacity 10, and 1 API key. Supported network and method coverage is shared with the catalog above. Upgrade for larger quotas, higher limits, support, and any overage option listed for the selected paid plan.