Everything in CAP
Type: 2
Domain
Origin
Signals: Last 30 days
More
Group by: Capability
Distributed through
Form
GraphQL protocol adapter generated from the CDS model
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
Exposes a CAP service as OData V2
CAP plugin serving the Cardano blockchain as OData V4
CAP plugin indexing the Midnight blockchain, exposed as OData V4
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Generates OpenAPI documents from a CDS service
Swagger UI for a CAP service's OpenAPI definition
Exposes CAP services as MCP servers for AI agents
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas applies that prohibition to CAP wrappers around those APIs. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement. In beta, with nine releases in the six weeks after the first, so pin it.
MCP server inside a CAP application with model and query tools
CAP travel-booking app built on xflights master data
WebSocket and Socket.IO adapter for CDS services
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
CAP's getting-started bookshop sample
CAP reuse package serving Airlines, Airports and Flights data
CAP Java reuse package for Airlines, Airports and Flights data
SAP HANA database service for CAP
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CAP plugin casting read values back to CDS model types
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Composite CAP app from separately deployed services
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
Consumes events from SAP Cloud Application Event Hub in CAP
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
Composite CAP app from separately deployed services
CAP travel-booking app built on xflights master data
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
CAP reuse package serving Airlines, Airports and Flights data
CAP travel-booking app built on xflights master data
CDS plugin for building agents inside a CAP service
Not as a gateway or proxy for SAP Application APIs: capire's guide states that CAP-level agents are intended only for exposing custom CAP application services and are not an SAP-endorsed architecture or pathway for agentic access to those APIs, and sends the reader to the SAP Architecture Center for the endorsed routes. Not as the screen a user of the application talks to, either — the chat preview in the generic index.html page is marked experimental and for local development.
LangGraph Store keeping agent memory as CDS entities
LangGraph checkpointer backed by CDS for CAP agents
CAP travel-booking app built on xflights master data
CAP samples comparing SAP AI Core responses with content filtering
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 generating email through SAP AI Core with anonymization
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.
Shows @cap-js/mcp query results as a table inside the agent host
Value-help recommendations and SAP AI Core as a CAP service
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
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.
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.
Value-help recommendations and SAP AI Core as a CAP service
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
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 running RAG similarity queries over SAP HANA Cloud vectors
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 integration with the SAP Audit Log service
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
CAP integration with the SAP Audit Log service
Poetry Slam Manager, a multi-tenant SaaS reference app on SAP BTP
Business-level metrics from CDS annotations via @cap-js/telemetry
OpenTelemetry instrumentation for CAP services
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Showcase for dev-approuter in front of two UI5 apps
Sample CAP plugin extending @sap/cds/common with reuse data
Sample CAP reuse service for orders, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP reuse service for reviews, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP Java reuse service for reviews, with a Vue UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Event registration app showing OData V4 draft with UI5 and CAP
Incident Management reference application for CAP
Travel-booking reference app on CAP Node.js and Java backends
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
CAP bookshop showing UI5 development with cds-plugin-ui5
Triggers n8n workflows from a CAP application
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Java implementation of the capire/bookshop getting-started sample
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
Incident Management reference application for CAP
Incident Management CAP app for the SAP BTP Developer's Guide
Travel-booking reference app on CAP Node.js and Java backends
Bookshop app demonstrating the CAP Java SDK end to end
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
Event registration app showing OData V4 draft with UI5 and CAP
CAP travel-booking app built on xflights master data
CAP Java travel-booking app built on xflights-java master data
CAP agent writing reports into a shared SDM document workspace
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.
UI5 app consuming the cds-bookshop server via ui5-middleware-cap