Finance
Finance — 8 operations on https://api.hanzo.ai.
The REST reference for Finance — 8 operations, generated from the OpenAPI document.
| Base URL | https://api.hanzo.ai |
| Operations | 8 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
finance
ListFinanceAccounts returns the ledger accounts the caller may see, with their balances.
GET /v1/finance/accounts
ListFinanceAccounts 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.
| Parameter | 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. |
get_v1_finance_balance
GET /v1/finance/balance
get_v1_finance_credits
GET /v1/finance/credits
get_v1_finance_invoices
GET /v1/finance/invoices
get_v1_finance_ledger
GET /v1/finance/ledger
get_v1_finance_payment-methods
GET /v1/finance/payment-methods
GetTreasury returns the reserve fund's health and the current revenue-share policy for any validated caller.
GET /v1/finance/treasury
GetTreasury 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.
get_v1_finance_usage
GET /v1/finance/usage
How is this guide?