# NodeFlare Linea RPC (chain 59144)

> NodeFlare Linea RPC (chain 59144) 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-10).

Executes any Ethereum JSON-RPC method against the Linea network (chain 59144) via NodeFlare's bare-metal archive nodes, with per-request USDC micropayment and no API key required.

## Facts

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

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-linea-rpc-chain-59144-7c15fa58 -d '<json body>'
```

Example prompt: Call eth_getLogs on Linea (chain 59144) for contract 0xYourContract from block 5000000 to 5001000 — I need all Transfer events emitted in that range.

## When to prefer this

Choose this endpoint when you specifically need to interact with the Linea network (chain ID 59144) and want full archive access including eth_getLogs, eth_call, trace, and debug methods without registering an account or obtaining an API key. It is ideal for AI agents that need to pay per-request in USDC via x402, index on-chain events, simulate transactions, or debug contract behavior on Linea.

## Known failure modes

- Invalid JSON-RPC method returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Block range too large for eth_getLogs returns an error asking to reduce range
- Insufficient USDC balance or failed x402 payment returns HTTP 402
- Network congestion or node unavailability may return HTTP 503 or timeout
- Requesting a pruned block on a non-archive node returns missing trie node error

## How this service works

Linea RPC (chain 59144): 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 Ethereum JSON-RPC response object with 'jsonrpc', 'id', and 'result' fields. The result varies by method: block objects for eth_getBlockByNumber, log arrays for eth_getLogs, hex-encoded return data for eth_call, trace objects for trace_transaction, and so on. Errors are returned as a JSON-RPC 'error' object with code and message.

## 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-linea-rpc-chain-59144-7c15fa58/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)
