# List beta URL: https://docs.hanzo.ai/docs/openapi/leaderboard/get-leaderboard-beta > Ranks everyone on the hanzo.ai/beta waitlist by one score: 1 per star on GitHub verified for the record and 1 per founder link followed, plus 1 per org that signed up with its referral code, plus 20 per such org that has made metered spend, plus 1 per 100,000 tokens the person used, all time. `GET /v1/leaderboard/beta` > [Leaderboard →](https://docs.hanzo.ai/docs/openapi/leaderboard) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | ------------------------------------------ | | **Address** | `https://api.hanzo.ai/v1/leaderboard/beta` | | **Method** | `GET` | | **Operation** | `get_leaderboard_beta` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Ranks everyone on the hanzo.ai/beta waitlist by one score: 1 per star on GitHub verified for the record and 1 per founder link followed, plus 1 per org that signed up with its referral code, plus 20 per such org that has made metered spend, plus 1 per 100,000 tokens the person used, all time. Ties go to the earlier application. Share clicks count for nothing. Everyone who ever applied is on it. A form filed before the person had an account is a row of its own (no name, score 0, the day it was filed) until their account's record claims it, and the record then begins when the form did. A row is named only for a person who opted into the public board (PUT /v1/leaderboard/optin); the caller always sees their own row named. Tokens are a range on every row and exact on a named row and the caller's. `tokens` and `referrals` say whether the warehouse and the referral service answered; a term that did not is left out of every score alike. A named handler, not a closure, so zipdoc can lift this prose into the registry. ## Request 1 field. | Field | In | Type | Required | Description | | ------- | ----- | ------- | -------- | --------------------------------------- | | `limit` | query | integer | — | Limit caps the rows, clamped to 1..100. | ## Response | Status | Body | Meaning | | --------- | --------------------- | ------- | | `200` | leaderboard.BetaBoard | ok | | `default` | problem-details | refused | `200` body — 23 fields. | Field | In | Type | Always | Description | | ------------------- | ---- | ---------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------- | | `of` | body | integer (int64) | — | Of is how many people are on the waitlist: every account that applied, and every lead that applied before it had an account. | | `referrals` | body | boolean | — | Referrals is whether referrals were counted; false when the referral service did not answer, and no record's score has them then. | | `rows` | body | leaderboard.BetaRow\[] | — | Rows are the top of the waitlist, best first. | | `rows[].applied` | body | string | — | Applied is the day the application began, 2006-01-02: the record's own, or the day of the lead it claims when that was earlier. | | `rows[].name` | body | string | — | Name is the handle its owner listed under on the public board; null for a person who did not opt in, whom the page calls a builder. | | `rows[].qualified` | body | integer (int64) | — | Qualified is how many of them have made metered spend. | | `rows[].rank` | body | integer (int64) | — | Rank is the record's place, 1 first. | | `rows[].referrals` | body | integer (int64) | — | Referrals is how many orgs signed up with the record's referral code. | | `rows[].score` | body | integer (int64) | — | Score is what the row is ranked by: points, referrals, qualified referrals and tokens, as GET /v1/leaderboard/beta's description states. | | `rows[].tokens` | body | string | — | Tokens is the person's all-time token usage as a range: 0, <1M, 1M-10M, 10M-100M, 100M-1B or 1B+. | | `rows[].tokensUsed` | body | integer (int64) | — | TokensUsed is the exact count, on a named row and the caller's; absent on every other. | | `rows[].you` | body | boolean | — | You marks the caller's own row. | | `tokens` | body | boolean | — | Tokens is whether token usage was counted; false when the warehouse did not answer, and no record's score has it then. | | `you` | body | leaderboard.BetaRow | — | | | `you.applied` | body | string | — | Applied is the day the application began, 2006-01-02: the record's own, or the day of the lead it claims when that was earlier. | | `you.name` | body | string | — | Name is the handle its owner listed under on the public board; null for a person who did not opt in, whom the page calls a builder. | | `you.qualified` | body | integer (int64) | — | Qualified is how many of them have made metered spend. | | `you.rank` | body | integer (int64) | — | Rank is the record's place, 1 first. | | `you.referrals` | body | integer (int64) | — | Referrals is how many orgs signed up with the record's referral code. | | `you.score` | body | integer (int64) | — | Score is what the row is ranked by: points, referrals, qualified referrals and tokens, as GET /v1/leaderboard/beta's description states. | | `you.tokens` | body | string | — | Tokens is the person's all-time token usage as a range: 0, <1M, 1M-10M, 10M-100M, 100M-1B or 1B+. | | `you.tokensUsed` | body | integer (int64) | — | TokensUsed is the exact count, on a named row and the caller's; absent on every other. | | `you.you` | body | boolean | — | You marks the caller's own row. | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** ```bash hanzo leaderboard beta ``` **SDK** **.ts** ```ts import { Configuration, LeaderboardApi } from 'hanzoai'; const api = new LeaderboardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.getLeaderboardBeta(); ``` **.py** ```python from hanzoai.cloud import ApiClient, Configuration from hanzoai.cloud.api import LeaderboardApi client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"])) result = LeaderboardApi(client).get_leaderboard_beta() ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.LeaderboardAPI.GetLeaderboardBeta(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust use hanzo_client::apis::{configuration::Configuration, leaderboard_api}; let mut cfg = Configuration::new(); cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok(); let result = leaderboard_api::get_leaderboard_beta(&cfg, Default::default()).await?; ``` **.java** ```java import ai.hanzo.cloud.ApiClient; import ai.hanzo.cloud.api.LeaderboardApi; ApiClient client = new ApiClient(); client.setBearerToken(System.getenv("HANZO_API_KEY")); var result = new LeaderboardApi(client).getLeaderboardBeta(); ``` **HTTP** ```bash curl https://api.hanzo.ai/v1/leaderboard/beta \ -H "Authorization: Bearer $HANZO_API_KEY" ``` **MCP** Tool `leaderboard`, op `get_leaderboard_beta` — POST the JSON-RPC envelope to `https://api.hanzo.ai/v1/mcp`. ```bash 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_leaderboard_beta", "input": {} } } }' ``` --- [Leaderboard API](https://docs.hanzo.ai/docs/openapi/leaderboard) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)