Hanzo

Prompt

Package prompts is your prompt library, versioned, so nothing changes silently.

Package prompts is your prompt library, versioned, so nothing changes silently.

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

Specification

Specification pending — no HIP in hanzoai/hips declares capability: prompt 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
RESTprompt at its own prefix6 operations
CLIhanzo prompts …6 of 6
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool prompts on https://api.hanzo.ai/v1/mcp6 operations, 2 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/prompt, operation get_prompt:

hanzo prompts list

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/prompt/{name}Get returns one of the caller org's prompts: its CURRENT template text plus the metadata of every version it has had.
DELETE /v1/prompt/{name}Delete removes one of the caller org's prompts and every version of it, answering 204.
GET /v1/prompt/catalogCatalog returns the read-only starter prompt library shipped with the binary — reference content every tenant sees the same, NOT the caller's own…
GET /v1/prompt/metricsMetrics returns real per-prompt statistics for the caller's org: how many versions each prompt has, which one is current, and when it was created and…
GET /v1/promptList returns the caller org's prompt library as one row per prompt: its name, type, every version number it has, its taxonomy and when it last…
POST /v1/promptCreate records a prompt for the caller's org and answers 201 with it.

All Hanzo APIs · Interactive reference

How is this guide?

On this page