Service metadata

Fragmentos de código

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

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

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

Respuesta de ejemplo

Una respuesta real de este endpoint, capturada en la última comprobación de estado.

{
    "data": {
        "note": "queue, entry, exit and meta take no parameters. validator takes id (a numeric validator index or a 0x public key). ETH amounts are the meaningful queue metric (a post-Pectra validator can hold up to 2048 ETH); validator counts are given alongside. est_clear_hours fields are ESTIMATES using the current activation/exit churn limit of 256 ETH per epoch (~6.4 min); epochs are converted to wall-clock time from mainnet genesis. A ~90-second cache fronts the upstream.",
        "sample": {
            "epoch": 454431,
            "exit_queue_eth": 128.02,
            "exit_validators": 4
        },
        "source": "Ethereum Beacon API (ethereum-beacon-api.publicnode.com), keyless, live",
        "service": "ethstakingqueue-api",
        "endpoints": {
            "GET /v1/exit": "Exit queue breakdown (voluntary exits + slashed exits).",
            "GET /v1/meta": "This document.",
            "GET /v1/entry": "Activation queue breakdown (eligible-churning + deposited-not-yet-eligible).",
            "GET /v1/queue": "Headline: entry vs exit queue ETH, counts, net flow, estimated clear times.",
            "GET /v1/validator": "One validator by index or pubkey (id=0)."
        },
        "description": "The live Ethereum validator entry and exit queues, read keyless from a public consensus-layer (Beacon) node. Staking on Ethereum means joining an activation queue; unstaking means joining an exit queue — both rate-limited by the protocol churn limit. Queue size is the cleanest real-time read on staking demand and exit pressure. The queue endpoint is the headline (ETH waiting to activate vs exit, counts, estimated clear times); entry breaks down the activation side; exit breaks down the exit side (incl. slashed exits); validator looks up any single validator by index or public key. Distinct from beaconchain-api (consensus finality), the Solana validator feeds and the liquid-staking protocol feeds.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:43.475Z",
        "request_id": "6fc1f67a-85b6-4a84-8511-69ff44b05a72"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}