get_v1_referrals

Returns the caller's referral code, share link and the referrals they have made.

The code is a stable, deterministic function of the org, so the link in this response is the same one every time. Each row carries the referee, its status and the credit this org earned from it; creditsEarnedCents is their sum.

The read is self-updating: before listing, it runs the qualify check over this org's still-pending referees, so a referee who has since made metered spend is credited by the act of the referrer loading their page. That check is best-effort and bounded — a commerce hiccup leaves the referral pending for the next check rather than failing the page — and the grant is latched at-most-once, so this path and the admin sweep can never double-pay.

Arguments

This tool declares no arguments. Call it with an empty arguments object.

Call it

A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.

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_referrals",
         "arguments": {}
       }
     }'

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

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