List validator

Returns the validator slots the caller's org has claimed.

GET /v1/validator

Addresshttps://api.hanzo.ai/v1/validator
MethodGET
Operationget_validator
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the validator slots the caller's org has claimed.

One entry per claimed slot with its node identity, its live-ish node status and the owner-gated registration queued for it, if any. Slots are org-scoped by the validated identity, so a caller can only ever see their own — a slot claimed by another org is not merely hidden from this list, it is unreachable through the whole surface.

Request

1 field.

FieldInTypeRequiredDescription
limitquerystring—Limit is how many slots to return, as a decimal string in the ?limit= query.

Response

StatusBodyMeaning
200validator.validatorListok
defaultproblem-detailsrefused

200 body — 17 fields.

FieldInTypeAlwaysDescription
databodyvalidator.slotView[]—Data is one entry per slot this org has claimed.
data[].blsPubkeybodystring—BLSPubkey is the node's BLS public key, hex.
data[].crNamebodystring—CRName is the LuxNetwork custom resource that materializes the node.
data[].createdAtbodyinteger (int64)—CreatedAt is when the slot was first claimed, as a Unix timestamp.
data[].namespacebodystring—Namespace is the Kubernetes namespace the node's CR lives in.
data[].networkbodystring—Network is the luxd network slug the node joins.
data[].nodeIDbodystring—NodeID is the luxd node id derived from the sealed staking identity.
data[].nodeStatusbodystring—NodeStatus is the provisioning state of the node: "node_created" once the CR is applied, "node_pending" when no cluster is reachable (the slot is still claimed and the keys are still sealed).
data[].registrationbodyvalidator.registrationView—
data[].registration.idbodystring—ID is the registration's handle.
data[].registration.nodeIDbodystring—NodeID is the luxd node the registration is for.
data[].registration.statusbodystring—Status is the registration's lifecycle state; "pending_owner_approval" until the owner co-signs it out of band.
data[].slotbodyinteger (uint64)—Slot is the validator slot number — the same value as tokenId, under the name the portal reads.
data[].tokenIdbodyinteger (uint64)—TokenID is the GenesisNFT token id that IS this slot.
data[].updatedAtbodyinteger (int64)—UpdatedAt is when the slot last changed, as a Unix timestamp.
data[].walletbodystring—Wallet is the lowercase Ethereum address that proved ownership of the NFT.
networkbodystring—Network is the luxd network slug new nodes join on this deployment.

Failure carries the platform error shape — see Errors.

Examples

hanzo validator list
import { Configuration, ValidatorApi } from 'hanzoai';

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

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

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

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

let result = validator_api::get_validator(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ValidatorApi;

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

var result = new ValidatorApi(client).getValidator();
curl https://api.hanzo.ai/v1/validator \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches validator through the validator tool, which names its 4 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_validators"
         }
       }
     }'

Validator API · All Hanzo APIs · Interactive reference

Was this page useful?