Returns the reserve fund's health and the current revenue-share policy for any…
Returns the reserve fund's health and the current revenue-share policy for any validated caller.
GET /v1/treasury
| Address | https://api.hanzo.ai/v1/treasury |
| Method | GET |
| Operation | get_treasury |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the reserve fund's health and the current revenue-share policy for any validated caller. It is a TRANSPARENCY view — a partner or author can see that the pool backing their payouts is solvent — and NOT per-org money, which is the customer's own commerce balance at /v1/billing/balance. The policy is read-only here; only a SuperAdmin sets it.
Request
GET /v1/treasury takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | TreasuryReport | ok |
200 body — 9 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
accruedCents | body | integer | — | lifetime revenue-share into the fund |
byProgramCents | body | object | — | program → lifetime paid |
byProgramCents.* | body | integer | — | |
paidCents | body | integer | — | lifetime backed payouts out of the fund |
policy | body | SharePolicy | — | |
policy.revenueShareBps | body | integer | — | |
policy.updatedAt | body | integer | — | |
reserveCents | body | integer | — | fund:reserve balance (available now) |
solventForPayout | body | boolean | — | reserve > 0: at least some payout is backable |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, TreasuryApi } from 'hanzoai';
const api = new TreasuryApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTreasury();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TreasuryApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TreasuryApi(client).get_treasury()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.TreasuryAPI.GetTreasury(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, treasury_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = treasury_api::get_treasury(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TreasuryApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new TreasuryApi(client).getTreasury();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/treasury \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches treasury through the treasury tool, which names its 7 operations with its own verbs — this one among them, under a name only the door 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": "get_admin_treasury"
}
}
}'How is this guide?