# NodeFlare Polygon PoS RPC (Chain 137)

> NodeFlare Polygon PoS RPC (Chain 137) 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 Polygon PoS (chain 137) via NodeFlare's bare-metal archive nodes, billed per-request in USDC with no API key required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/polygon/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-polygon-pos-rpc-chain-137-81fdfb16
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XV2cdh-AUaDDswFvQzEPw

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-polygon-pos-rpc-chain-137-81fdfb16 -d '<json body>'
```

Example prompt: Call eth_getLogs on Polygon mainnet (chain 137) to fetch all Transfer events from the USDC contract at 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174 between block 50000000 and 50001000.

## When to prefer this

Choose this endpoint when you need to query Polygon PoS (chain 137) specifically and want archive depth (eth_getLogs, trace, debug) without managing API keys or subscriptions. Ideal for AI agents that pay per-call via x402/USDC rather than maintaining a monthly plan. Prefer this over generic RPC providers when you need trace and debug methods, event indexing across large block ranges, or contract simulation on Polygon archive state.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Requesting a block range too large for eth_getLogs may return a range-limit error
- Insufficient USDC balance causes payment failure before the RPC call is executed
- Network congestion on Polygon can cause occasional timeouts on heavy archive queries
- Trace/debug methods on very old blocks may time out if compute units exceed limits

## How this service works

Polygon PoS RPC (chain 137): 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 either a 'result' field with the method's return value (e.g. hex-encoded data, log arrays, block objects, trace frames) or an 'error' field with code and message if the call failed.

## 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-polygon-pos-rpc-chain-137-81fdfb16/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)