Hanzo Docs
Sign inAPI key

Create check

Reads the stars, follows and forks of the GitHub account you linked at sign-in, from GitHub's API, and puts to staff each that is a repository or account of ours, once each.

POST /v1/reward/me/github/check

Reward → · All API references → · Get started →

Addresshttps://api.hanzo.ai/v1/reward/me/github/check
MethodPOST
Operationpost_reward_me_github_check
AuthAuthorization: Bearer $HANZO_API_KEY

Reads the stars, follows and forks of the GitHub account you linked at sign-in, from GitHub's API, and puts to staff each that is a repository or account of ours, once each. Asked at most twice an hour.

Request

The document declares no body for POST /v1/reward/me/github/check. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_reward_me_github_check, which answers from the running route.

Response

StatusBodyMeaning
200reward.checkOutok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
followsbodyinteger (int64)—
forksbodyinteger (int64)—
loginbodystring—Login is the GitHub account the caller linked.
starsbodyinteger (int64)—Stars, Follows and Forks are the claims this check made, each for one repository or account of ours that GitHub shows the caller has starred, followed or forked, and nobody had claimed before.

Failure carries the platform error shape — see Errors.

Examples

hanzo reward me github check
import { Configuration, RewardApi } from 'hanzoai';

const api = new RewardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postRewardMeGithubCheck();
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).post_reward_me_github_check()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.RewardAPI.PostRewardMeGithubCheck(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::post_reward_me_github_check(&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).postRewardMeGithubCheck();

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 -X POST https://api.hanzo.ai/v1/reward/me/github/check \
  -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"
         }
       }
     }'

Reward API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.
PreviousCreate badgeNextCreate recheck