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

Sample CAP Application with SAP Cloud SDK for AI

A CAP backend-sample and fullstack-sample pair that call SAP AI Core through the SAP Cloud SDK for AI: a capital-of-country question and a templated chat completion.

The backend-sample is a standalone CAP service with an orchestration CDS service exposing two actions, askCapitalOfCountry and a templated chatCompletion, built with @sap-ai-sdk/ai-api, @sap-ai-sdk/foundation-models and @sap-ai-sdk/orchestration; the fullstack-sample pairs the same service with a UI5 app under app/ask-capital that calls it over OData V4. For a local run both bind to an SAP AI Core instance with cds bind; the deployed fullstack sample names the instance in its mta.yml instead.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
LLM integrationBTPCAPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.
Serves
Flavors
Requires
SAP AI CoreSAP AI CoreartifactThe service instance the samples call for both actions, bound locally with cds bind or named in the fullstack sample's mta.yml.

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 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/access-to-generative-ai-models/cap/README.mdOn GitHub

CAP Implementations for Generative AI Access

This directory contains Cloud Application Programming (CAP) model implementations that demonstrate best practices for accessing generative 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/access-to-generative-ai-models/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-access-to-generative-ai-models-cap
JSON
/artifacts/sap-samples-btp-ai-bp-access-to-generative-ai-models-cap.json
MCP
Connecting an agent