Marten Schiwek
Capabilities
Entries
SDK for SAP Advanced Financial Closing scheduling providers on CDS
WebSocket and Socket.IO adapter for CDS services
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.
CDS plugin for building agents inside a CAP service
Value-help recommendations and SAP AI Core as a CAP service
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP integration with the SAP Audit Log service
Type definitions for the CAP Node.js SDK
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
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.
Exposes CAP services as MCP servers for AI agents
Business notifications from CAP to SAP Build WorkZone
Prints documents held in CAP entities through SAP Print service
OpenTelemetry instrumentation for CAP services
Sources of capire, the CAP documentation
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
Showcase of Fiori elements for OData V4 features on a CAP backend
Details
For your agent
- Ref
actor:schiwekm- JSON
- /actors/schiwekm.json
- MCP
- Connecting an agent