get_v1_usage_leaderboard

Leaderboard ranks AI usage over a window, either the users of the caller's own org or organizations against each other, and always reports the caller's own standing even when it falls outside the returned page. Identities are private by default: a caller sees themselves, plus the peers or orgs that opted into public listing, and only an admin sees their own org's members named. Cross-org spend is restricted to platform admins. When the warehouse is not connected the board answers empty with available=false rather than a fabricated rank.


Tool	`get_v1_usage_leaderboard`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	4
Operation	`GET /v1/usage/leaderboard`
Product	usage

Arguments

Field	Type	Required	Default	Description
`limit`	`integer`	—	—	Limit caps the rows returned, clamped to 100. Defaults to 10, which is also what a non-positive or unparseable value takes.
`metric`	`string`	—	—	Metric is the value ranked: tokens (default), requests, or cost.
`period`	`string`	—	—	Period is the window ranked: day, week, month (default) or all.
`scope`	`string`	—	—	Scope picks the board: "personal" (default) ranks the caller among their own org's users, "org" is that same org board named for an admin, "global" ranks organizations against each other.

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": "get_v1_usage_leaderboard",
         "arguments": {
           "limit": 0,
           "metric": "<metric>",
           "period": "<period>",
           "scope": "<scope>"
         }
       }
     }'

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_get_v1_usage_leaderboard`	`GET /v1/usage/leaderboard`	usage	Leaderboard ranks AI usage over a window, either the users of the caller's own org or orga

The same capability over plain HTTP is in the usage 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).

get_v1_usage_leaderboard

Arguments

Call it

The operation behind it

On this page