post_v1_referrals_claim
Records that the caller's org signed up through a referral code.
Records that the caller's org signed up through a referral code.
The REFEREE is the validated caller, never a client field, and the referrer is resolved from the code — so a caller can only ever attach THEMSELVES to someone else's code. Referring yourself is 400 and an unknown code is 404.
It is idempotent and first-touch: an org can be referred once, ever. A repeat call returns the referral already on file with created=false and 200, where the first call answers 201.
Recording a referral grants nothing. Both bonuses are granted later, when the referee actually makes metered spend — see GET /v1/referrals and POST /v1/admin/referrals/sweep.
| Tool | post_v1_referrals_claim |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | POST /v1/referrals/claim |
| Product | referrals |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
code | string | — | — | — | Code is the referrer's referral code, as it appeared in their ?ref= link. Case and surrounding whitespace do not matter. |
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": "post_v1_referrals_claim",
"arguments": {
"code": "<code>"
}
}
}'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 |
|---|---|---|---|
post_v1_referrals_claim | POST /v1/referrals/claim | referrals | Records that the caller's org signed up through a referral code. |
The same capability over plain HTTP is in the referrals 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?