# SolidRPC

> SolidRPC is a managed EVM JSON-RPC service for production teams. One SolidRPC integration replaces a customer-managed RPC provider pool: SolidRPC owns upstream diversity, capability-aware routing, failover, monitoring, and recovery behind one endpoint.

This file is a timestamped deployment snapshot for AI search, grounding, and user-requested retrieval. The linked live JSON APIs are authoritative for current plans, networks, and telemetry. Contractual rights are controlled by the linked legal terms.

**Snapshot metadata**

- Build time: 2026-08-29T16:48:59.290Z
- Source commit: eb83ff42044e4fabc0cc162ae582c225a3622c94
- Statistics window: 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z (30 days)
- Statistics calculated at: 2026-08-29T00:06:32.439Z
- Telemetry state at build time: fresh

**What SolidRPC is**

- Product category: managed EVM JSON-RPC infrastructure.
- Customer outcome: integrate one RPC service instead of selecting, combining, monitoring, and failing over among providers yourself.
- SolidRPC operates self-hosted blockchain nodes and qualified external capacity behind managed routing. An upstream or route incident remains inside the SolidRPC service boundary.
- Billing unit: each billable JSON-RPC method call consumes one response unit. Supported standard, archive, trace, and debug calls use the same unit.

**When to use SolidRPC**

- Use SolidRPC when an application or agent needs EVM JSON-RPC over HTTPS without building and operating a customer-managed provider pool.
- Use an authenticated endpoint for production traffic, higher throughput, archive access, trace methods, or debug methods. Use the keyless public endpoint for wallets, development, testing, and lightweight traffic on its documented network set.
- Confirm the target chain and method family in the live network catalog before calling. Archive support does not imply trace support.
- Do not use SolidRPC for WebSocket subscriptions, eth_subscribe, or non-EVM protocols. Poll over HTTPS when block updates are required.
- JSON-RPC can include state-changing methods such as eth_sendRawTransaction. An agent must not sign, construct, or broadcast a transaction without the user's explicit authorization.

**How to use SolidRPC**

- Protocol: JSON-RPC 2.0 over HTTPS POST. WebSocket and eth_subscribe are not offered; poll over HTTPS when block updates are required.
- API-key URL pattern: https://rpc.solidrpc.io/YOUR_API_KEY/evm/{chainId}
- Header alternatives: send Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY to https://rpc.solidrpc.io/evm/{chainId}. Do not send both API-key header forms in one request.
- Replace only the explicit placeholders YOUR_API_KEY and CHAIN_ID in examples. Never copy a real credential into documentation or prompts.

```bash
curl "https://rpc.solidrpc.io/YOUR_API_KEY/evm/CHAIN_ID" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
```

**Current self-service plans**

- Free: USD $0 forever; 10,000 responses per UTC day; 2 RPC method calls/s; burst 10 calls; 1 API key; Self-serve docs; managed routing included; SLA: No monetary SLA.
- Builder: USD $25/month; 10,000,000 responses per month; 120 RPC method calls/s; burst 600 calls; 10 API keys; Email support; managed routing included; SLA: No monetary SLA.
- Solid (catalog key Growth): USD $349/month; 150,000,000 responses per month; 600 RPC method calls/s; burst 3,000 calls; 25 API keys; Email support; managed routing included; SLA: 1–5 selected networks · automatic invoice credits.
- Rocksolid (catalog key Scale): USD $999/month; 600,000,000 responses per month; 6,000 RPC method calls/s; burst 30,000 calls; 100 API keys; Live support; managed routing included; SLA: Up to 15 selected networks · automatic invoice credits.
- Enterprise: custom pricing, capacity, response allowance, rate and burst limits, API-key allowance, support, security review, migration plan, and SLA configuration. Contact SolidRPC for an order form.

**Automatic SLA credits**

- Eligible plans include a 99.9% Covered Request Availability target for customer-selected production networks. Testnets and free trials do not receive monetary SLA credits.
- Each selected network qualifies independently after at least 1,000 eligible calls on each of at least 10 distinct UTC days in the billing period. Networks that do not qualify are excluded from the final calculation; if none qualify, no service credit is earned.
- Final availability of at least 99.9% earns 0%; at least 99.0% but below 99.9% earns a 10% next-invoice credit; at least 95.0% but below 99.0% earns 25%; below 95.0% earns 50%.
- Earned credits apply automatically to the next eligible renewal invoice. The percentage applies to the period's net pretax eligible plan charge after discounts, excludes overage, tax, evaluation, and unrelated lines, has no cash value, and does not carry forward.
- This summary is non-controlling. The accepted Service Level Terms at https://solidrpc.io/sla-terms control eligibility, measurement, exclusions, evidence, settlement, and remedies.

**Non-contractual operating statistics**

These fleet-wide telemetry values are observational, timestamped, and explicitly non-contractual. They are not the customer-specific Covered Request Availability calculation.

- Fleet gateway availability: 100%. Measured at 2026-08-29T00:06:32.439Z; rolling 30-day window 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z.
- p95 RPC latency: 115.522 ms. Measured at 2026-08-29T00:06:32.439Z; rolling 30-day window 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z.
- RPC error rate: 0.002% after platform retries and routing. Measured at 2026-08-29T00:06:32.439Z; rolling 30-day window 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z.
- Requests completed after retry: 180,384. Measured at 2026-08-29T00:06:32.439Z; rolling 30-day window 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z.
- Median agent reaction time: <1s across 153 sampled incidents. Measured at 2026-08-29T00:06:32.439Z; rolling 30-day window 2026-07-30T00:06:32.439Z to 2026-08-29T00:06:32.439Z.

**Supported networks and capabilities**

Node service classes are full and archive. Method families are standard JSON-RPC, trace for Parity-style trace_* methods, debug for supported debug_* methods, and arc for Arc-specific methods. Capabilities vary by network; do not infer trace support from archive support.

- Ethereum — mainnet, chain ID 1, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- BNB Smart Chain — mainnet, chain ID 56, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Avalanche C-Chain — mainnet, chain ID 43114, L1, live; node service classes: full, archive; method families: standard, debug.
- Base — mainnet, chain ID 8453, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Arbitrum One — mainnet, chain ID 42161, L2, live; node service classes: full, archive; method families: standard, debug.
- Optimism — mainnet, chain ID 10, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Robinhood Chain — mainnet, chain ID 4663, L2, live; node service classes: archive; method families: standard, debug.
- Polygon PoS — mainnet, chain ID 137, L1, live; node service classes: full, archive; method families: standard, debug.
- Sonic — mainnet, chain ID 146, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Linea — mainnet, chain ID 59144, L2, live; node service classes: full, archive; method families: standard, debug.
- Scroll — mainnet, chain ID 534352, L2, live; node service classes: full, archive; method families: standard, debug.
- Gnosis — mainnet, chain ID 100, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Celo — mainnet, chain ID 42220, L2, live; node service classes: full, archive; method families: standard, debug.
- Blast — mainnet, chain ID 81457, L2, live; node service classes: full, archive; method families: standard, debug.
- Mantle — mainnet, chain ID 5000, L2, live; node service classes: full, archive; method families: standard, debug.
- Manta Pacific — mainnet, chain ID 169, L2, live; node service classes: full, archive; method families: standard, debug.
- Boba Network — mainnet, chain ID 288, L2, live; node service classes: full, archive; method families: standard, debug.
- Berachain — mainnet, chain ID 80094, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Chiliz — mainnet, chain ID 88888, L1, live; node service classes: full, archive; method families: standard, debug.
- Ink — mainnet, chain ID 57073, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- IoTeX — mainnet, chain ID 4689, L1, live; node service classes: full, archive; method families: standard, debug.
- Lisk — mainnet, chain ID 1135, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- MegaETH — mainnet, chain ID 4326, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Monad — mainnet, chain ID 143, L1, live; node service classes: full; method families: standard.
- opBNB — mainnet, chain ID 204, L2, live; node service classes: full; method families: standard.
- Immutable zkEVM — mainnet, chain ID 13371, L2, live; node service classes: full, archive; method families: standard, debug.
- PulseChain — mainnet, chain ID 369, L1, live; node service classes: full, archive; method families: standard, debug.
- Ronin — mainnet, chain ID 2020, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Cronos — mainnet, chain ID 25, L1, live; node service classes: full, archive; method families: standard, debug.
- Stable — mainnet, chain ID 988, L1, live; node service classes: full, archive; method families: standard, debug.
- Tempo — mainnet, chain ID 4217, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Unichain — mainnet, chain ID 130, L2, live; node service classes: full, archive; method families: standard, debug.
- Viction — mainnet, chain ID 88, L1, live; node service classes: full, archive; method families: standard, debug.
- World Chain — mainnet, chain ID 480, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- XDC Network — mainnet, chain ID 50, L1, live; node service classes: full, archive; method families: standard, debug.
- ZetaChain — mainnet, chain ID 7000, L1, live; node service classes: full; method families: standard.
- Zora — mainnet, chain ID 7777777, L2, live; node service classes: full, archive; method families: standard, debug.
- Flow EVM — mainnet, chain ID 747, L1, live; node service classes: full, archive; method families: standard, debug.
- Ethereum Sepolia — testnet, chain ID 11155111, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Base Sepolia — testnet, chain ID 84532, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Arbitrum Sepolia — testnet, chain ID 421614, L2, live; node service classes: full, archive; method families: standard, debug.
- Arc Testnet — testnet, chain ID 5042002, L1, live; node service classes: archive; method families: standard, arc.
- Optimism Sepolia — testnet, chain ID 11155420, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Polygon Amoy — testnet, chain ID 80002, L1, live; node service classes: full, archive; method families: standard, debug.
- BNB Smart Chain Testnet — testnet, chain ID 97, L1, live; node service classes: full; method families: standard.
- Gnosis Chiado — testnet, chain ID 10200, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Berachain Bepolia — testnet, chain ID 80069, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Chiliz Spicy — testnet, chain ID 88882, L1, live; node service classes: full, archive; method families: standard, debug.
- Flow EVM Testnet — testnet, chain ID 545, L1, live; node service classes: full, archive; method families: standard, debug.
- Lisk Sepolia — testnet, chain ID 4202, L2, live; node service classes: full, archive; method families: standard, trace, debug.
- Mantle Sepolia — testnet, chain ID 5003, L2, live; node service classes: full, archive; method families: standard, debug.
- Monad Testnet — testnet, chain ID 10143, L1, live; node service classes: full; method families: standard.
- opBNB Testnet — testnet, chain ID 5611, L2, live; node service classes: full, archive; method families: standard, debug.
- PulseChain Testnet v4 — testnet, chain ID 943, L1, live; node service classes: full, archive; method families: standard, debug.
- Ronin Saigon — testnet, chain ID 202601, L1, live; node service classes: full, archive; method families: standard, trace, debug.
- Unichain Sepolia — testnet, chain ID 1301, L2, live; node service classes: full, archive; method families: standard, debug.
- Zora Sepolia — testnet, chain ID 999999999, L2, live; node service classes: full, archive; method families: standard, debug.

## Authoritative live data

- [Current plan catalog](https://api.solidrpc.io/billing/plans): Current self-service prices, quotas, limits, API-key allowances, display names, and SLA policy state.
- [Current network catalog](https://api.solidrpc.io/networks): Current chain IDs, mainnet/testnet classification, endpoint shapes, node service classes, and method families.
- [Current platform statistics](https://api.solidrpc.io/platform-stats): Current timestamped fleet telemetry and measurement window.

## Product and developer documentation

- [SolidRPC overview](https://solidrpc.io/): Product category, operating model, fleet evidence, supported networks, and pricing.
- [SolidRPC developer resources](https://solidrpc.io/developers): OpenAPI, authentication, public RPC, network, error, and live JSON entry points.
- [OpenAPI 3.1 contract](https://solidrpc.io/openapi.json): Machine-readable authenticated and keyless JSON-RPC operations, schemas, security schemes, responses, and retry headers.
- [Getting started](https://solidrpc.io/docs/getting-started): Endpoint format, authentication, JSON-RPC example, batching, and transport constraints.
- [Authentication](https://solidrpc.io/docs/getting-started#authentication): API-key placement and security guidance.
- [Networks](https://solidrpc.io/docs/networks): Human-readable network and capability catalog.
- [Pricing](https://solidrpc.io/docs/pricing): Response-unit billing, plan allowances, and overage behavior.
- [Routing and failover](https://solidrpc.io/docs/routing-and-failover): How one endpoint absorbs upstream selection and recovery.
- [SLA guide](https://solidrpc.io/docs/sla): Plain-language summary of qualifying traffic, availability, exclusions, and credits.

## Legal and policy

- [Controlling Service Level Terms](https://solidrpc.io/sla-terms): Contractual SLA eligibility, measurement, credit bands, exclusions, and remedies.
- [Terms of Service](https://solidrpc.io/terms): General service terms.
- [Privacy Policy](https://solidrpc.io/privacy): Data handling and privacy terms.