# Validator

URL: https://docs.hanzo.ai/docs/openapi/validator

> One-click validator onboarding: prove your Genesis NFT, get a node provisioned, queue its registration.

Also for this capability: **API** · [CLI](https://docs.hanzo.ai/docs/cli/validator) · [MCP](https://docs.hanzo.ai/docs/mcp-tools/validator) · [SDKs](https://docs.hanzo.ai/docs/sdks)

One-click validator onboarding: prove your Genesis NFT, get a node provisioned, queue its registration.

> [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|                |                                        |
| -------------- | -------------------------------------- |
| **Base URL**   | `https://api.hanzo.ai`                 |
| **Operations** | 4                                      |
| **Auth**       | `Authorization: Bearer $HANZO_API_KEY` |

## Specification

Specification pending — no HIP in [hanzoai/hips](https://github.com/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 validator …`                               | 4 of 4                                                                    |
| **SDK**  | `ValidatorApi` in every published client          | 4 methods                                                                 |
| **MCP**  | tool `validator` on `https://api.hanzo.ai/v1/mcp` | 4 operations, 2 under the document's own id — ask `describe` for the rest |

## Quickstart

```bash
export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys
```

Then the first call — a read that needs nothing but the key. `GET /v1/validator`, operation `get_validator`:

**CLI**

```bash
hanzo validator list
```

**SDK**

**.ts**

```ts
import { Configuration, ValidatorApi } from 'hanzoai';

const api = new ValidatorApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getValidator();
```

**.py**

```python
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()
```

**.go**

```go
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
}
```

**.rs**

```rust
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?;
```

**.java**

```java
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();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/validator \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

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:

```bash
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"
         }
       }
     }'
```

Answers `200` with `object` — ok.

## Endpoints

| Endpoint                                                                                               | What it does                                                                                            |
| ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
| [`GET /v1/validator/{tokenId}`](https://docs.hanzo.ai/docs/openapi/validator/get-validator-by-tokenid) | Returns one claimed validator slot, scoped to the caller's org.                                         |
| [`GET /v1/validator/challenge`](https://docs.hanzo.ai/docs/openapi/validator/get-validator-challenge)  | Issues the single-use nonce and the exact message a wallet must sign to claim a validator slot.         |
| [`GET /v1/validator`](https://docs.hanzo.ai/docs/openapi/validator/get-validator)                      | Returns the validator slots the caller's org has claimed.                                               |
| [`POST /v1/validator`](https://docs.hanzo.ai/docs/openapi/validator/post-validator)                    | Claims a validator slot and provisions its node, after proving the caller's wallet owns the slot's NFT. |

---

[All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)