adminWaitlistBoost

Grants a user waitlist points, moving them up toward the access cutoff. This is the access lever: the cutoff itself does not move, the person does.

It funnels through the engine's verified grant seam (POST /v1/waitlist/award with source="grant" — the ONE path that honours an explicit points amount) and writes a tamper-evident audit row either way, so a FAILED grant is recorded too. The reason field goes only to that row.


Tool	`adminWaitlistBoost`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	5
Operation	`POST /v1/admin/waitlist/boost`
Product	cloud

Arguments

Field	Type	Required	Default	Description
`email`	`string`	—	—	Email identifies the entry to boost. Either this or RefCode is required.
`points`	`integer`	—	—	Points is how many points to award. Must be positive — this seam exists to move someone UP toward the cutoff.
`reason`	`string`	—	—	Reason is the operator's justification. Not sent to the engine; it is recorded on the audit row, which is the point of asking for it.
`refCode`	`string`	—	—	RefCode identifies the entry by its referral code, when the email is unknown.
`waitlist`	`string`	—	—	Waitlist is the waitlist slug the grant lands on. 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": "adminWaitlistBoost",
         "arguments": {
           "email": "<email>",
           "points": 0,
           "reason": "<reason>",
           "refCode": "<refCode>",
           "waitlist": "<waitlist>"
         }
       }
     }'

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_adminWaitlistBoost`	`POST /v1/admin/waitlist/boost`	cloud	Grants a user waitlist points, moving them up toward the access cutoff.

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).

Arguments

Call it

The operation behind it

On this page