Validator
Package validators is one-click validator onboarding: prove your Genesis NFT, get a node provisioned, queue its registration.
Package validators is one-click validator onboarding: prove your Genesis NFT, get a node provisioned, queue its registration.
| Base URL | https://api.hanzo.ai |
| Operations | 4 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Specification
Specification pending — no HIP in hanzoai/hips declares capability: validator yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.
Four surfaces
| Surface | Reaches this capability as | Coverage |
|---|---|---|
| REST | validator at its own prefix | 4 operations |
| CLI | hanzo validators … | 4 of 4 |
| SDK | — | no published client declares one yet — regenerating the clients is what adds them |
| MCP | tool validators on https://api.hanzo.ai/v1/mcp | 4 operations, 2 under the document's own id — ask describe for the rest |
Quickstart
export HANZO_API_KEY=sk-... # console.hanzo.ai → API keysThen the first call — a read that needs nothing but the key. GET /v1/validator, operation get_validator:
hanzo validators listimport { 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 := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ValidatorAPI.GetValidator(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ValidatorApi(client).getValidator();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/validator \
-H "Authorization: Bearer $HANZO_API_KEY"Tool validators, op get_validator — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "validators",
"arguments": {
"op": "get_validator",
"input": {}
}
}
}'Answers 200 with object — ok.
Endpoints
| Endpoint | What it does |
|---|---|
GET /v1/validator/{tokenId} | Returns one claimed validator slot, scoped to the caller's org. |
GET /v1/validator/challenge | Issues the single-use nonce and the exact message a wallet must sign to claim a validator slot. |
GET /v1/validator | Returns the validator slots the caller's org has claimed. |
POST /v1/validator | Claims a validator slot and provisions its node, after proving the caller's wallet owns the slot's NFT. |
How is this guide?
Reference
Package reference is the lookup data a risk decision needs but cannot derive: which email domains hand out throwaway inboxes, which addresses belong to a datacentre or a Tor exit, which card scheme…
Wallet
Package wallets is blockchain key custody: create wallets, rotate their keys, and sign with them.