Connect Ethereum, Base, and Arbitrum.

Set up one SolidRPC integration across Ethereum, Base, and Arbitrum One, verify chain IDs and current blocks, and preserve credentials for later sessions. This recipe reads blockchain data. It does not create an account, sign a transaction, or fund credit.

Give your agent the task.

Task prompt

Configure SolidRPC for Ethereum, Base, and Arbitrum One. Reuse my saved credentials if available. Otherwise check onboarding and obtain my approval before creating an account or spending. Verify eth_chainId and eth_blockNumber for each network, then save the connection settings privately.

New to SolidRPC? Follow agent account setup first. A small task may fit public RPC. Account delegation requires paid access, and this script expects a separate ak_ RPC key.

Check coverage and limits.

Required methods: eth_chainId, eth_blockNumber. Read the network catalog and rate limits before a large run. One billable method call uses one response unit. Retries and range splits add requests.

Verify the catalog entries for Ethereum (1), Base (8453), and Arbitrum One (42161). Use the RPC origin returned for your environment. A key can serve multiple networks when its policy allows them. The network used to pay for credit does not determine which blockchain you query.

Run the example.

Download multichain-check.mjs and its shared rpc-client.mjs into the same folder. Review them before running. The helper refuses management tokens and redirects, sends the RPC key in a header, and makes read-only calls with bounded retries.

Configuration

# Node.js 22 or newer. Save both linked scripts in one folder.
export RPC_ORIGIN='https://rpc.solidrpc.io'
export RPC_KEY_FILE='/absolute/path/to/private/rpc-key'

Run

node multichain-check.mjs

Keep the key file outside your repository. The scripts print results without credentials. They do not automatically purchase more credit when the account runs out.

Know what success looks like.

The output has one line for each of the three networks, with the expected chain ID and latest block. This uses six calls before retries. It proves connectivity, not archive coverage, throughput, or a latency guarantee. Test the actual application methods next.

For errors, inspect HTTP status and the JSON-RPC error separately. Use the error reference. Report any partial result instead of claiming the entire task completed.

Need account access? Read the setup guide or open the management API contract.