solidrpc.io valid

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.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:19:13.462Z. Cached copy · Source on solidrpc.io

# 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-10-24T00:40:17.853Z
- Source commit: 68a92c11e9bc5ce2272b6867650391898fa9253c
- Statistics window: 2026-09-24T00:30:21.119Z to 2026-10-24T00:30:21.119Z (30 days)
- Statistics calculated at: 2026-10-24T00:30:21.119Z
- 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 or native head notification written over WebSocket consumes one response unit. Supported standard, archive, trace, and debug calls use the same unit. WebSocket controls and suppressed duplicates are free.

**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.
- WebSocket supports native newHeads and ordinary RPC only on activated, qualified networks for eligible paid accounts. Check websocket.availability, url and subscriptionTypes in /networks. Free/public, unsupported subscription types and non-EVM protocols are excluded.
- 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, plus WSS on activated networks for eligible paid accounts. WSS path: /ws/YOUR_API_KEY/evm/{chainId}. Each written head costs one response unit and shares HTTP/WS rate, burst and allowance. No durable replay. All WS traffic is outside monetary SLA credits. See /docs/websocket.
- 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
…

Machine-readable: GET /v1/resolve?q=solidrpc.io · GET /v1/domain/solidrpc.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for solidrpc.io:
1. POST https://agentwebmap.com/v1/sites/solidrpc.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://solidrpc.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/solidrpc.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/solidrpc.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.