Prompt management
Keeping the prompts an application sends to a model as templates with placeholders, stored and versioned apart from the code that calls them, so a change of wording is not a deployment. What people conflate under it: the template filled at runtime, the registry it lives in, and the orchestration step that fills it.
Overview
SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp carries both halves: templating as a module of its orchestration service, and the Prompt Registry, where a template is stored and versioned and then referenced from an orchestration call.
Not covered: At the template. What a prompt should say, and whether it still behaves after a model change, is not in the service; that question sits with agent evalsAgent evalsKnowing whether an AI feature still behaves after a model, prompt or schema change. Regression testing for non-deterministic output, against fixtures that reflect real business data.SAP and community, unassessed.
No community artifact is documented here.
@sap-ai-sdk/prompt-registry@sap-ai-sdk/prompt-registryA package for keeping prompts in SAP's prompt registry rather than in the codebase, so changing a prompt is not a deployment.sap official, cap is the client for the registry and @sap-ai-sdk/orchestration@sap-ai-sdk/orchestrationThe Orchestration Service client of SAP's AI SDK, which applies templating, grounding, filtering and masking around a model call rather than in the application.sap official, cap fills a template at call time; nothing in @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap knows what a prompt is.
Not covered: At the SDK call. The template is filled in the service; where it is stored, who may change it and how a change is reviewed are the registry's, on the BTP door.
A prompt registry inside the application: cds-plugin-llm@saptarishi/cds-plugin-llmA CAP service kind that puts eleven model providers behind one chat, stream, embed and batch interface, so which backend a service calls is a profile in package.json rather than a change to the handler.independent, cap registers templates by name for CAP handlers, can load them from a Git repository so a wording change goes through pull request review, and pins which version a call gets.
Artifacts
Content
Seen working
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Details
Coverage
For your agent
- Ref
capability:prompt-management- JSON
- /capabilities/prompt-management.json
- MCP
- Connecting an agent