Service metadata and endpoint catalog

Code snippets

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

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

$ch = curl_init("https://api.oanor.com/vechain-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/vechain-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": "VeChain Thor node API (mainnet.vechain.org, live)",
        "service": "vechain-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/block": "A block's details (revision=best|number|0xid).",
            "GET /v1/account": "An address's VET balance and VTHO energy (address=0xdec03b1419446f11cec897c9d3e0e909755562b7).",
            "GET /v1/network": "Live chain tip and dual-token info.",
            "GET /v1/transaction": "A transaction's clauses, value, gas and VTHO paid (id=0x + 64 hex)."
        },
        "tip_number": 25056892,
        "description": "Live on-chain data from the VeChainThor network (VET), an enterprise-focused layer-1 blockchain with a dual-token model (VET stores value, VTHO pays for gas), via the public VeChain Thor node API. The account endpoint returns an address's VET balance, its VTHO energy and whether it is a contract; the transaction endpoint returns a transaction's origin, clauses, total VET value, gas used, VTHO paid and whether it reverted; the block endpoint returns a block's number, id, timestamp, size, gas limit and used, Proof-of-Authority beneficiary and transaction count; the network endpoint returns the live chain tip. Live, no key, nothing stored. Distinct from the Bitcoin, Litecoin, Dogecoin, Cardano, Cosmos, Solana and EVM on-chain APIs and from price feeds — this is VeChainThor's own account state, clause-based transactions, blocks and VET/VTHO dual-token data.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-10T14:01:38.942Z",
        "request_id": "298c28dd-a042-4b3c-814d-757f939904fa"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}