# QuickNode JSON-RPC Proxy — Litecoin Testnet

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

Proxies JSON-RPC method calls to the Litecoin testnet blockchain via QuickNode's node infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/ltc-testnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-6b7e4bed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_otuBUdZ7gEt81xragUnp8

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-6b7e4bed -d '<json body>'
```

Example prompt: Call the Litecoin testnet node and get the current block count using the getblockcount JSON-RPC method — use jsonrpc 2.0 and request ID 1.

## When to prefer this

Use this endpoint when you need to interact specifically with the Litecoin testnet blockchain via JSON-RPC — for testing LTC transactions, querying testnet block/transaction data, or developing Litecoin applications before mainnet deployment. Prefer this over ltc-mainnet when testing or developing to avoid real funds.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array returns error code -32602 invalid params
- Testnet node unavailable returns HTTP 503 or timeout
- Payment not included or insufficient returns HTTP 402 payment required
- Unsupported method for Litecoin returns error

## How this service works

JSON-RPC proxy — ltc-testnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested Litecoin testnet method call, including the result field with chain data (e.g. block number, transaction info, balance) or an error object if the call failed.

## 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-6b7e4bed/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)