Hanzo AI

Task

Hanzo Task: boards, the work items on them, and the filters that make a board.

Also for this capability: API · CLI · SDKs

Hanzo Task: boards, the work items on them, and the filters that make a board.

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

Specification

Specification pending — no HIP in hanzoai/hips declares capability: task 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
RESTtask at its own prefix13 operations
CLIhanzo task …13 of 13
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool tasks on https://api.hanzo.ai/v1/mcp20 operations, 0 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/task/board, operation get_task_board:

hanzo task board

Answers 200 with task.issueView[] — ok.

Endpoints

EndpointWhat it does
GET /v1/task/boardReturns a board's issues — work items with their column, priority, assignee, labels and schedule.
GET /v1/task/issuesAnswers across every project in the org.
POST /v1/task/projects/{key}/issues/{num}/claimTakes an issue: it becomes yours and it moves to in_progress.
GET /v1/task/projects/{key}/issues/{num}Returns ONE work item in full — its description included.
PATCH /v1/task/projects/{key}/issues/{num}Edits a work item — rename it, rewrite it, move it to another column, or re-prioritise it.
GET /v1/task/projects/{key}/issuesReturns a board's issues — work items with their column, priority, assignee, labels and schedule.
POST /v1/task/projects/{key}/issuesOpens a work item on the board — an issue on that repository on the deployment's forge, filed as YOU.
GET /v1/task/projects/{key}Returns one board of your org by its key — the repository name.
PATCH /v1/task/projects/{key}Refused — a board is a repository on the forge
DELETE /v1/task/projects/{key}Refused — a board is a repository on the forge
GET /v1/task/projectsReturns the boards of your org — the places your work actually is.
POST /v1/task/projectsRefused — a board is a repository on the forge
GET /v1/task/rooms/{room}Summarises one room's work.

All Hanzo APIs · Interactive reference

How is this guide?