adminCreateCredit
Mints credit for one org. It is the ONE admin mint surface, and it does NOT mint in-process: it forwards the request to commerce's already-mint-gated POST /v1/billing/credits, authenticated by the…
Mints credit for one org. It is the ONE admin mint surface, and it does NOT mint in-process: it forwards the request to commerce's already-mint-gated POST /v1/billing/credits, authenticated by the service token and scoped to the target org, then writes one tamper-evident compliance record. Commerce stays the sole credit ledger; this is a thin, audited relay so there is exactly one place credit is created.
The body is commerce's OWN CreateCreditGrant contract, forwarded whole — every field
it carries reaches commerce. The only two this layer reads are the target org (org,
or user as the org-pool alias), which selects the namespace commerce's EdgeAuth
trusts, and idempotencyKey, which makes a double-clicked grant credit once.
A FAILED grant is audited too, with the request body attached: an attempted mint is exactly as interesting to a compliance auditor as a successful one.
| Tool | adminCreateCredit |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | none in the OpenAPI document |
| Product | — |
Arguments
This tool declares no arguments. Call it with an empty arguments object.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.
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": "adminCreateCredit",
"arguments": {}
}
}'tools/list needs no credential; tools/call does — called without one the door 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
The door exposes adminCreateCredit, but the copy of the OpenAPI document this build holds (pinned at 4e41f04ca) describes no operation for it — neither under that name nor at the route the name implies. That is either a route the document has yet to declare, or one the door has renamed since the pin. Everything on this page comes from tools/list; there is no REST reference to link to until the two agree.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?