Create mode

Moves this org between sandbox money and real money.

POST /v1/billing/mode

Billing → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/billing/mode`
Method	`POST`
Operation	`post_billing_mode`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Moves this org between sandbox money and real money.

It decides whether a charge hits a real card, so it is the one posture change that is not self-service: the platform bar, never an org owner, because an org that could put itself in test mode could take priced work for free.

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

Request

1 field, body application/json (required).

Field	In	Type	Required	Description
`testMode`	body	boolean	—

Response

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

200 body — 4 fields.

Field	In	Type	Always
`live`	body	boolean	—
`orgId`	body	string	—
`orgName`	body	string	—
`testMode`	body	boolean	—

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo billing mode

.ts

.py

.go

.rs

.java

import { Configuration, BillingApi } from 'hanzoai';

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

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).post_billing_mode(test_mode=False)

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

resp, _, err := client.BillingAPI.PostBillingMode(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::post_billing_mode(&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).postBillingMode();

curl -X POST https://api.hanzo.ai/v1/billing/mode \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "testMode": false
     }'

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

Billing API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate methods — POST /v1/billing/methods NextCreate methods — POST /v1/billing/portal/methods