Returns the ledger accounts the caller may see, with their balances.

GET /v1/treasury/accounts

Treasury → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/treasury/accounts`
Method	`GET`
Operation	`get_treasury_accounts`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the ledger accounts the caller may see, with their balances. It is tenant-isolated SERVER-SIDE: an ordinary caller sees ONLY accounts under its own "org:<tenant>:" prefix, never house accounts and never another tenant's. A SuperAdmin may widen with ?scope=house (the reserve, revenue and payout house accounts) or ?org=<tenant> — the only way to cross the tenant boundary, and only for platform sudo. The answer is honestly empty until a tenant has ledger postings.

Request

2 fields.

Field	In	Type	Required	Description
`scope`	query	string	—	Scope is "house" to read the reserve/revenue/payout house accounts.
`org`	query	string	—	Org names another tenant to read.

Response

Status	Body	Meaning
`200`	accountsOut	ok

200 body — 5 fields.

Field	In	Type	Always	Description
`accounts`	body	accountView[]	—	Accounts are the ledger accounts in scope with their balances.
`accounts[].address`	body	string	—	Address is the ledger account address ("org:acme:wallet", "fund:reserve", …).
`accounts[].balanceCents`	body	integer	—	BalanceCents is that account's signed balance in minor units.
`scope`	body	string	—	Scope is the scope actually served: "org" or "house".
`tenant`	body	string	—	Tenant is the org whose accounts these are (empty for the house scope's own rows).

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

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_accounts()

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

resp, _, err := client.TreasuryAPI.GetTreasuryAccounts(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_accounts(&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).getTreasuryAccounts();

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/accounts \
  -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"
         }
       }
     }'

Treasury API · All Hanzo APIs · Interactive reference

Returns the ledger accounts the caller may see, with their balances.

Request

Response

Examples

On this page