Service level agreement
Solid and Rocksolid include a 99.9% Covered Request Availability target for selected by user networks and automatic next-invoice credits.
What BETA means
BETA refers to the automated request classifier used to decide whether each eligible call succeeded. It does not make the SLA or an earned service credit non-binding.
The classifier is intentionally conservative. When the response, method, upstream metadata, or live chain evidence does not clearly prove success, it may mark a request unsuccessful even though the customer received a usable successful response. During BETA, we review these cases and improve network-, method-, client-, and upstream-specific classification as we identify new response patterns.
Plans and selected networks
| Plan | Monetary SLA | Covered networks |
|---|---|---|
| Free | No monetary SLA | — |
| Builder | No monetary SLA | — |
| Solid | 99.9% Covered Request Availability | 1–5 selected networks |
| Rocksolid | 99.9% Covered Request Availability | 1–15 selected networks |
| Enterprise | Custom | Custom allowance and SLA configuration |
| Pay as you go | No monetary SLA | — |
Testnets and free trials are outside the monetary SLA. Your first accepted network selection starts after the agreement is recorded. Later changes to selected networks take effect at the next billing cycle. The current selection remains covered until then.
What the metric measures
Covered Request Availability begins when an eligible JSON-RPC call with an id reaches the SolidRPC gateway. Calls that never reach that boundary cannot enter the measurement. Notifications without an id are excluded because they have no response to measure.
Each selected network qualifies independently after at least 1,000 eligible calls on each of 10 distinct UTC days. Qualified networks are combined by eligible call count, networks that do not reach the threshold are excluded from the period’s final calculation.
Next invoice credit
| Final Covered Request Availability | NEXT INVOICE CREDIT |
|---|---|
| At least 99.9% | 0% |
| 99.0% to below 99.9% | 10% |
| 95.0% to below 99.0% | 25% |
| Below 95.0% | 50% |
The percentage applies to the period’s net pretax eligible plan charge after discounts, excluding overage, tax, evaluation, and unrelated lines. The credit applies automatically to the next eligible renewal, has no cash value, does not carry forward, and is the sole monetary remedy for missing the target.
Maintenance and network freshness
A maintenance or incident window recorded by an authorized SolidRPC operator can exclude failures only inside its recorded time, network, and service-class scope. It may be recorded before, during, or after the affected interval, including for a blockchain halt. Successful calls remain successes. Calls completed while the selected blockchain network head is stale are excluded from the calculation.
Caller errors and unavailable blocks
Excluded calls count toward neither availability nor traffic qualification. Examples include execution reverts, fee-cap and transaction-nonce rejections, and requests rejected by SolidRPC’s own getLogs range, address, or topic limits. A provider’s capacity or result-size limit on an otherwise eligible call remains a failure if SolidRPC cannot serve it.
A request above the highest reported execution head is excluded only when the complete routing evidence shows unavailable block data in every failed branch with no accompanying service fault. For a range, its upper block is checked; each failed subrequest of a split range must qualify independently. Missing data at or below a reported head, an unknown head, or incomplete evidence does not qualify for this exclusion. The same rule can apply during a blockchain halt before the head becomes stale.
Where to check coverage
The customer SLA dashboard shows the active selection, period reports, claims, and credits. This guide is a summary, the accepted Service Level Terms control.