Hanzo
Cloud MCPauthors

post_v1_authors_deploys_record

RecordAuthorDeploy records that the caller's org deployed a project built from a source repository, which is the edge that makes an author's work earn royalty.

RecordAuthorDeploy records that the caller's org deployed a project built from a source repository, which is the edge that makes an author's work earn royalty.

It is deliberately NOT an error for a deploy to attribute to nobody: a project built from no repository, or from one no author has verified, answers {"recorded": false, "reason"} so a deploy pipeline can fire this on every deploy without branching. Attribution resolves per-repository first, then owner-wide, so a repository with its own claim always earns for its own author.

A deploy of a Hanzo-maintained template attributes to the platform treasury, and a self-deploy (the author's own org deploying its own repository) is recorded for provenance but excluded from accrual. The edge is idempotent per repository+project+org.

Answers 201 when it recorded a new edge and 200 otherwise.

Toolpost_v1_authors_deploys_record
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments2
OperationPOST /v1/authors/deploys/record
Productauthors

Arguments

FieldTypeRequiredDefaultValuesDescription
projectstringProject is the deployed project's id. Required.
repoUrlstringRepoURL is the source repository the project was built from. Empty means a hand-built project with nothing to attribute — an honest no-op, not an error.

tools/list declares a type and a description for each field and nothing further. A means neither the door nor that operation constrains the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

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_authors_deploys_record",
         "arguments": {
           "project": "<project>",
           "repoUrl": "<repoUrl>"
         }
       }
     }'

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

OperationRouteProductSummary
cloud_post_v1_authors_deploys_recordPOST /v1/authors/deploys/recordauthorsRecordAuthorDeploy records that the caller's org deployed a project built from a source…

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


All 833 tools · The door · API reference

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

How is this guide?

On this page