# 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-09-27T07:47:53.517Z
- Source commit: 1e4ede55e6791d8fcf18a257b901764ad8c5e386
- Statistics window: 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z (30 days)
- Statistics calculated at: 2026-09-19T00:53:31.999Z
- Telemetry state at build time: stale

**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.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; 10 RPC method calls/s; burst 50 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: 99.98%. Measured at 2026-09-19T00:53:31.999Z; rolling 30-day window 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z.
- p95 RPC latency: 971.793 ms. Measured at 2026-09-19T00:53:31.999Z; rolling 30-day window 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z.
- RPC error rate: 0.028% after platform retries and routing. Measured at 2026-09-19T00:53:31.999Z; rolling 30-day window 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z.
- Requests completed after retry: 3,619,954. Measured at 2026-09-19T00:53:31.999Z; rolling 30-day window 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z.
- Median agent reaction time: <1s across 408 sampled incidents. Measured at 2026-09-19T00:53:31.999Z; rolling 30-day window 2026-08-20T00:53:31.999Z to 2026-09-19T00:53:31.999Z.

**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, arc for Arc-specific methods, and txpool for read-only pending-pool queries on paid Arc Mainnet (which can be incomplete without trusted peers). 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; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/1.
- BNB Smart Chain — mainnet, chain ID 56, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/56.
- Avalanche C-Chain — mainnet, chain ID 43114, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Base — mainnet, chain ID 8453, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/8453.
- Arbitrum One — mainnet, chain ID 42161, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/42161.
- Optimism — mainnet, chain ID 10, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/10.
- Robinhood Chain — mainnet, chain ID 4663, L2, live; node service classes: archive; method families: standard, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/4663.
- Arc Mainnet — mainnet, chain ID 5042, L1, live; node service classes: archive; method families: standard, trace, debug, arc, txpool; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/5042.
- Polygon PoS — mainnet, chain ID 137, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/137.
- Sonic — mainnet, chain ID 146, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Fantom Opera — mainnet, chain ID 250, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- HyperEVM — mainnet, chain ID 999, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- Plasma — mainnet, chain ID 9745, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- ZKsync Era — mainnet, chain ID 324, L2, live; node service classes: archive; method families: standard, debug; WebSocket unavailable.
- Linea — mainnet, chain ID 59144, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Scroll — mainnet, chain ID 534352, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Gnosis — mainnet, chain ID 100, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Celo — mainnet, chain ID 42220, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Blast — mainnet, chain ID 81457, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Mantle — mainnet, chain ID 5000, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Manta Pacific — mainnet, chain ID 169, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Boba Network — mainnet, chain ID 288, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Berachain — mainnet, chain ID 80094, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Chiliz — mainnet, chain ID 88888, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Ink — mainnet, chain ID 57073, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- IoTeX — mainnet, chain ID 4689, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Lisk — mainnet, chain ID 1135, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- MegaETH — mainnet, chain ID 4326, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Monad — mainnet, chain ID 143, L1, live; node service classes: full; method families: standard; WebSocket unavailable.
- opBNB — mainnet, chain ID 204, L2, live; node service classes: full; method families: standard; WebSocket unavailable.
- Immutable zkEVM — mainnet, chain ID 13371, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- PulseChain — mainnet, chain ID 369, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Ronin — mainnet, chain ID 2020, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Cronos — mainnet, chain ID 25, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/25.
- Stable — mainnet, chain ID 988, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Tempo — mainnet, chain ID 4217, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Unichain — mainnet, chain ID 130, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/130.
- Viction — mainnet, chain ID 88, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- World Chain — mainnet, chain ID 480, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/480.
- XDC Network — mainnet, chain ID 50, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- ZetaChain — mainnet, chain ID 7000, L1, live; node service classes: full; method families: standard; WebSocket unavailable.
- Zora — mainnet, chain ID 7777777, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Flow EVM — mainnet, chain ID 747, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Ethereum Sepolia — testnet, chain ID 11155111, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Base Sepolia — testnet, chain ID 84532, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Arbitrum Sepolia — testnet, chain ID 421614, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Arc Testnet — testnet, chain ID 5042002, L1, live; node service classes: archive; method families: standard, trace, debug, arc, txpool; WebSocket available for eligible paid accounts: newHeads. URL: wss://rpc.solidrpc.io/ws/{api_key}/evm/5042002.
- Optimism Sepolia — testnet, chain ID 11155420, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Polygon Amoy — testnet, chain ID 80002, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- BNB Smart Chain Testnet — testnet, chain ID 97, L1, live; node service classes: full; method families: standard; WebSocket unavailable.
- Gnosis Chiado — testnet, chain ID 10200, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Berachain Bepolia — testnet, chain ID 80069, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Chiliz Spicy — testnet, chain ID 88882, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Flow EVM Testnet — testnet, chain ID 545, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Lisk Sepolia — testnet, chain ID 4202, L2, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Mantle Sepolia — testnet, chain ID 5003, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Monad Testnet — testnet, chain ID 10143, L1, live; node service classes: full; method families: standard; WebSocket unavailable.
- opBNB Testnet — testnet, chain ID 5611, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- PulseChain Testnet v4 — testnet, chain ID 943, L1, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Ronin Saigon — testnet, chain ID 202601, L1, live; node service classes: full, archive; method families: standard, trace, debug; WebSocket unavailable.
- Unichain Sepolia — testnet, chain ID 1301, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Zora Sepolia — testnet, chain ID 999999999, L2, live; node service classes: full, archive; method families: standard, debug; WebSocket unavailable.
- Avalanche Fuji C-Chain — testnet, chain ID 43113, L1, live; node service classes: archive; method families: standard, debug; WebSocket unavailable.
- Ethereum Hoodi — testnet, chain ID 560048, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- HyperEVM Testnet — testnet, chain ID 998, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- Plasma Testnet — testnet, chain ID 9746, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- Robinhood Testnet — testnet, chain ID 46630, L2, live; node service classes: archive; method families: standard, debug; WebSocket unavailable.
- Sonic Testnet — testnet, chain ID 14601, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- Tempo Moderato — testnet, chain ID 42431, L1, live; node service classes: archive; method families: standard, trace, debug; WebSocket unavailable.
- ZKsync Sepolia — testnet, chain ID 300, L2, live; node service classes: archive; method families: standard, debug; WebSocket unavailable.

## 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.
- [Referral program](https://solidrpc.io/docs/referrals): Earn 10% of a referred account's payments as account credit for twelve months.
- [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.

## Guides and comparisons

- [All SolidRPC guides](https://solidrpc.io/blog): Provider comparisons, pricing analysis, migration guidance, and production EVM RPC operations.
- [SolidRPC plans are changing on 28 October. Keep today’s pricing and limits.](https://solidrpc.io/blog/plan-changes-october-2026): SolidRPC plans change on 28 October 2026. Active customers keep their pricing and limits. Activate before the change to secure today’s terms.
- [Arc Mainnet RPC is live on SolidRPC](https://solidrpc.io/blog/arc-mainnet-rpc-solidrpc): Connect to Arc Mainnet through SolidRPC. Get the chain ID, a first JSON-RPC call, USDC gas and indexing notes, and the checks to run before production traffic.
- [latest vs safe vs finalized: choosing an EVM RPC block tag](https://solidrpc.io/blog/evm-rpc-block-tags-latest-safe-finalized): Choose latest, safe, finalized, pending, a block number, or a block hash for EVM RPC reads, indexers, simulations, caching, and failover.
- [Block receipts vs transaction receipts for EVM indexers](https://solidrpc.io/blog/eth-getblockreceipts-vs-transaction-receipts): Choose block or transaction receipt RPC for an EVM indexer, verify complete results, handle reorgs, and qualify historical receipt access before backfilling.
- [eth_call vs debug_traceCall vs eth_simulateV1](https://solidrpc.io/blog/eth-call-vs-debug-tracecall-vs-eth-simulatev1): Choose the right EVM transaction simulation method, block context, overrides, validation, and production test plan for calls, traces, and sequences.
- [Building on Robinhood Chain? Make SolidRPC Your First Integration.](https://solidrpc.io/blog/robinhood-chain-solidrpc-first-integration): Build on Robinhood Chain with SolidRPC: one managed RPC integration, historical data, transaction debugging, and straightforward usage pricing. Start free.
- [Best Binance RPC providers in 2026 (BNB Smart Chain)](https://solidrpc.io/blog/best-binance-rpc-providers-2026): Compare the best Binance and BNB Smart Chain RPC providers in 2026 by archive depth, logs, trace/debug support, WebSocket, pricing model, and failover.
- [Best Robinhood Chain RPC providers in 2026](https://solidrpc.io/blog/best-robinhood-chain-rpc-providers-2026): Compare SolidRPC, Blockmachine, Alchemy, QuickNode, dRPC, and public Robinhood Chain RPC by price, archive depth, methods, transport, and operational fit.
- [Best Polygon RPC providers in 2026](https://solidrpc.io/blog/best-polygon-rpc-providers-2026): Compare SolidRPC, Blockmachine, dRPC, Alchemy, QuickNode, and third-party Polygon public RPCs by cost, archive depth, methods, transport, and failover.
- [Cheapest EVM RPC providers in 2026: compare by workload](https://solidrpc.io/blog/cheapest-evm-rpc-providers-2026): Compare cheap EVM RPC providers by real method mix, archive and trace needs, failed-request billing, and cost per finished workload.
- [EVM JSON-RPC batching: when it helps and when it hurts](https://solidrpc.io/blog/evm-json-rpc-batching-guide): Use EVM JSON-RPC batches safely with unique IDs, block pinning, partial-error handling, bounded retries, provider-limit tests, and real benchmarks.
- [Ethereum WebSocket vs HTTP polling for event indexing](https://solidrpc.io/blog/ethereum-websocket-vs-http-polling): Choose WebSocket subscriptions or HTTP polling for EVM event indexing, with durable cursors, reconnect recovery, reorg handling, and cost tests.
- [debug_traceTransaction vs trace_transaction: which trace API should you use?](https://solidrpc.io/blog/debug-tracetransaction-vs-trace-transaction): Choose between debug_traceTransaction and trace_transaction by output, client support, history, indexing needs, portability, and failure behavior.
- [How to backfill EVM logs without gaps or duplicates](https://solidrpc.io/blog/eth-getlogs-backfill-without-gaps): Build a reliable eth_getLogs backfill with adaptive block ranges, durable cursors, idempotent writes, reorg handling, retries, and completeness checks.
- [Do you need an archive node for EVM RPC?](https://solidrpc.io/blog/do-you-need-archive-node-evm-rpc): Learn which EVM RPC methods need historical state, why logs and traces are different, and how to test archive access before choosing a node or provider.
- [Arc Testnet RPC: public endpoint and developer guide](https://solidrpc.io/blog/arc-testnet-rpc-solidrpc): Connect to Arc Testnet with SolidRPC's free public RPC. Get chain ID 5042002, USDC gas details, curl setup, limits, archive access, and a test checklist.
- [Alchemy alternatives for archive RPC](https://solidrpc.io/blog/alchemy-alternatives-archive-rpc): Looking for an Alchemy alternative for archive RPC? Compare archive access, eth_getLogs, trace/debug support, rate limits, pricing predictability, and managed node operations.
- [QuickNode alternatives for high-volume RPC](https://solidrpc.io/blog/quicknode-alternatives-high-volume-rpc): Compare QuickNode alternatives for high-volume RPC workloads. Learn what to evaluate for archive reads, eth_getLogs, trace/debug, pricing predictability, and managed operations.
- [Best RPC provider for indexers](https://solidrpc.io/blog/best-rpc-provider-for-indexers): Choosing the best RPC provider for indexers? Compare archive access, eth_getLogs performance, trace/debug support, retries, cost predictability, and failover.
- [How much does archive RPC cost?](https://solidrpc.io/blog/how-much-does-archive-rpc-cost): Archive RPC cost depends on method mix, chain, volume, traces, logs, and retries. Learn how to estimate spend and when free archive RPC is enough.
- [`eth_getLogs` performance comparison](https://solidrpc.io/blog/eth-getlogs-performance-comparison): Learn how to compare eth_getLogs performance across RPC providers using realistic block ranges, topic filters, latency, errors, rate limits, and cost.
- [`debug_traceTransaction` RPC provider comparison](https://solidrpc.io/blog/debug-tracetransaction-rpc-provider-comparison): Compare RPC providers for debug_traceTransaction workloads. Learn how trace/debug calls affect performance, cost, archive access, and reliability.
- [BSC RPC provider for high-volume workloads](https://solidrpc.io/blog/bsc-rpc-provider-high-volume-workloads): Choosing a shared or dedicated BSC RPC provider? Compare archive access, logs, traces, throughput, failover, pricing, and managed node operations.
- [Polygon RPC nodes: archive, full, and dedicated options](https://solidrpc.io/blog/polygon-archive-node-rpc-provider): Compare Polygon archive, full, shared, and dedicated RPC options by historical depth, logs, debug methods, capacity, failover, and operational ownership.
- [RPC 429 errors: causes and fixes](https://solidrpc.io/blog/rpc-429-errors-causes-fixes): Fix RPC 429 errors with backoff, pacing, and capacity checks. See which application controls remain when SolidRPC owns upstream routing and failover.
- [How to reduce Alchemy CU usage](https://solidrpc.io/blog/how-to-reduce-alchemy-cu-usage): Learn practical ways to reduce Alchemy compute unit usage by optimizing eth_getLogs, retries, caching, backfills, batching, and provider strategy.
- [Self-hosted nodes vs RPC provider cost comparison](https://solidrpc.io/blog/self-hosted-nodes-vs-rpc-provider-cost-comparison): Compare self-hosted blockchain nodes vs RPC providers across hardware, storage, snapshots, monitoring, upgrades, incidents, archive access, and engineering time.
- [EVM RPC failover: how to prevent stale or inconsistent data](https://solidrpc.io/blog/evm-rpc-failover-stale-inconsistent-data): Keep EVM RPC failover fresh and consistent. Learn what SolidRPC operates behind one integration and what your application still owns.

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