Reports the deployment's chain indexer(s) and how far each has indexed.
Reports the deployment's chain indexer(s) and how far each has indexed.
GET /v1/explorer/indexers
| Address | https://api.hanzo.ai/v1/explorer/indexers |
| Method | GET |
| Operation | get_explorer_indexers |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Reports the deployment's chain indexer(s) and how far each has
indexed. Identity and health come from the indexer's /health; the latest indexed
block (height + time) from its /v1/explorer/blocks. The row EXISTS if EITHER call
reaches the indexer; when the indexer is entirely unreachable the answer degrades
to an honest-EMPTY list at 200, not a 502. No chain HEAD is exposed by the indexer
REST, so lag is honestly omitted rather than fabricated.
Request
GET /v1/explorer/indexers takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | indexersOut | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
indexers | body | indexerView[] | — | Indexers is one row per reachable chain indexer, or an empty list when the indexer is unreachable — never a fabricated row. |
indexers[].chain | body | string | — | Chain is the chain this indexer indexes, as the indexer names it. |
indexers[].height | body | string | — | Height is the latest INDEXED block height, as a decimal string. |
indexers[].id | body | string | — | ID identifies the indexer: its chain name, else its chain id, else the brand. |
indexers[].lag | body | string | — | Lag is how far behind the chain HEAD this indexer is. |
indexers[].network | body | string | — | Network is the deployment's network tier: mainnet, testnet or devnet. |
indexers[].status | body | string | — | Status is "degraded" when /health explicitly reports unhealthy, else "active". |
indexers[].updatedAt | body | string | — | UpdatedAt is the latest indexed block's timestamp, RFC 3339 UTC. |
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.getExplorerIndexers();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_indexers()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ExplorerAPI.GetExplorerIndexers(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_indexers(&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).getExplorerIndexers();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/indexers \
-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?