Hanzo

Author

Package authors is a royalty for open-source work: your repo runs, you get paid.

Package authors is a royalty for open-source work: your repo runs, you get paid.

Base URLhttps://api.hanzo.ai
Operations5
AuthAuthorization: Bearer $HANZO_API_KEY

Specification

Specification pending — no HIP in hanzoai/hips declares capability: author yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.

Four surfaces

SurfaceReaches this capability asCoverage
RESTauthor at its own prefix5 operations
CLIhanzo authors …5 of 5
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool authors on https://api.hanzo.ai/v1/mcp11 operations, 1 under the document's own id — ask describe for the rest

Quickstart

export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/author, operation get_author:

hanzo authors get

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/author/basisReturns the AUDIT TRAIL behind the caller's own royalty: every ledger row with the spend it was computed from, the share applied at the time, the…
POST /v1/author/connectEnrols the caller's org in the author program at status "connected" and returns its enrolment, including the verify code the file method needs.
POST /v1/author/deploys/recordRecords 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.
POST /v1/author/repos/verifyProves that the caller owns a repository — or a whole OWNER — and records the claim, which is what makes deploys of that code earn royalty.
GET /v1/authorReturns the caller's author-program dashboard: enrolment status, linked forge login, verified repositories and owner-wide claims, recorded deploys,…

All Hanzo APIs · Interactive reference

How is this guide?

On this page