Managed EVM JSON-RPC service for production teams.

One RPC integration. No provider stack to manage.

Your app gets fresh, correct blocks. You stay calm. We run the nodes, the failover, and the recovery. You keep one endpoint.

Get an API key Migrate to SolidRPC

10K responses/day. No card required.

Trusted by

nimimo

Our nodes serve first. Third-party RPC providers stand by behind the same endpoint.

Fleet evidence

Operational data, with its state attached.

Last verified · Nov 4, 2026, 00:47 UTC

Rolling 30 days · Oct 5, 2026 – Nov 4, 2026 UTC

Fleet gateway availability: 100%; Prometheus gateway probes
RPC error rate: 0.019%; After platform retries and routing
Requests completed after retry: 16.7M; 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 methodology

How it works

Infrastructure we run, not a relay we rent.

SolidRPC runs its own blockchain nodes and uses them first when they can serve your request. Additional RPC providers add resilience, capacity, and coverage behind the same endpoint. We own upstream diversity, routing, failover, monitoring, and recovery.

01
We operate our own capacity.
Our nodes serve first wherever they can. Additional RPC providers cover the rest behind the same endpoint.
02
We check every path before it serves.
Chain, method, block range, freshness, and health. A path that fails a check is not used.
03
We own monitoring and recovery.
Traffic moves off an unsuitable path and returns once it is eligible again. Your endpoint never changes.

Fleet metrics reflect observed platform performance. SLA credits apply to eligible plans and covered networks.

How routing and failover work

Network coverage

41 mainnets. 26 testnets. One endpoint shape.

Use the same endpoint shape across supported mainnets and testnets. Open a network for its chain-specific methods, archive coverage, tracing, and operational details.

20 of 67 shown

Live catalog response · 41 mainnets · 26 testnetsView the full network catalog

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.

SolidRPC plan comparison
Plan	Free $0 forever Evaluate one managed endpoint with real traffic.	Builder $35 / 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.	EnterpriseContractual Custom by agreement Dedicated capacity, security review support, and a migration plan for retiring provider endpoints and customer-managed routing.
Included responses	10K responses / day	10M / month	120M / month	400M / month	Custom
Request rate	10 RPC method calls/s · burst 50 calls	120 calls/s · burst 600	500 calls/s · burst 2,500	4,000 calls/s · burst 20,000	Custom
API keys	1 API key	10	25	100	Custom
Support	Self-serve docs	Email support	Email support	Live support	Direct engineering contact
Managed routing	Included	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	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	Contractual terms in your agreement
Security review	Published practices	Published practices	Published practices	Published practices	Security review on request
Plan action	Start free	Choose Builder	Choose Solid	Choose Rocksolid	Talk to an engineer

Get an API key Estimate your RPC costs

Read contractual SLA coverage

Accountability

A company stands behind the endpoint.

Company
SolidRPC, Inc. A Delaware corporation, run by its founders.
About us
Operations
Gateways across multiple regions and datacenters, health-checked and restarted automatically.
How we handle failures
Security
Vulnerability reports answered within 2 business days.
Security practices
Procurement
Security questionnaires and a buyer review pack.
Request a review

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_URL

Review the migration workflow

How 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 SolidRPC

Is 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.

Does SolidRPC also manage gateway availability?

Yes. SolidRPC operates multiple gateway instances, checks their health, and automatically restarts unhealthy instances. SolidRPC runs gateway infrastructure across multiple regions and datacenters, providing redundancy behind one endpoint. We manage gateway operations alongside upstream diversity, routing, failover, monitoring, and recovery, so your team keeps one RPC integration.

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.

Get an API key