Ci

Mounts the CI fleet dashboard as a capability of this binary.

Also for this capability: API · CLI · MCP · SDKs

Mounts the CI fleet dashboard as a capability of this binary.

Base URL	`https://api.hanzo.ai`
Operations	2
Auth	`Authorization: Bearer $HANZO_API_KEY`

Specification

Specification pending — no HIP in hanzoai/hips declares capability: ci 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	`ci` at its own prefix	2 operations
CLI	`hanzo ci …`	2 of 2
SDK	`CiApi` in every published client	2 methods
MCP	tool `ci` on `https://api.hanzo.ai/v1/mcp`	2 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/ci/runs, operation get_ci_runs:

CLI

SDK

HTTP

MCP

hanzo ci runs

.ts

.py

.go

.rs

.java

import { Configuration, CiApi } from 'hanzoai';

const api = new CiApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getCiRuns();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import CiApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = CiApi(client).get_ci_runs()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CiAPI.GetCiRuns(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, ci_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = ci_api::get_ci_runs(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CiApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new CiApi(client).getCiRuns();

curl https://api.hanzo.ai/v1/ci/runs \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches ci through the ci tool, which names its 2 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_ci_fleet"
         }
       }
     }'

Answers 200 with object — ok.

Endpoints

Endpoint	What it does
`GET /v1/ci/fleet`	Compares what was written with what is running, one row per service along a single causal line: head, the commit on the branch; built, the image that commit produced; declared, the tag pinned in the universe repository; running, what the cluster serves.
`GET /v1/ci/runs`	Lists recent builds: the repo, the branch, the commit and how each run ended, newest first.

All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCompute NextNode