Set up RPC with an AI agent.

Create a new account.

Give your agent the machine-readable instructions. It needs HTTPS access and permission to create an account and spend your approved budget. Its own environment may still require owner actions.

1. 01

   Check access and approve the budget.

   Your agent reads current availability, networks, prices, and terms. Give it your permanent email and approve both the payment limit and usage limit.

2. 02

   Create the account and save its credential.

   The agent saves a private provisioning credential before creating the account. Account creation spends nothing. It asks for billing details only when the API requires them.

3. 03

   Authorize and fund the account.

   Use an owner-authorized wallet to sign the budget. The agent checks the funding quote, including tax and usable credit, then pays within your approved limit. SolidRPC never needs your wallet private key.

4. 04

   Activate access and connect.

   After funding settles, the agent rotates its provisioning credential into an operational credential and retires the old one. It creates a separate RPC key and verifies the chain and methods your task needs.

Prepaid access uses HTTPS. Buying a card plan requires the owner. With USDC funding, a facilitator submits the payment, so the payer does not submit an ETH gas transaction.

Connect an existing paid account.

1. Open Agent access and create a credential with only the permissions your agent needs.
2. Save the credential in a private file or secret manager. Give your agent its location and this guide.
3. Ask the agent to check your account, usage, and billing before making changes. Reuse an existing RPC key when appropriate.

Free accounts cannot delegate control. Your agent must ask before increasing budgets or changing security settings beyond your instructions.

Two keys, two jobs.

Save each key separately. Keep secrets out of prompts, source code, and repositories.

sa_Management credential

Manage the account, RPC keys, usage, and billing.

Send as a Bearer token to https://api.solidrpc.io/agent/v1. Never send it to an RPC endpoint.

ak_RPC key

Make blockchain JSON-RPC calls.

Send to https://rpc.solidrpc.io/evm/{chainId}. See supported authentication methods.

Return in a new agent session.

Give the new session the location of your saved management credential and RPC key. It can read your billing and usage through the API without an interactive login.

Keep payment intent IDs, idempotency keys, and payment proofs with your private state. If a payment result is uncertain, check the original intent before paying again. Follow the recovery instructions for interrupted payments or credential rotation.

Open the account yourself.

Use access an agent-created account with the same email. Follow the email link to set a password and sign in. This is optional.

Claiming the account keeps its agent credentials and RPC keys. Revoke them separately if needed.

Connect through HTTPS or MCP.

Start with the HTTPS onboarding instructions. They link the current terms, request schemas, and setup example.

Once you have a management credential, an MCP client can connect to https://api.solidrpc.io/agent/mcp using Streamable HTTP and Bearer authentication. Store the token through the client’s private credential settings. MCP uses the same account permissions.

Try an example.

Use a saved RPC key to read blockchain data. Each example includes an agent prompt and a runnable script.

• Read ETH and USDC balances on Base →
• Export Ethereum USDC transfers →
• Connect Ethereum, Base, and Arbitrum →