Workflow
Hanzo Workflow: durable workflows that survive a crash, with every run visible and replayable.
Also for this capability: API · CLI · SDKs
Hanzo Workflow: durable workflows that survive a crash, with every run visible and replayable.
| Base URL | https://api.hanzo.ai |
| Operations | 5 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Specification
Specification pending — no HIP in hanzoai/hips declares capability: workflow 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
| Surface | Reaches this capability as | Coverage |
|---|---|---|
| REST | workflow at its own prefix | 5 operations |
| CLI | hanzo workflow … | 5 of 5 |
| SDK | — | no published client declares one yet — regenerating the clients is what adds them |
| MCP | — | no tool names it yet — use HTTP or an SDK |
Quickstart
export HANZO_API_KEY=sk-... # console.hanzo.ai → API keysThen the first call — a read that needs nothing but the key. GET /v1/workflow, operation get_workflow:
hanzo workflow getimport { Configuration, WorkflowApi } from 'hanzoai';
const api = new WorkflowApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getWorkflow();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import WorkflowApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = WorkflowApi(client).get_workflow()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.WorkflowAPI.GetWorkflow(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, workflow_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = workflow_api::get_workflow(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.WorkflowApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new WorkflowApi(client).getWorkflow();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/workflow \
-H "Authorization: Bearer $HANZO_API_KEY"MCP declares no tool for workflow — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
Endpoints
| Endpoint | What it does |
|---|---|
GET /v1/workflow | Redirect to the workflow API root |
POST /v1/workflow | Redirect to the workflow API root |
PUT /v1/workflow | Redirect to the workflow API root |
PATCH /v1/workflow | Redirect to the workflow API root |
DELETE /v1/workflow | Redirect to the workflow API root |
How is this guide?