OrganisationSAP
Capire Docs & Samples
Capabilities
Provides
Agent evalsCAPBTPABAPAgent 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.Agent guidanceCAPBTPABAPAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.DestinationsCAPBTPDestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.Service integrationCAPService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.
Demonstrates
Agent toolingCAPBTPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.Data modellingCAPABAPData modellingDefining the shape of data before anything serves it: entities and their types, how they relate, and the projections and views that services and applications consume.Database connectorsCAPBTPABAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).DeploymentCAPBTPDeploymentGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.DocumentationCAPBTPABAPDocumentationFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.Fiori annotationsCAPABAPFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.Plugin authoringCAPPlugin authoringWriting a package that extends a framework or runtime rather than an application that uses it — a reusable extension loaded by its host, and the question you arrive at once solving a problem twice makes you want to solve it once for everyone.Reference appsCAPABAPReference appsA whole application to read rather than a snippet to copy — somewhere to see how the pieces sit together once there are more than three of them.Serve your application over MCPCAPBTPABAPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).Service compositionCAPService compositionBuilding one solution out of parts other projects published: a reuse package brings its models, code, initial data and texts into your project through npm or Maven, you serve what you reference and extend what you import, and the same modules deploy as one application or as several on a shared database. Distinct from [service integration](capability:service-integration), which reaches a service that stays deployed elsewhere, and from [tenant extensibility](capability:tenant-extensibility), which is a subscriber extending a running SaaS.Service integrationCAPService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.
Entries
Group by20 of 20 entries
EntrySignals
Maintains
capire/s4capire/s4A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.sap official, cap
Prebuilt SAP S/4HANA integration package for CAP projects
capire/skillscapire/skillsSAP's own skill set for coding agents working on CAP — cap-developer, cap-add-remote-service, cap-upgrade and cap-trivia, each a SKILL.md with references beside it.sap official, cap
Agent skills for CAP development, each a SKILL.md with references
Maintains: samples, sketches and references
@capire/data-viewer@capire/data-viewerA CAP plugin that adds a generic data browser to an application, written to show how a plugin is built rather than to be depended on, and used in the bookstore sample.sap official, cap
Its own readme carries a caution: this is a sample, not intended for production use. It exists to demonstrate the plugin mechanism, and the bookstore sample is where it is used.
Sample CAP plugin adding a generic data browser
bookshop-javabookshop-javaThe Java implementation of the capire/bookshop primer, CAP's own getting-started sample: the same application built on Spring Boot instead of Node.js, started with mvn spring-boot:run.sap official, cap
Java implementation of the capire/bookshop getting-started sample
bookstore-javabookstore-javaThe Java implementation of the capire/bookstore composite app: bookshop, reviews, orders and a common content package, each its own repository.sap official, cap
Java implementation of the capire/bookstore composite app
capire/bookshopcapire/bookshopThe primer of CAP: a bookshop small enough to read in one sitting, whose Books and Authors every CAP explanation, including this graph's, assumes you have already seen.sap official, cap
CAP's getting-started bookshop sample
capire/bookstorecapire/bookstoreA composite application assembled from separately deployed services — bookshop, reviews, orders and a common content package — rather than one project with more folders in it.sap official, cap
Composite CAP app from separately deployed services
capire/docscapire/docsThe sources of capire itself, in the repository it is built from: the documentation every core_coverage claim in this graph is checked against, so a claim can be dated against a commit.sap official, cap
Sources of capire, the CAP documentation
capire/incidents-appcapire/incidents-appThe Incident Management reference application — the one SAP's own tutorial paths build, step by step, and the model cds add incidents-sample drops into a project.sap official, cap
Incident Management reference application for CAP
commoncommonA CAP plugin that extends @sap/cds/common with enhanced reuse data in .csv, published as a sample of how to write a CAP plugin rather than as something to run in production.sap official, cap
Sample CAP plugin extending @sap/cds/common with reuse data
ordersordersA sample reuse service for managing orders, with its own Fiori UI, written to show how a CAP plugin is built and consumed: embedded in the consuming application or run standalone over OData.sap official, cap
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP reuse service for orders, with a Fiori UI
orders-javaorders-javaA sample reuse service for managing orders, with its own Fiori UI, in the capire/orders-java repository; its README is the one orders carries and names no runtime.sap official, cap
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP Java reuse service for orders, with a Fiori UI
reviewsreviewsA sample reuse service for managing reviews, with its own Fiori UI, written to show how a CAP plugin is built and consumed, and used in the bookstore sample.sap official, cap
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
reviews-javareviews-javaA sample reuse service for managing reviews, with a Vue UI, in the capire/reviews-java repository, written to show how a CAP plugin is built and used in the bookstore sample.sap official, cap
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
shared-dbshared-dbA CAP sample showing how one domain model is shared across several apps that all rely on it, used to deploy microservices against a shared database, with capire's Microservices with CAP guide as background.sap official, cap
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP sample sharing one domain model and database across apps
shared-db-javashared-db-javaA CAP sample showing how one domain model is shared across several apps that all rely on it, in the capire/shared-db-java repository, with capire's Microservices with CAP guide as background.sap official, cap
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Java sample sharing one domain model across several apps
xflightsxflightsA reuse package serving master-data entities (Airlines, Airports and Flights) as a service that other CAP applications compose into their own data model.sap official, cap
CAP reuse package serving Airlines, Airports and Flights data
xflights-javaxflights-javaThe Java twin of capire/xflights: a CAP Java service managing Airlines, Airports and Flights master data, with its client package xflights-data pulled into a consuming app through Maven.sap official, cap
CAP Java reuse package for Airlines, Airports and Flights data
xtravelsxtravelsA travel-booking application built on the master data that xflights publishes, composing another package's schema into its own rather than owning master data itself.sap official, cap
CAP travel-booking app built on xflights master data
xtravels-javaxtravels-javaThe Java twin of xtravels: a Spring Boot travel-booking application built on master data from xflights-java, which CAP mocks automatically unless a hybrid profile connects a running instance.sap official, cap
CAP Java travel-booking app built on xflights-java master data
Writing and topics
Piece, what it offersStill applies
Model Context Protocol Adapter — CAP guideModel Context Protocol Adapter — CAP guideDocuments @cap-js/mcp and com.sap.cds:cds-adapter-mcp, service annotations, generated describe/query/call tools and local client setup. The guide records Java doc-comment configuration, unbound-action-based data changes, incomplete XSUAA PKCE support and the adapter’s governance boundaries.
Details
History
- capire/skillscap-developer's own SKILL.md says it covers CAP applications in either Node.js or Java, and its eval file marks every case with a stack. Stated so the two CAP flavors read this entry as an answer rather than as an artifact that does not say.
- capire/skillsThe edge carried one source and no quote. Re-read both eval files on 2026-10-15: the fixture path, the expected-output field, the named assertions and the stack marker are now quoted, and the capability's two comparison properties are answered from the same sentences.
- xtravelscapire's XTravels Sample for AI page shows the sample integrating several MCP services and CAP-level agents.
- First entry seenDiscovered via GitHub API · capire, Added by hand, npm registry · keywords:sap-cap, capire.
Profile
For your agent
- Ref
actor:capire- JSON
- /actors/capire.json
- MCP
- Connecting an agent