SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

SAP BTP AI Best Practice Demo - Prompt Registry - CAP

A CAP backend-sample and fullstack-sample that create, use and delete a template in SAP AI Core's Prompt Registry instead of embedding the prompt in code.

createPromptTemplate registers a named askCapitalOfCountry template under an ai-best-practices scenario, askCapitalOfCountry answers from that template, and deletePromptTemplate removes it again: three CDS actions split across a prompt-registry and an orchestration service, implemented, the README says, with the SAP AI SDK, and @sap-ai-sdk/prompt-registry and @sap-ai-sdk/orchestration are in the fullstack-sample's dependencies. The fullstack-sample pairs the same services with a UI5 app under app/ask-capital, and its README notes the create step has to run first or the app has no template to query. Both bind to a SAP AI Core service instance with cds bind.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Prompt managementBTPCAPPrompt managementcapabilityKeeping 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.
Serves
Flavors
Requires
SAP AI CoreSAP AI CoreartifactThe service instance the samples bind to at runtime, which also holds the Prompt Registry template that the CDS actions create, resolve and delete.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerLuís MarquesPersonContributes to this
In the atlas: contributes to 8
@luismarques-io
1 contributor

Before choosing this

Conditions

PracticalFunctional boundary

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.

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference
Runtime
Node.js

As a sample

Form
A reference application

Connections3

README

quoted from SAP-samples/sap-btp-ai-best-practices under Apache-2.0, read
SAP-samples/sap-btp-ai-best-practices/best-practices/generative-ai/prompt-registry/cap/README.mdOn GitHub

CAP Implementations for Prompt Registry

This directory contains Cloud Application Programming (CAP) model implementations that demonstrate best practices for prompt registry with AI models through SAP BTP services.

Available Samples

Overview

These samples showcase how to:

  • Connect to generative AI services from CAP applications
  • Structure service layers for AI orchestration
  • Implement proper error handling
  • Deploy applications to SAP BTP

Getting Started

Each subdirectory contains a comprehensive README.md with detailed setup instructions, deployment guides, and usage examples.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
best-practices/generative-ai/prompt-registry/cap/README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, ai-and-agents
Flavors1
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-btp-ai-bp-prompt-registry-cap
JSON
/artifacts/sap-samples-btp-ai-bp-prompt-registry-cap.json
MCP
Connecting an agent