List oracles

Reports the on-chain price/data oracles from the graph's O-Chain PriceFeed registry.

GET /v1/explorer/oracles

Addresshttps://api.hanzo.ai/v1/explorer/oracles
MethodGET
Operationget_explorer_oracles
AuthAuthorization: Bearer $HANZO_API_KEY

Reports the on-chain price/data oracles from the graph's O-Chain PriceFeed registry. A reachable graph with no feeds answers an honest empty list; an unreachable or erroring graph likewise degrades to an empty list at 200 rather than a 502, so the console never error-toasts. No feed is ever fabricated.

Request

GET /v1/explorer/oracles takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200explorer.oraclesOutok
defaultproblem-detailsrefused

200 body — 8 fields.

FieldInTypeAlwaysDescription
oraclesbodyexplorer.oracleView[]—Oracles is one row per on-chain price feed, or an empty list when the graph is unreachable or carries none — never a fabricated feed.
oracles[].feedbodystring—Feed is the trading pair this feed prices.
oracles[].idbodystring—ID is the feed's own id, else its trading pair.
oracles[].namebodystring—Name is the feed's display name — the trading pair, e.g. "LUX/USD".
oracles[].sourcebodystring—Source is the oracle network the feed originates from; "O-Chain" by default.
oracles[].statusbodystring—Status is "active" for a listed feed.
oracles[].updatedAtbodystring—UpdatedAt is the feed's own timestamp, RFC 3339 UTC.
oracles[].valuebodystring—Value is the feed's price, verbatim as the registry carries it.

Failure carries the platform error shape — see Errors.

Examples

hanzo explorer oracles
import { Configuration, ExplorerApi } from 'hanzoai';

const api = new ExplorerApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getExplorerOracles();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ExplorerApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ExplorerApi(client).get_explorer_oracles()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ExplorerAPI.GetExplorerOracles(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, explorer_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = explorer_api::get_explorer_oracles(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ExplorerApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ExplorerApi(client).getExplorerOracles();
curl https://api.hanzo.ai/v1/explorer/oracles \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches explorer through the explorer tool, which names its 2 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_explorer_indexers"
         }
       }
     }'

Explorer API · All Hanzo APIs · Interactive reference

Was this page useful?