Prompt Registry
Version-controlled prompt templates with namespace organization, variable rendering, and caching for production performance.
Enterprise feature
The prompt registry requires an Enterprise plan.
Overview
The prompt registry lets you manage prompt templates centrally instead of embedding them in application code. Every change creates a new immutable version with a full audit trail.
- Namespaces: organize prompts by team or domain (
billing/invoice-parser) - Versioning: every update creates a new version; old versions are preserved
- Templates: use
{{variable}}placeholders rendered at request time - Caching: read-through cache with write-through invalidation
Create a Prompt
bash
curl -X POST https://api.ingateai.com/api/prompts \
-H "Content-Type: application/json" \
-H "X-Ingate-Key: sk-ingate-your-key" \
-d '{
"namespace": "support",
"slug": "ticket-classifier",
"content": "Classify this support ticket into one of: {{categories}}.\n\nTicket: {{ticket_text}}\n\nCategory:"
}'Get a Prompt
bash
# Latest version
curl https://api.ingateai.com/api/prompts/support/ticket-classifier
# Specific version
curl https://api.ingateai.com/api/prompts/support/ticket-classifier?version=2Update a Prompt
Updates create a new version; the previous version is preserved:
bash
curl -X PUT https://api.ingateai.com/api/prompts/support/ticket-classifier \
-H "Content-Type: application/json" \
-H "X-Ingate-Key: sk-ingate-your-key" \
-d '{
"content": "You are a support ticket classifier.\n\nCategories: {{categories}}\n\nTicket: {{ticket_text}}\n\nRespond with only the category name."
}'Render a Template
Render a prompt with variables without sending it to an LLM:
bash
curl -X POST https://api.ingateai.com/api/prompts/support/ticket-classifier/render \
-H "Content-Type: application/json" \
-H "X-Ingate-Key: sk-ingate-your-key" \
-d '{
"variables": {
"categories": "billing, technical, account, general",
"ticket_text": "I can\'t log in to my account since yesterday"
}
}'Version History
bash
curl https://api.ingateai.com/api/prompts/support/ticket-classifier/versionsWhy Centralized Prompts?
Key benefits
- No redeploys: update prompts without shipping application code
- Audit trail: every change is versioned and immutable
- Consistency: all services consume the same prompt definitions
- A/B testing: pin specific versions per environment
- Rollback: instantly revert to any previous version