leaderboard
leaderboard: 6 operations.
leaderboard: 6 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | leaderboard |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/usage/activity · GET /v1/usage/leaderboard · GET /v1/usage/leaderboard/optin |
| Product | usage |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is the door's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means the door does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
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": "leaderboard",
"arguments": {
"op": "get_usage_activity"
}
}
}'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
leaderboard dispatches to 6 operations. 3 of them the door names exactly as the document ids them, and those are below; for the rest the door has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
get_usage_activity | GET /v1/usage/activity | usage | Activity returns the per-day usage series for ONE authorized subject — the points a… |
get_usage_leaderboard | GET /v1/usage/leaderboard | usage | Leaderboard ranks AI usage over a window, either the users of the caller's own org or… |
get_usage_leaderboard_optin | GET /v1/usage/leaderboard/optin | usage | Returns the caller's own public-listing preference and their org's, each with whether the… |
The same capability over plain HTTP is in the usage API reference, on https://api.hanzo.ai.
How is this guide?