# NodeFlare Arbitrum One RPC (chain 42161)

> NodeFlare Arbitrum One RPC (chain 42161) 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).

Provides full JSON-RPC access to the Arbitrum One network (chain 42161) including archive methods like eth_getLogs, trace, and debug, with pay-per-request USDC billing and no API key required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/arb/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-arbitrum-one-rpc-chain-42161-8a7910b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_F9grrIxXh1h073fxNwmn8

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-arbitrum-one-rpc-chain-42161-8a7910b6 -d '<json body>'
```

Example prompt: Call eth_getLogs on Arbitrum One (chain 42161) for the USDC contract address 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, filtering for Transfer events from block 200000000 to latest.

## When to prefer this

Choose this endpoint when you need full archive access to Arbitrum One (chain 42161) including eth_getLogs, trace, and debug methods, without setting up an account or managing API keys — especially useful for AI agents that can pay per request in USDC via the x402 protocol. Prefer over free public RPCs when you need reliability, archive depth, or heavy compute methods.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params returns error code -32602 (invalid params)
- Insufficient USDC payment balance causes HTTP 402 payment required
- Block range too large for eth_getLogs may return error or timeout
- Calling debug/trace methods on a non-archive block that was pruned returns null or error
- Network congestion may increase response latency

## How this service works

Arbitrum One RPC (chain 42161): 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

Returns a standard JSON-RPC 2.0 response object containing a 'result' field with the requested blockchain data (e.g. hex balances, log arrays, block objects, trace arrays, call return values) or an 'error' field with code and message if the request fails.

## 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-arbitrum-one-rpc-chain-42161-8a7910b6/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)