Billing
billing: 39 operations.
Also for this capability: API · CLI · MCP · SDKs
billing: 39 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | billing |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | POST /v1/billing/subscriptions/{id}/cancel · POST /v1/billing/invoices/{id}/collect · GET /v1/billing/invoices/{id} · GET /v1/billing/ledger · GET /v1/billing/recharge · GET /v1/billing/tier · GET /v1/billing/usage/rollup · GET /v1/billing/wire · POST /v1/billing/invoices/{id}/issue · POST /v1/billing/invoices · POST /v1/billing/subscriptions/{id}/reactivate · POST /v1/billing/invoices/{id}/void |
| Product | billing |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "billing",
"arguments": {
"op": "list_billing_accounts"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
billing dispatches to 39 operations. 12 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
cancelSubscription | POST /v1/billing/subscriptions/{id}/cancel | billing | End a subscription |
collectInvoice | POST /v1/billing/invoices/{id}/collect | billing | Collect an issued invoice from credits, balance, then card |
getInvoice | GET /v1/billing/invoices/{id} | billing | Read one invoice |
get_billing_ledger | GET /v1/billing/ledger | billing | Answers the org's own postings inside range=, each as a signed entry: a DEPOSIT CREDITS the wallet (positive, account credits:<org>), a HOLD sets money aside for a payment agreed and not yet made (negative, account held:<org>) and its return gives it back (positive), and every other posting DEBITS it (negative, account usage:<org>), described by its notes or its tags. |
get_billing_recharge | GET /v1/billing/recharge | billing | 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_billing_tier | GET /v1/billing/tier | billing | Answers which tier the caller is on, what it allows, and what is left to spend. |
get_billing_usage_rollup | GET /v1/billing/usage/rollup | billing | Answers the caller's month: what their plan includes, what has been consumed against it, and the wallet beside it. |
get_billing_wire | GET /v1/billing/wire | billing | Answers where to send a wire top-up: the receiving bank details, with the caller's own payment reference. |
issueInvoice | POST /v1/billing/invoices/{id}/issue | billing | Issue a draft invoice, making it collectible |
raiseInvoice | POST /v1/billing/invoices | billing | Raise a draft invoice against a customer |
reactivateSubscription | POST /v1/billing/subscriptions/{id}/reactivate | billing | Put a canceled subscription back on its plan |
voidInvoice | POST /v1/billing/invoices/{id}/void | billing | Void a draft or issued invoice |
The same capability over plain HTTP is in the billing API reference, on https://api.hanzo.ai.
All 120 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.