# QuickNode JSON-RPC Proxy — Starknet Mainnet (STRK)

> QuickNode JSON-RPC Proxy — Starknet Mainnet (STRK) is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-15).

Proxies JSON-RPC method calls to the Starknet mainnet blockchain, enabling reads and writes against the live STRK network.

## Facts

- Endpoint: POST https://x402.quicknode.com/strk-mainnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-3afb0400
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dpyo_dwR_dWgNGjIfCQB0

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 quicknode-3afb0400 -d '<json body>'
```

Example prompt: Can you call starknet_getBlockWithTxs on Starknet mainnet with the latest block tag so I can see the most recent transactions?

## When to prefer this

Choose this endpoint when you need live, production-grade access to Starknet mainnet — for reading chain state, querying contracts, or submitting transactions on the STRK network. Prefer this over self-hosted nodes for reliability, or over testnet endpoints when you need real mainnet data.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Network congestion or node unavailability returns 503 or timeout
- Payment failure (insufficient USDC) blocks the request with 402
- Requesting a non-existent block hash or transaction hash returns null result

## How this service works

JSON-RPC proxy — strk-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested Starknet method call — such as block details, transaction data, contract call output, or account balance — or an error object if the method fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "jsonrpc",
  "method"
 ],
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ],
   "description": "Request identifier"
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
  },
  "params": {
   "type": "array",
   "description": "Method parameters"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "error": {
   "type": "object",
   "properties": {
    "code": {
     "type": "integer"
    },
    "message": {
     "type": "string"
    }
   }
  },
  "result": {
   "description": "RPC result (type varies by method)"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-3afb0400/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quicknode.com](https://www.zero.xyz/host/x402.quicknode.com/llms.txt)