# NodeFlare Cronos RPC (Chain 25)

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

Provides full JSON-RPC access to the Cronos EVM blockchain (chain 25) via HTTPS, including archive/debug/trace methods, with per-request USDC payment and no API key required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/cronos/x402
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeflare-cronos-rpc-chain-25-5876cc86
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RccV1i_axh3H3B5WzyT4C

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-cronos-rpc-chain-25-5876cc86 -d '<json body>'
```

Example prompt: Send an eth_getLogs request to the Cronos mainnet (chain 25) to fetch all Transfer events from contract 0xc21223249CA28397B4B6541dfFaEcC539BfF0c59 between blocks 10000000 and 10001000.

## When to prefer this

Choose this endpoint when you need direct JSON-RPC access to the Cronos blockchain (chain ID 25) without setting up an account or API key, and you want pay-per-request USDC billing suitable for AI agent workflows. Especially valuable for archive/debug/trace methods not always available on free RPC tiers. Prefer over managed RPC services when you need no-signup access or are operating in an agentic payment context via x402.

## Known failure modes

- Invalid JSON-RPC method returns error code -32601
- Malformed params return -32602 invalid params error
- Block not found for out-of-range block numbers
- Insufficient USDC payment results in 402 payment required
- Rate limiting or node unavailability returns 503
- eth_getLogs with too broad a filter may time out or return too many results

## How this service works

Cronos RPC (chain 25): 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. One of the first independent x402 RPC providers for this chain.

## Output

Standard Ethereum JSON-RPC response object for the requested method: could include block objects, transaction receipts, contract return values, event log arrays, trace/debug output, or gas estimates — depending on the method called. Responses follow the standard eth_* JSON-RPC envelope with id, jsonrpc, and result fields.

## 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-cronos-rpc-chain-25-5876cc86/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)