Person

Kevin Riedelsheimer

Capabilities6

Contributes to 6
Agent access to your codeCAPBTPAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Content filteringBTPCAPContent filteringcapabilityChecking what goes into a model and what comes out of it against content rules, and stopping or flagging a request that fails them. Distinct from [data masking](capability:data-masking), which hides values: a filter refuses content.Data maskingBTPCAPData maskingcapabilityReplacing the personal or confidential values in a prompt with placeholders before it leaves for a model, and putting them back in the answer. Anonymisation, where the values are gone for good, and pseudonymisation, where they return, are the two forms; which fields count as sensitive is the application's question, not the module's.DocumentationCAPBTPDocumentationcapabilityFinding 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.LLM integrationCAPBTPLLM 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.Prompt managementBTPCAPPrompt managementcapabilityKeeping the prompts an application sends to a model as templates with placeholders, stored and versioned apart from the code that calls them, so a change of wording is not a deployment. What people conflate under it: the template filled at runtime, the registry it lives in, and the orchestration step that fills it.

Entries11

Group by11 of 11 entries
EntrySignals
Contributes to11
@cap-js/mcp-serverv0.0.8
Functional boundary

MCP server for CAP development: model and docs search

@sap-ai-sdk/ai-apiv2.17.0
none

AI Core control plane API surface of SAP's AI SDK

@sap-ai-sdk/corev2.17.0
none

Shared internals of SAP's AI SDK

@sap-ai-sdk/foundation-modelsv2.17.0
none

Client for foundation models via SAP AI Core and Generative AI Hub

@sap-ai-sdk/orchestrationv2.17.0
none

Orchestration Service client for templating, grounding and masking

@sap-ai-sdk/prompt-registryv2.17.0
none

Client for prompts kept in SAP's prompt registry

SAP-samples/cap-hana-exercises-codejam
none

CodeJam building a full-stack CAP app on SAP HANA Cloud

SAP-samples/cloud-btp-cli-api-codejam
none

CodeJam material on the btp CLI and the Core Services API

SAP-samples/codejam-cap-llm
none

CodeJam on a CAP job posting service using SAP AI Core over OData

SAP-samples/codejam-code-based-agents
none

CodeJam on code-based AI agents in Python or TypeScript on SAP BTP

SAP-samples/generative-ai-codejam
none

CodeJam deploying an LLM on Generative AI Hub and building RAG

Details

Profile1
For your agent
Ref
actor:kevinriedelsheimer
JSON
/actors/kevinriedelsheimer.json
MCP
Connecting an agent