Oracle freshness/health — fresh vs stale feeds

Frammenti di codice

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

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

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

Risposta di esempio

Una risposta reale di questo endpoint, acquisita dall'ultimo health check.

{
    "data": {
        "note": "The on-chain health of the tracked Chainlink feeds — how many have updated recently (fresh) versus gone quiet (stale, over 24h), the average time since last update and the stalest feed. This is the oracle-reliability check a DeFi integration needs: protocols that read a stale feed can mis-price collateral, so monitoring freshness on-chain is the safety layer a plain price API doesn't give you. Live, cached ~60s.",
        "source": "Ethereum public JSON-RPC (Chainlink aggregators), keyless",
        "all_fresh": true,
        "fresh_count": 15,
        "stale_count": 0,
        "stale_feeds": [],
        "stalest_feed": {
            "pair": "AVAX/USD",
            "fresh": true,
            "seconds_since_update": 56320
        },
        "feeds_tracked": 15,
        "avg_update_age_seconds": 17538
    },
    "meta": {
        "timestamp": "2026-06-12T19:35:39.527Z",
        "request_id": "2340fa42-ec19-444d-b103-c3f722ba56c6"
    },
    "status": "ok",
    "message": "Health retrieved successfully",
    "success": true
}