Pay for the request you need.

A price before you pay.

The quote is fixed for that request. Routing, cache hits and internal retries do not increase it.

Standard callSupported chain information, blocks, transactions, receipts, current-state reads and signed transaction submission.

0.002 USDC

Historical state, logs and tracesSupported state reads at an explicit block number or hash, eth_getLogs and the listed debug and trace methods.

0.0025 USDC

Batches add the prices together. Ten standard calls cost 0.020 USDC. Ten historical, log or trace calls cost 0.025 USDC. A batch with ten of each costs 0.045 USDC. The full quote is charged, including calls that return an error.

Request a price by sending the exact call or batch without PAYMENT-SIGNATURE. HTTP 402 returns the total and payment instructions without executing the request. A payment with the wrong amount is rejected with the correct requirement.

These prices apply to this pay-per-request endpoint. Account plans and prepaid credit have their own pricing. The quote states the payable total and any required billing information before signing.

One call or a batch.

The initial supported RPC networks are Ethereum (1), Base (8453) and Arbitrum One (42161). The payment network is separate from the blockchain you read. Check the live quote before signing.

https://rpc.solidrpc.io/x402/evm/{chainId}

Current state

Supported balance, code, transaction-count, storage and bounded contract calls with latest, safe or finalized use the standard price.

Historical state

The same supported state methods with an explicit block number or EIP-1898 block hash use the historical-state price. Retrieving an old transaction, receipt or block is a standard read.

Request limits

One HTTP JSON-RPC call or a batch of up to 50 calls, each with a unique ID. Maximum request size is 128 KiB and combined response size is 4 MiB. Each call has a 30-second execution limit. Supported eth_call requests require a gas limit of at most 1,000,000.

Outside this release

Notifications, WebSockets, stateful filters, unsigned transaction submission and methods outside the published allowlist are rejected before payment. The capability response lists every supported method and parameter rule. These restrictions apply only to this payment preview. Regular RPC access has separate network capabilities and account requirements.

Logs require explicit numeric ranges of at most 2,000 blocks or one block hash. The supported debug methods require callTracer, with a timeout of at most 10 seconds. Parity trace methods are available on Ethereum only. trace_filter also requires a count of at most 1,000. Use the API reference for the complete parameter schemas.

Submit a transaction you signed locally.

Use eth_sendRawTransaction with a signed legacy, EIP-2930 or EIP-1559 transaction for the selected chain. SolidRPC confirms the USDC payment before broadcasting it. The 0.002 USDC RPC fee does not include blockchain gas or transaction value. A returned hash confirms submission, not mining or successful execution on-chain.

Ask for separate approval before submitting a blockchain transaction. A payment budget alone does not authorize it. Never change the signed bytes or create a replacement purchase to recover an uncertain submission.

How your client pays.

1. 01

   Read the quote

   Send a supported call or batch without a payment. The HTTP 402 response tells your client the exact price, payment network, token, recipient and expiry.

2. 02

   Approve and sign locally

   Your compatible client checks your spending limits and signs the request-bound payment. Your wallet private key stays on your machine.

3. 03

   Receive the result

   For a single read, SolidRPC saves the result before payment settles. Batches and signed transactions settle first, then execute. The response includes each result or error and a payment receipt.

Your agent can build the payment request from the API reference. Results are returned as soon as payment settlement succeeds, with no extra wait for blockchain finality.

Use a client that supports SolidRPC’s request-binding extension. It signs the nonce supplied by the quote and sends PAYMENT-SIGNATURE with X-SolidRPC-Quote. A generic x402 client that ignores this extension cannot complete the payment.

Keep signing in your local client. Never send your wallet private key to an MCP tool, an HTTP endpoint or an agent conversation. Local read-only mode must stay enabled until you authorize spending.

Use SolidRPC pay-per-request for my blockchain task.
Read https://rpc.solidrpc.io/x402/capabilities
and https://rpc.solidrpc.io/x402/openapi.json first.

Use a compatible client with SolidRPC request binding.
Ask me to approve the per-purchase and total USDC limits.
A batch is charged in full, including failed calls.
Ask separately before submitting a blockchain transaction.
Keep wallet signing local and save private retry state.
Check the quote's network, token, recipient and exact amount.
If a payment is pending, recover it before signing another.
Report the result, payment receipt and total spent.

A retry is not another purchase.

Save the original quote, signed payment and receipt information privately. If the response is interrupted, retry the same request with the same payment. A changed request with a used authorization is rejected.

• Payment pending: follow the receipt URL and keep the original quote. Do not sign another payment while settlement is uncertain.
• Payment complete: retrieve the original result for up to 24 hours. Retrying a latest read returns that saved snapshot.
• Single read failed: a failure before settlement is not charged. Inspect the error before trying again.
• Batch item failed: the full quoted batch remains charged. Each item returns its own result or error. The batch is not atomic and does not guarantee a shared block snapshot.
• Transaction submission uncertain: keep the same purchase and signed bytes. Recovery checks the transaction hash and may resend only that transaction. A definitively rejected single submission records a refund obligation for support review. It does not refund a failed item within a batch.

A successful payment does not grant account-management permissions. For reusable RPC keys, account usage and delegated billing control, follow the agent account setup guide.