# NodeFlare Base RPC (Chain 8453)

> NodeFlare Base RPC (Chain 8453) is a paid API for AI agents from rpc.nodeflare.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Executes JSON-RPC calls against the Base (chain 8453) EVM network via NodeFlare's bare-metal archive nodes, paid per-request in USDC with no account required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/base/x402?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeflare-base-rpc-chain-8453-fb4b94e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JUqg40Bib16xb_3WGp4bj

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability nodeflare-base-rpc-chain-8453-fb4b94e3 -d '<json body>'
```

Example prompt: Call eth_getLogs on Base chain to fetch all Transfer events for the USDC contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 from block 18000000 to 18001000.

## When to prefer this

Choose this endpoint when you need direct, low-level EVM JSON-RPC access to Base (chain 8453) — especially for archive queries, event indexing, transaction simulation, or tracing — without setting up an account or API key. Ideal for AI agents making pay-per-use calls in USDC via x402. Prefer over managed RPC providers when you need debug/trace methods, archive depth, or want to avoid API key management.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601
- Malformed params array causes -32602 invalid params error
- Insufficient USDC balance or payment failure returns 402 Payment Required
- Requesting a pruned state on a non-archive range (not applicable here, archive supported)
- Rate limits or node unavailability may return 503
- Unsupported method on Base (e.g. eth_mining) returns -32601

## How this service works

Base RPC (chain 8453): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy calls priced by compute units.

## Output

A standard JSON-RPC 2.0 response object containing the result field populated with blockchain data (block info, logs, call return values, traces, etc.) or an error object with code and message if the call fails. Archive-depth data is available for all historical blocks.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nodeflare-base-rpc-chain-8453-fb4b94e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rpc.nodeflare.app](https://www.zero.xyz/host/rpc.nodeflare.app/llms.txt)
