Add the Docs MCP to your AI coding tool to get help building with Respan. No API key needed.
Prompt management lets you create, version, and deploy prompt templates centrally — instead of hardcoding prompts in your application, reference them by ID.
Before you begin, make sure you have:
Go to the Prompts page and click Create new prompt. Name your prompt and add a description.

In the Editor tab, set parameters like model, temperature, max tokens, and top P in the right sidebar.

Click + Add message to add messages. Use {{variable_name}} for dynamic content — see Variables for Jinja templates, JSON inputs, and more.
Variable names must use underscores: {{task_description}} not {{task description}}.

Avoid “Commit + deploy” unless you want changes to go live immediately.

Go to the Deployments tab and click Deploy. See Deployment & versioning for version pinning, rollbacks, and overrides.
Deploying immediately affects production. All API calls using this prompt will use the new version right away.

Find the Prompt ID in the Overview panel on the Prompts page.
Then call it from your application using prompt schema v2 (recommended):
OpenAI SDKs strip v2 fields like schema_version and patch. Prompt schema v2 requires raw HTTP requests.
You don’t need model and messages — the prompt configuration is used automatically.
With v1, use override: true to let the prompt config win over request-body parameters. This is the default when schema_version is omitted.
See Prompt merge modes (v1 vs v2) for full details.
Filter logs by prompt name on the Logs page to track usage, response times, and token consumption. See Prompt logging for logging setup.