List me
Reads the signed-in person's standing in each program from the append-only ledger: lifetime points (which levels and rank read, and which never fall), the part of them that is redeemable, the level and the next one, and the badges held.
GET /v1/reward/me
| Address | https://api.hanzo.ai/v1/reward/me |
| Method | GET |
| Operation | get_reward_me |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Reads the signed-in person's standing in each program from the append-only ledger: lifetime points (which levels and rank read, and which never fall), the part of them that is redeemable, the level and the next one, and the badges held.
Request
GET /v1/reward/me takes no parameters and no body — the credential is the whole request.
Response
The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.
Examples
hanzo reward me getimport { Configuration, RewardApi } from 'hanzoai';
const api = new RewardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getRewardMe();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import RewardApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = RewardApi(client).get_reward_me()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.RewardAPI.GetRewardMe(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, reward_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = reward_api::get_reward_me(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.RewardApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new RewardApi(client).getRewardMe();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/reward/me \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches reward through the reward tool, which names its 7 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_reward_me_posts"
}
}
}'