Template

A gallery of starter kits you can deploy as they come.

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

A gallery of starter kits you can deploy as they come.

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

Specification

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

CLI

SDK

HTTP

MCP

hanzo template list

.ts

.py

.go

.rs

.java

import { Configuration, TemplateApi } from 'hanzoai';

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

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TemplateApi(client).get_template()

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

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

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

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

let result = template_api::get_template(&cfg, Default::default()).await?;

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

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

var result = new TemplateApi(client).getTemplate();

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

MCP reaches template through the template tool, which names its 5 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": "list_templates"
         }
       }
     }'

Answers 200 with object — ok.

Endpoints

Endpoint	What it does
`GET /v1/template/{slug}`	Returns one starter kit: the caller org's own by that slug, else the public catalog's.
`PUT /v1/template/{slug}`	Overwrites the caller org's OWN starter kit at the path slug, answering the stored kit.
`DELETE /v1/template/{slug}`	Deletes the caller org's OWN starter kit.
`GET /v1/template`	Lists the public starter-kit catalog plus, for a validated caller, that org's own private kits.
`POST /v1/template`	Creates a starter kit PRIVATE to the caller's org and answers 201 with the stored kit.

All Hanzo APIs · Interactive reference

Was this page useful?

PreviousGit NextBlueprint