Catalog returns the read-only starter prompt library shipped with the binary —…
Catalog returns the read-only starter prompt library shipped with the binary — reference content every tenant sees the same, NOT the caller's own prompts…
GET /v1/prompt/catalog
| Address | https://api.hanzo.ai/v1/prompt/catalog |
| Method | GET |
| Operation | get_prompt_catalog |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Catalog returns the read-only starter prompt library shipped with the binary — reference content every tenant sees the same, NOT the caller's own prompts and never mixed into them. An org's library stays honestly empty until someone explicitly imports a starter, which is an ordinary POST /v1/prompt. Entries that would fail the create guards are dropped, so everything offered here can actually be imported.
Request
GET /v1/prompt/catalog takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | catalogList | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | CatalogEntry[] | — | Data is every starter prompt, each importable as-is with POST /v1/prompt. |
data[].labels | body | string[] | — | Labels is the starter's second suggested taxonomy, same treatment as Tags. |
data[].name | body | string | — | Name is the starter's suggested handle. It is NOT taken in your org: the catalog is shared reference content, so this name is free until you import it, and… |
data[].prompt | body | string | — | Prompt is the starter's full template body, ready to POST as-is. |
data[].tags | body | string[] | — | Tags is the starter's suggested taxonomy, carried through unchanged if you import it. |
data[].type | body | string | — | Type labels the template's kind, defaulted to "text" for entries that declare none. |
Failure carries the platform error shape — see Errors.
Examples
hanzo prompts catalogimport { Configuration, PromptApi } from 'hanzoai';
const api = new PromptApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPromptCatalog();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PromptApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PromptApi(client).get_prompt_catalog()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PromptAPI.GetPromptCatalog(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, prompt_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = prompt_api::get_prompt_catalog(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PromptApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new PromptApi(client).getPromptCatalog();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/prompt/catalog \
-H "Authorization: Bearer $HANZO_API_KEY"Tool prompts, op get_prompt_catalog — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "prompts",
"arguments": {
"op": "get_prompt_catalog",
"input": {}
}
}
}'How is this guide?