Service metadata

Extraits de code

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

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

$ch = curl_init("https://api.oanor.com/beaconchain-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/beaconchain-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Exemple de réponse

Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.

{
    "data": {
        "note": "All endpoints take no parameters. Slots and epochs are integers; an epoch is 32 slots (≈ 6.4 minutes). finality_lag is epochs the head is ahead of the last finalized epoch (≈2 is healthy). Times are UTC. A ~30-second cache fronts the beacon node.",
        "sample": {
            "head_slot": 14541812,
            "head_epoch": 454431
        },
        "source": "public Ethereum consensus-layer (Beacon) API, keyless, live",
        "service": "beaconchain-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/status": "Head slot/epoch, epoch clock, finalized epoch, finality lag, sync health.",
            "GET /v1/genesis": "Genesis time, network age and slot/epoch timing constants.",
            "GET /v1/finality": "Finalized & justified checkpoints with lag behind head."
        },
        "description": "The live consensus state of Ethereum's Beacon Chain — the proof-of-stake layer that secures Ethereum — read keyless from a public consensus-layer node. The status endpoint gives the head slot and epoch, the epoch clock, the finalized and justified epochs and the finality lag (with an is_finalizing health flag); finality gives the finalized/justified checkpoints in detail with how far behind the head they are; genesis gives the chain's genesis time, age and slot/epoch timing constants. The Ethereum consensus / finality cut — distinct from the execution-layer feeds (gas, blocks, transactions), the staking-token and restaking feeds and the price feeds. It reports consensus state (slots, epochs, finality), not per-validator economics (which a public node does not serve in one call).",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:53.783Z",
        "request_id": "072ac738-d9eb-4daf-87e8-f30410ab019a"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}