Your repository runs, and you are paid

1. Connect your GitHub account with POST /v1/author/connect.
2. Prove you own a repository, or a whole owner, with POST /v1/author/repos/verify: through a linked GitHub account that can push to it, or a hanzo.json on its default branch carrying your verify code.
3. When an org deploys a project built from that repository, the deploy is recorded against it.
4. Each period, you accrue 20% of that org’s metered spend — once per org per period, and never from your own org.
5. Payouts are recorded against what has accrued, and settled by a person.

Repositories Hanzo maintains earn the same 20% when other orgs deploy them, recorded to Hanzo’s own account.

GET /v1/author answers your verified repositories, the deploys recorded against them, and what has accrued, is pending and has been paid. GET /v1/author/basis is the audit trail: every ledger row, the spend it was computed from and the share applied.

Referring customers is a separate programme, paid on Hanzo’s margin: see affiliates. Open issues scoped for an outside fix are the bounties. Everything Hanzo publishes is on the open source page.