adminIssueGrant

Issues a credit grant to any org from the operator Grants view, with the target named in the body.

Issues a credit grant to any org from the operator Grants view, with the target named in the body. It funnels through the SAME core.ApplyGrant that POST /v1/admin/customers/:org/credit uses, so there is exactly ONE credit-write path and one audit trail behind both.


Tool	`adminIssueGrant`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	6
Operation	`POST /v1/admin/grants`
Product	cloud

Arguments

Field	Type	Required	Default	Description
`amountCents`	`integer`	—	—	AmountCents is the credit, in whole cents. Must be positive and within the per-grant cap.
`currency`	`string`	—	—	Currency is the ISO code, lower-cased. Empty means usd.
`org`	`string`	—	—	Org is the tenant to credit. Required.
`reason`	`string`	—	—	Reason is the operator's justification, recorded on the audit row.
`source`	`string`	—	—	Source is the money bucket: "trial" (default) for a non-cash comp that is never refundable, or "prepaid" for real money. Anything unknown falls back to trial.
`user`	`string`	—	—	User optionally names a MEMBER to credit, by bare IAM username. Empty credits the org. Which of the two the money actually lands on is decided by account.Payer, not here: a pooled org keeps one balance whatever is named.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

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": "adminIssueGrant",
         "arguments": {
           "amountCents": 0,
           "currency": "<currency>",
           "org": "<org>",
           "reason": "<reason>",
           "source": "<source>",
           "user": "<user>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. 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

Operation	Route	Product	Summary
`cloud_adminIssueGrant`	`POST /v1/admin/grants`	cloud	Issues a credit grant to any org from the operator Grants view, with the target named in t

The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.

All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

Arguments

Call it

The operation behind it

On this page