put_v1_admin_enablement
SetEnablement sets one item's global enablement state — off, beta or ga — and optionally replaces the list of orgs granted its beta.
SetEnablement sets one item's global enablement state — off, beta or ga — and
optionally replaces the list of orgs granted its beta. It is generic over
kind, so the same call manages models, providers and product features through
the one registry. off is an absolute kill switch: a self-service opt-in can
never re-open it. SuperAdmin only; every other caller is refused.
| Tool | put_v1_admin_enablement |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | PUT /v1/admin/enablement |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
betaOrgs | string[] | — | — | BetaOrgs REPLACES the item's beta grant list when present. Omit it to leave the existing grants alone. |
id | string | — | — | ID is the item within that namespace — a model id, a provider name, or a feature's key. |
kind | string | — | — | Kind is the item's namespace: "model", "provider" or "feature". |
state | string | — | — | State is the item's global enablement: "off" (hidden from everyone, absolutely), "beta" (visible only to granted orgs) or "ga" (visible to everyone). Required. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "put_v1_admin_enablement",
"arguments": {
"betaOrgs": [
"<betaOrgs>"
],
"id": "<id>",
"kind": "<kind>",
"state": "<state>"
}
}
}'Values are placeholders derived from each field's declared type. 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 |
|---|---|---|---|
cloud_put_v1_admin_enablement | PUT /v1/admin/enablement | cloud | SetEnablement sets one item's global enablement state — off, beta or ga — and optionally r |
The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?