Managed EVM JSON-RPC service for production teams.
One RPC integration. No provider stack to manage.
Use one hosted HTTPS endpoint across supported EVM networks. SolidRPC operates upstream diversity, routing, failover, monitoring, and recovery behind it.
10K responses/day. No card required.
Trusted by
https://rpc.solidrpc.io/YOUR_API_KEY/evm/1- Your code
- One endpoint shape
- SolidRPC
- Routing, retry, and failover
- Operations
- Monitoring and recovery
Upstream incidents stay behind the endpoint.
Everything included
Get the whole RPC stack. Manage none of it.
Managed nodes, familiar provider capacity, automatic routing, and SLA credits, included.
Your managed RPC stack
Included
- SolidRPC managed nodes
- Included
- Third-party RPC providers you already use, but cheaper
- Included
- Automatic routing to the best qualified upstream
- Included
- Automatic SLA credits
- Included
SLA credits apply to eligible plans and covered networks.
Fleet evidence
Operational data, with its state attached.
Delayed snapshot · Sep 19, 2026, 00:53 UTC
Rolling 30 days · Aug 20, 2026 – Sep 19, 2026 UTC
| Metric | Value | Source context |
|---|---|---|
| Fleet gateway availability | 99.98% | Prometheus gateway probes · not contractual |
| RPC error rate | 0.028% | After platform retries and routing |
| Requests completed after retry | 3.6M | Succeeded on attempt two or later |
| Median agent reaction time | <1s | Alert received to work start |
Retries and route changes remain behind the SolidRPC endpoint.
Read the measurement methodologyNetwork coverage
One endpoint shape across supported EVM networks.
Use the same endpoint shape across supported mainnets and testnets. Open a network for its chain-specific methods, archive coverage, tracing, and operational details.
Chain ID 42161
Chain ID 5042
Chain ID 43114
- BaseL2
Chain ID 8453
Chain ID 80094
- BlastL2
Chain ID 81457
Chain ID 56
Chain ID 288
- CeloL2
Chain ID 42220
- ChilizL1
Chain ID 88888
- CronosL1
Chain ID 25
- EthereumL1
Chain ID 1
Chain ID 250
- Flow EVML1
Chain ID 747
- GnosisL1
Chain ID 100
- HyperEVML1
Chain ID 999
Chain ID 13371
- InkL2
Chain ID 57073
- IoTeXL1
Chain ID 4689
- LineaL2
Chain ID 59144
- LiskL2
Chain ID 1135
Chain ID 169
- MantleL2
Chain ID 5000
- MegaETHL2
Chain ID 4326
- MonadL1
Chain ID 143
- opBNBL2
Chain ID 204
- OptimismL2
Chain ID 10
- PlasmaL1
Chain ID 9745
Chain ID 137
Chain ID 369
Chain ID 4663
- RoninL1
Chain ID 2020
- ScrollL2
Chain ID 534352
- SonicL1
Chain ID 146
- StableL1
Chain ID 988
- TempoL1
Chain ID 4217
- UnichainL2
Chain ID 130
- VictionL1
Chain ID 88
Chain ID 480
Chain ID 50
Chain ID 7000
Chain ID 324
- ZoraL2
Chain ID 7777777
Pricing
One service and one billing model.
Each billable JSON-RPC method call consumes one response unit. Standard, archive, trace, and debug requests use the same unit where the method is supported.
On activated WebSocket networks for eligible paid accounts, each written head uses one existing response unit, shared with HTTP/WS calls and account limits. Live delivery requires reconnect and reconciliation after a gap. All WS traffic is excluded from monetary SLA credits. Check WebSocket availability.
| Plan | Free $0 forever Evaluate one managed endpoint with real traffic. | Builder $25 / month For prototypes and production pilots. | SolidRecommended $349 / month For production teams replacing several RPC providers. | Rocksolid $999 / month For high-volume traffic across networks. |
|---|---|---|---|---|
| Included responses | 10K responses / day | 10M / month | 150M / month | 600M / month |
| Request rate | 10 RPC method calls/s · burst 50 calls | 120 calls/s · burst 600 | 600 calls/s · burst 3,000 | 6,000 calls/s · burst 30,000 |
| API keys | 1 API key | 10 | 25 | 100 |
| Support | Self-serve docs | Email support | Email support | Live support |
| Managed routing | Included | Included | Included | Included |
| WebSocket | HTTPS only | HTTPS and WS on selected networks | HTTPS and WS on selected networks | HTTPS and WS on selected networks |
| SLA coverage | No monetary SLA | No monetary SLA | 1–5 selected networks · automatic invoice credits | Up to 15 selected networks · automatic invoice credits |
Enterprise
Dedicated capacity, security review support, and a migration plan for retiring provider endpoints and customer-managed routing.
Migration
Replace endpoint sprawl in a reviewable code change.
Inspect the current provider setup, redirect compatible requests, run the project’s tests, and review the diff before deployment.
- const rpcUrls = [primary, fallbackA, fallbackB]
+ const rpcUrl = process.env.SOLIDRPC_URLHow do I migrate to SolidRPC?
Open the migration page, install the skill for Codex or Claude Code, and run the provided prompt. Your coding agent inspects your project, updates compatible RPC traffic, and tests the change.
Migrate to SolidRPCIs SolidRPC another fallback provider?
No. SolidRPC replaces the customer-managed provider pool for supported traffic. Upstream selection, failover, monitoring, and recovery are part of the service.
Will migration change production automatically?
No. The migration workflow updates and tests a local project. Your team reviews the diff, keeps secrets out of prompts, and chooses when to deploy.
What about WebSockets and provider-specific APIs?
Migrate compatible HTTP JSON-RPC and check the WebSocket guide for activated networks for eligible paid accounts with native newHeads. Other subscription types and provider-specific APIs need explicit review. WebSocket delivery shares your response-unit ceiling and is live-only, with no monetary SLA credits.
Ready to test the endpoint?
Start with one API key. Keep the rollout decision in your hands.