Person
Jérôme Benoit
Capabilities
Provides
LLM integrationCAPLLM integrationCalling 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.
Contributes to
Content filteringCAPContent filteringChecking 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 maskingCAPData maskingReplacing 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.Prompt managementCAPPrompt managementKeeping 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.
Entries
Group by
EntrySignals
Maintains
@jerome-benoit/sap-ai-provider@jerome-benoit/sap-ai-providerA provider for the Vercel AI SDK that speaks to SAP AI Core through its orchestration or foundation models API, so an application written against that SDK runs on SAP's models without being rewritten.independent, cap
Vercel AI SDK provider for SAP AI Core
Contributes to
@sap-ai-sdk/ai-api@sap-ai-sdk/ai-apiThe AI Core API surface of SAP's AI SDK, covering deployments, configurations and the rest of the control plane, as opposed to calling a model.sap official, cap
AI Core control plane API surface of SAP's AI SDK
@sap-ai-sdk/core@sap-ai-sdk/coreThe shared internals that the packages of SAP's AI SDK build on, which its own readme says are not meant to be depended on directly.sap official, cap
Shared internals of SAP's AI SDK
@sap-ai-sdk/foundation-models@sap-ai-sdk/foundation-modelsThe package of SAP's AI SDK that calls foundation models through SAP AI Core and the Generative AI Hub, and the one an application actually reaches for.sap official, cap
Client for foundation models via SAP AI Core and Generative AI Hub
@sap-ai-sdk/orchestration@sap-ai-sdk/orchestrationThe Orchestration Service client of SAP's AI SDK, which applies templating, grounding, filtering and masking around a model call rather than in the application.sap official, cap
Orchestration Service client for templating, grounding and masking
@sap-ai-sdk/prompt-registry@sap-ai-sdk/prompt-registryA package for keeping prompts in SAP's prompt registry rather than in the codebase, so changing a prompt is not a deployment.sap official, cap
Client for prompts kept in SAP's prompt registry
Details
History
- @jerome-benoit/sap-ai-providerThe edge carried no sentence and no source, so the entry sat on this capability's options list with nothing read for it. The README, read on 2026-10-15, names SAP AI Core as the service it provides for and streaming among its features, which is what the two properties state.
- @jerome-benoit/sap-ai-providerThe page opened with its index line alone, which left two facts a reader of this capability needs unsaid: that there are two routes into SAP AI Core and that only the model is replaced, not the SDK around it.
- @jerome-benoit/sap-ai-providerTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @jerome-benoit/sap-ai-providerPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- First entry seenDiscovered via npm registry, The discovery pass.
Profile
For your agent
- Ref
actor:jerome-benoit- JSON
- /actors/jerome-benoit.json
- MCP
- Connecting an agent