Service metadata and endpoint catalog

Code snippets

curl "https://api.oanor.com/nano-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/nano-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/nano-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/nano-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Example response

A real response from this endpoint, captured by the latest health check.

{
    "data": {
        "source": "Nano RPC via a public node (rpc.nano.to, live)",
        "service": "nano-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/block": "A single block's amount, balance and confirmation (hash=64 hex).",
            "GET /v1/account": "An account's XNO balance, receivable and representative (account=nano_1nanode8ngaakzbck8smq6ru9bethqwyehomf79sae1k7xd47dkidjqzffeg).",
            "GET /v1/history": "An account's own chain of blocks (account=nano_…, count=15).",
            "GET /v1/network": "Block counts and online ORV voting weight."
        },
        "description": "Live on-chain data from the Nano network (XNO), a feeless, instant cryptocurrency with a block-lattice architecture where every account has its own blockchain and consensus is reached by Open Representative Voting (ORV), via a public Nano RPC node. The account endpoint returns an account's confirmed XNO balance, receivable balance, block count and delegated representative; the history endpoint returns an account's own chain of blocks; the block endpoint returns a single block's amount, balance, height and confirmation; the network endpoint returns the total, cemented and unchecked block counts and the online voting weight securing the network. Live, no key, nothing stored. Distinct from the Bitcoin, Stacks, EOS, Internet Computer and EVM on-chain APIs and from price feeds — this is Nano's own block-lattice account chains and ORV voting weight.",
        "total_blocks": 220091712,
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-10T13:59:46.554Z",
        "request_id": "9a38d171-6aa1-4d4a-8e96-d0349bbf4a72"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}