Replace org

Sets the ORG's listing on the cross-org global board.

PUT /v1/leaderboard/optin/org

Leaderboard → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/leaderboard/optin/org`
Method	`PUT`
Operation	`put_leaderboard_optin_org`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Sets the ORG's listing on the cross-org global board. Only an admin of the caller's own org — an org admin or a platform SuperAdmin — may change it, and the org written is the caller's validated tenant, never a value from the request. Listing consents to publishing the org's usage VOLUME; cross-org spend stays restricted to platform admins regardless.

Request

2 fields, body application/json (required).

Field	In	Type	Required	Description
`display`	body	string	—	Display is the name shown for the org on that board: 1-40 characters of letters, digits, space, dot, underscore, apostrophe or hyphen.
`listed`	body	boolean	—	Listed publishes the org on the cross-org global board when true, and withdraws it when false.

Response

Status	Body	Meaning
`200`	leaderboard.orgOptinView	ok
`default`	problem-details	refused

200 body — 3 fields.

Field	In	Type	Always	Description
`canManage`	body	boolean	—	CanManage is true only for an admin of this org (or a platform SuperAdmin) — the callers whose write of the org preference will be accepted.
`display`	body	string	—	Display is the name shown for the org on that board.
`listed`	body	boolean	—	Listed is true when the org has opted onto the cross-org global board.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo leaderboard optin org

.ts

.py

.go

.rs

.java

import { Configuration, LeaderboardApi } from 'hanzoai';

const api = new LeaderboardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putLeaderboardOptinOrg({ display: "<display>", listed: false });

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).put_leaderboard_optin_org(display="<display>", listed=False)

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.LeaderboardAPI.PutLeaderboardOptinOrg(context.Background()).Execute()
if err != nil {
	return err
}

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::put_leaderboard_optin_org(&cfg, Default::default()).await?;

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).putLeaderboardOptinOrg();

curl -X PUT https://api.hanzo.ai/v1/leaderboard/optin/org \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "display": "<display>",
       "listed": false
     }'

MCP reaches leaderboard through the leaderboard tool, which names its 5 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_leaderboards"
         }
       }
     }'

Leaderboard API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList leaderboard NextReplace optin