Reports the on-chain price/data oracles from the graph's O-Chain PriceFeed…
Reports the on-chain price/data oracles from the graph's O-Chain PriceFeed registry.
GET /v1/explorer/oracles
| Address | https://api.hanzo.ai/v1/explorer/oracles |
| Method | GET |
| Operation | get_explorer_oracles |
| Auth | Authorization: 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
| Status | Body | Meaning |
|---|---|---|
200 | oraclesOut | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
oracles | body | 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[].feed | body | string | — | Feed is the trading pair this feed prices. |
oracles[].id | body | string | — | ID is the feed's own id, else its trading pair. |
oracles[].name | body | string | — | Name is the feed's display name — the trading pair, e.g. |
oracles[].source | body | string | — | Source is the oracle network the feed originates from; "O-Chain" by default. |
oracles[].status | body | string | — | Status is "active" for a listed feed. |
oracles[].updatedAt | body | string | — | UpdatedAt is the feed's own timestamp, RFC 3339 UTC. |
oracles[].value | body | string | — | Value is the feed's price, verbatim as the registry carries it. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
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 := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ExplorerAPI.GetExplorerOracles(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ExplorerApi(client).getExplorerOracles();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/explorer/oracles \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches explorer through the explorer tool, which names its 2 operations with its own verbs — this one among them, under a name only the door 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_indexers"
}
}
}'How is this guide?