Everything in the atlas
Type
Domain
Origin
Signals
Content
More
Group by: Capability
Value-help recommendations and SAP AI Core as a CAP service
Protocol adapter serving CAP data as TOON instead of JSON
Vercel AI SDK provider for SAP AI Core
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
CAP service kind putting eleven model providers behind one API
MCP server answering plain-English questions against a CDS schema
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
SAP reuse library for calling large language models from ABAP
B-Tocs ABAP SDK plugin connecting to Ollama models
No published releases; repository quiet for 28 months.
ABAP-native MCP endpoint that drives opted-in abap2UI5 apps
Stateful apps cannot be operated: a stateful session lives in one HTTP request and an MCP call is one request, so `app_start` refuses them. The repository carries no release yet and states the addon has not been run in production use, the 7.02 downport is lint-only with no 7.02 system having run it, and the ABAP Cloud HTTP service setup is written down but still to verify on your own system.
No published releases; repository quiet for 34 months.
ABAP client library for IBM watsonx.ai APIs
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
ABAP client with one interface to chat-completion LLM APIs
The declared repository is archived.
ABAP library for calling Azure OpenAI and OpenAI
No published releases; repository quiet for 29 months.
AI runtime on BTP with the Generative AI Hub
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
ABAP framework for chaining and orchestrating LLM calls
CodeJam on LLM-backed integration flows and MCP via API Management
Sample apps for SAP AI Core's Generative AI Hub capabilities
Setup guide and Python notebooks for SAP AI Core's Generative AI Hub
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
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.
Sample implementations for AI-powered applications on SAP BTP
ABAP report sending a prompt to a local LLM via an SM59 destination
CAP reference app for GenAI email support with RAG on HANA Cloud
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CodeJam on a CAP job posting service using SAP AI Core over OData
CodeJam on code-based AI agents in Python or TypeScript on SAP BTP
CodeJam deploying an LLM on Generative AI Hub and building RAG
Hands-on building an AI agent with the SAP Cloud SDK for AI
TechEd 2025 material on two SAP Databricks scenarios in BDC
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
UI5 workshop adding Chrome's on-device AI APIs to a TypeScript app
ML models that classify records and predict attributes
Machine learning recommendations over browsing history via REST
Tutorial notebooks and templates for a first SAP AI Core project
ML service on SAP AI Core scoring restaurant-inspection violations
FastAPI backend for SAP-RPT-1.5 predictions from SAP Analytics Cloud
SQL examples for the HANA APL APIs plus scoring runtimes
Code examples for predictive and ML scenarios on SAP HANA
Bruno collections and code for SAP-RPT predictions on tabular data
CodeJam on a first machine learning workflow in SAP HANA Cloud
TechEd 2023 session on SAP HANA features over HDI
TechEd 2025 workshop on SAP HANA Cloud's AI capabilities
TechEd 2025 material on two SAP Databricks scenarios in BDC
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
CAP service kind putting eleven model providers behind one API
AI runtime on BTP with the Generative AI Hub
CAP samples using SAP AI Core's Prompt Registry for templates
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.
CAP samples filling a prompt template sent to SAP AI Core
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.
Sample implementations for AI-powered applications on SAP BTP