Base
by BlockRun.AI in Onchain & crypto
Multi-chain JSON-RPC passthrough fronted by BlockRun, powered by Tatum's gateway across 40 chains (Ethereum, Base, Solana, Polygon, BSC, Arbitrum, Optimism, Avalanche, Bitcoin, Sui, and more). One endpoint, every chain, pay-per-call in USDC, no API key. $0.002 per call (or per element of a JSON-RPC batch). Network: Base.
https://blockrun.ai/api/v1/rpc/base- Price
- $0.003
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 330 ms
- 520 ms slowest 5%
- Last check
- Passed
- 4 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://blockrun.ai/api/v1/rpc/base
Each call costs $0.003 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
Built from the input schema. Replace the values with your own.
POST https://blockrun.ai/api/v1/rpc/base
content-type: application/json
{
"id": "example",
"jsonrpc": "example",
"method": "example"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string or number | Yes | JSON-RPC id |
jsonrpc | string | Yes | "2.0" |
method | string | Yes | Chain RPC method, e.g. eth_blockNumber, eth_call, eth_getBalance (EVM) or getSlot, getAccountInfo (Solana). |
params | array | No | Method-specific params. |
Example response
The provider's example. We can't check it without paying.
{
"id": "",
"jsonrpc": "",
"result": {}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://blockrun.ai/api/v1/rpc/base' \
-H 'content-type: application/json' \
--data-raw '{"id":"example","jsonrpc":"example","method":"example"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://blockrun.ai/api/v1/rpc/base' \
-H 'content-type: application/json' \
--data-raw '{"id":"example","jsonrpc":"example","method":"example"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fblockrun.ai%2Fapi%2Fv1%2Frpc%2Fbase&method=POST
const res = await pay("https://blockrun.ai/api/v1/rpc/base", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"id": "example",
"jsonrpc": "example",
"method": "example"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://blockrun.ai/api/v1/rpc/base",
json={
"id": "example",
"jsonrpc": "example",
"method": "example",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 276 ms | $0.003 |
| 9 h ago | Passed | 402 | 374 ms | $0.003 |
| 14 h ago | Passed | 402 | 342 ms | $0.003 |
| 18 h ago | Passed | 402 | 296 ms | $0.003 |
| 23 h ago | Passed | 402 | 284 ms | $0.003 |
Show 10 older checks
| 27 h ago | Passed | 402 | 305 ms | $0.003 |
| 32 h ago | Passed | 402 | 330 ms | $0.003 |
| 36 h ago | Passed | 402 | 366 ms | $0.003 |
| 40 h ago | Passed | 402 | 286 ms | $0.003 |
| 44 h ago | Passed | 402 | 346 ms | $0.003 |
| 2 days ago | Passed | 402 | 280 ms | $0.003 |
| 2 days ago | Passed | 402 | 161 ms | $0.003 |
| 2 days ago | Passed | 402 | 472 ms | $0.003 |
| 3 days ago | Passed | 402 | 316 ms | $0.003 |
| 3 days ago | Passed | 402 | 415 ms | $0.003 |