post_v1_admin_authors_id_payout

PayAuthor records a payout of accrued royalty and settles it.

The amount is RESERVED against the author's pending royalty atomically before anything is paid, so a payout can never exceed what is owed even under concurrent calls. An external author's payout is then BACKED against the platform reserve fund — a second, independent guard — and refused with 402 if the reserve cannot cover it, with the reservation voided. A "credits" method issues the actual wallet grant after both guards; a cash method is record-only. A first-party (treasury) author's royalty is realized into Hanzo's own reserve instead of an external wallet, and every payout row discloses which of the three it was.

A Hanzo platform operation: a caller who is not a SuperAdmin gets 403.


Tool	`post_v1_admin_authors_id_payout`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	4
Operation	`POST /v1/admin/authors/{id}/payout`
Product	cloud

Arguments

Field	Type	Required	Default	Description
`amountCents`	`integer`	—	—	AmountCents is how much to pay, in cents. Must be positive and can never exceed the author's pending royalty (accrued minus paid).
`id`	`string`	—	—	ID is the author to pay, from the path.
`method`	`string`	—	—	Method is how it settles: "credits" issues a grant into the author's wallet; wire, paypal and the like are record-only. Required.
`reference`	`string`	—	—	Reference is the operator's external reference for a cash settlement — a wire confirmation, a PayPal transaction id.

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": "post_v1_admin_authors_id_payout",
         "arguments": {
           "amountCents": 0,
           "id": "<id>",
           "method": "<method>",
           "reference": "<reference>"
         }
       }
     }'

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_post_v1_admin_authors_id_payout`	`POST /v1/admin/authors/{id}/payout`	cloud	PayAuthor records a payout of accrued royalty and settles it.

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).

post_v1_admin_authors_id_payout

Arguments

Call it

The operation behind it

On this page