get_v1_validators_challenge
Issues the single-use nonce and the exact message a wallet must sign to claim a validator slot.
Issues the single-use nonce and the exact message a wallet must sign to claim a validator slot.
The nonce is bound to (validated org, slot) and stored server-side, so a signature obtained for one org or one slot can never be replayed for another, and the message POST /v1/validators verifies is rebuilt from those same server facts rather than trusted from the caller. Redeem it with POST /v1/validators before it expires; it can be redeemed once.
A tokenId outside the Validator tier is refused here rather than after signing.
| Tool | get_v1_validators_challenge |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | GET /v1/validators/challenge |
| Product | validators |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
tokenId | string | — | — | — | TokenID is the Validator-tier GenesisNFT token id, as a decimal string in the ?tokenId= query. A value that is not a positive integer is 400. It is a string rather than a number because the parse that has always served this route trims surrounding whitespace, and one parse rule is better than two. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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": "get_v1_validators_challenge",
"arguments": {
"tokenId": "<tokenId>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_validators_challenge | GET /v1/validators/challenge | validators | Issues the single-use nonce and the exact message a wallet must sign to claim a validator… |
The same capability over plain HTTP is in the validators API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?