Olenza Node — JSON-RPC

Direct JSON-RPC to our own full nodes for every chain. No node to run yourself.

Machine-readable: OpenAPI 3.1 · these docs as markdown · llms.txt

Endpoint

POST https://node.olenza.io/v1/rpc/{chain}

Chains: btc, ltc, zec, dcr, xmr. The body is a standard JSON-RPC request, or an array of them for a batch. Monero (xmr) takes one call per request: monerod does not accept batches, so the gateway refuses an array for it with INVALID_REQUEST, not counted.

Authentication

Send your API key in a header:

X-API-Key: olz_…
Authorization: Bearer olz_…     (either one)

If your client cannot set headers, put the key in the path: https://node.olenza.io/v1/rpc/{chain}/olz_…. Prefer the header: our servers never log the path or the full key, but your own tools, proxies and browser history may keep a URL. The same key works for the Explorer API (header only there).

Examples

Each chain speaks its own node's dialect — the gateway does not translate. One example per dialect:

Bitcoin-style RPC — BTC, LTC, ZEC, DCR

curl https://node.olenza.io/v1/rpc/btc \
  -H "X-API-Key: $OLENZA_KEY" \
  --data '{"jsonrpc":"1.0","id":1,"method":"getblockcount","params":[]}'

{"result":969857,"error":null,"id":1}

Monero daemon RPC — XMR

curl https://node.olenza.io/v1/rpc/xmr \
  -H "X-API-Key: $OLENZA_KEY" \
  --data '{"jsonrpc":"2.0","id":"0","method":"get_block_count"}'

{"id":"0","jsonrpc":"2.0","result":{"count":3776747,"status":"OK","untrusted":false}}

Opening an endpoint in a browser shows a short help page; a GET from code is refused with 405 USE_POST.

Once your key is recognised, every response — answers and refusals alike — carries your current limits. Refusals before that (401, an unknown chain, TOO_MANY_INVALID_KEYS) do not.

Errors

Errors are JSON-RPC error objects. error.data.reason is a stable code:

Errors returned by the node itself (for example "Block not found") are passed through unchanged.

Using the API means accepting the Terms of Service — in short: one free account per person, no reselling raw access, no getting around limits.

Only these methods are available — wallet, peer, node-control and UTXO-set scan methods are not. Every call counts as one unit.

Blocks, transactions and addresses as JSON, from the same indexes as the explorer site.

Machine-readable: OpenAPI 3.1 · per-chain reference with live samples: explorer.olenza.io/api

Endpoint

GET https://explorer.olenza.io/api/v1/{chain}/…

Chains: btc, ltc, zec, dcr, xmr. GET, except the one endpoint that takes a secret (outputs/check, a POST); answers are application/json.

Authentication

Send your API key in the X-API-Key header (or Authorization: Bearer). The same key works for Olenza Node. Keys are never accepted in the URL — URLs end up in logs.

Use of the API is covered by the Terms of Service.

curl -H "X-API-Key: $OLENZA_KEY" https://explorer.olenza.io/api/v1/btc/status

A Bitcoin transaction consumes outputs and creates new ones. A Monero transaction hides its amounts and recipients on purpose. Forcing both into one shape would mean lying about one of them, so the API has two shapes and /status says which one a chain answers with, in family:

An endpoint a chain's family does not have answers 404 NOT_ON_THIS_CHAIN and says why. It is a fact about the chain, not a failure.

Basics

• Amounts are strings in the coin's smallest unit. Divide by 10^decimals — decimals is in /status. Strings, because some totals do not fit a 64-bit integer and JavaScript loses precision above 2⁵³.
• A field that does not apply to a chain is left out, never null.
• Paging: page and page_size.

Limits and errors

Every call counts as one unit, whatever the endpoint, and once against the per-second rate limit. The Explorer API has its own limits, separate from Olenza Node (see Limits). Every response carries the same X-RateLimit-*, X-Quota-* and X-Request-Id headers as Node (see the Node tab). 5xx the explorer fails to answer are not counted, except 504 UPSTREAM_TIMEOUT, which is counted like any call that runs past the time limit; a 404 for something that does not exist is an answer and is counted.

{"error": {"reason": "NOT_FOUND", "message": "transaction not found"}}

Base https://explorer.olenza.io/api/v1/{chain}/…. Which endpoints a chain answers depends on its family. Try any of them against a chain with your key, or browse the explorer site.

Every chain

utxo chains

ring chains (Monero)

Monero has no address lookup: an address never appears on the chain.

Real answers from Bitcoin, trimmed where a list is long. Other utxo chains answer in the same shape; ring chains add a ring object to /status and use their own transaction shape.

{
  "chain": "btc", "name": "Bitcoin", "symbol": "BTC", "decimals": 8,
  "family": "utxo",
  "height": 969857,
  "best_hash": "00000000000000000000ead5f66b412664314405c5cbf8eec247f8fb414f050c",
  "difficulty": 132716002350731.3,
  "in_sync": true,
  "node_version": "/Satoshi:27.1.0/",
  "mempool_count": 3456
}

{
  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
  "balance": "10749121007",
  "received": "10749121007",
  "sent": "0",
  "tx_count": 66717,
  "unconfirmed": "42303"
}

{
  "txid": "04453bd51515e7014016d1ea328ee1f731185688e60e274a5058b6e72472ed7d",
  "block_hash": "00000000000000000000ead5f66b412664314405c5cbf8eec247f8fb414f050c",
  "block_height": 969857,
  "confirmations": 1,
  "time": 1791121118,
  "vsize": 346,
  "vin": [
    {"n": 0, "txid": "cc628ec46a68300b2d8ad0dafb00897c0a8186c9311919be0d8aa57e9fa9b344",
     "vout": 9, "value": "134605279", "addresses": ["1KdCveSZfa6AKqNwod25fWXGhLDs3aLyDD"]}
  ],
  "vout": [
    {"n": 0, "value": "55152", "addresses": ["bc1qahz063em92csjdfauvvh7vvmex4sm7kae7t4v4"]},
    {"n": 5, "value": "127130057", "addresses": ["1Nb9NUVWpjruzafXh2uKK5v5xxEEL1hPrH"]}
  ],
  "value_in": "134605279",
  "value_out": "134598039",
  "fee": "7240"
}

HTTP/2 404
{"error": {"reason": "NOT_FOUND", "message": "transaction not found"}}