post_v1_authors_connect
ConnectAuthor enrols the caller's org in the author program at status "connected" and returns its enrolment, including the verify code the file method needs.
ConnectAuthor enrols the caller's org in the author program at status "connected" and returns its enrolment, including the verify code the file method needs. It is IDEMPOTENT: a second call returns the same enrolment rather than a conflict.
The forge login is taken from IAM's LINKED account for the provider when there is one — that is identity proof, not a claim — and only otherwise from the login in the body, which then has to be proven per repository. Connecting does not admit an org to earning: a platform reviewer approves that separately.
Answers 201 when it enrolled the org and 200 when it found an existing enrolment.
| Tool | post_v1_authors_connect |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/authors/connect |
| Product | authors |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
githubLogin | string | — | — | — | GithubLogin is the account to link. Used only when IAM holds no linked account for the provider — a linked account is stronger proof and always wins. |
login | string | — | — | — | Login is the provider-neutral alias for GithubLogin, preferred when both are sent. |
provider | string | — | — | — | Provider is the forge to enrol with: github (the default) or gitlab. |
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_connect",
"arguments": {
"githubLogin": "<githubLogin>",
"login": "<login>",
"provider": "<provider>"
}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_post_v1_authors_connect | POST /v1/authors/connect | authors | ConnectAuthor enrols the caller's org in the author program at status "connected" and… |
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?
get_v1_authors_basis
MyRoyaltyBasis returns 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 platform's matching half, whether each…
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.