Concepts

Prompt registry

Store, version, and label prompts server-side, then reference them by name instead of shipping templates in your app.

Store, version, and label prompts server-side, then reference them by name instead of shipping template strings in your app. References take three forms: prompt_<slug> (latest), prompt_<slug>@<label> (e.g. @prod), and prompt_<slug>@v<N> (a pinned version).

EndpointWhat it does
GET /v1/prompts/{ref}Fetch a stored version, no rendering, no upstream call.
POST /v1/prompts/{ref}/renderServer-side render (mustache-style), no upstream call.
POST /v1/prompts/{ref}/completionsRender and run through the full chat pipeline.
The prompt registry requires the prompt_registry entitlement (Standard plan and above). Without it these endpoints return 403 feature_not_entitled.