List recharge

Reads the caller's auto-reload rule: top the balance up by `amountCents` whenever it falls below `thresholdCents`, charging the card on file off-session.

GET /v1/billing/recharge

Billing → · All API references → · Get started →


Address	`https://api.hanzo.ai/v1/billing/recharge`
Method	`GET`
Operation	`get_billing_recharge`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Reads the caller's auto-reload rule: top the balance up by amountCents whenever it falls below thresholdCents, charging the card on file off-session. It is the same setting every prepaid AI account calls auto-reload.

An org that has never set one reads as disabled with zeroes rather than as an error — "no rule" answers the question — and stored is how a caller tells never-configured from deliberately-off.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

GET /v1/billing/recharge takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	billing.AutoRecharge	ok
`default`	problem-details	refused

200 body — 7 fields.

Field	In	Type	Always
`amountCents`	body	integer (int64)	—
`currency`	body	string	—
`enabled`	body	boolean	—
`lastRechargedAt`	body	string	—
`stored`	body	boolean	—
`subject`	body	string	—
`thresholdCents`	body	integer (int64)	—

Failure carries the platform error shape — see Errors.

Examples

hanzo billing recharge get

import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingRecharge();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BillingApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BillingApi(client).get_billing_recharge()

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

resp, _, err := client.BillingAPI.GetBillingRecharge(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, billing_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = billing_api::get_billing_recharge(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new BillingApi(client).getBillingRecharge();

curl https://api.hanzo.ai/v1/billing/recharge \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches billing through the billing tool, which names its 9 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": "get_billing_balance"
         }
       }
     }'

Billing API · All Hanzo APIs · Interactive reference

Request

Response

Examples

On this page