CDS pluginCDS pluginInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cap-decisions
Adds a decisions service to a CAP Node.js application that answers typed questions about one text or JSON state through an HTTP decision endpoint.
Adds a decisions required service to a CAP Node.js application: cds.connect.to('decisions') returns a client whose decide() call sends one text or JSON state and a map of named choice, score and noul questions to an HTTP endpoint that speaks the Jev protocol, and gets one typed answer per question back with its probabilities and a confidence value. Which endpoint that is comes from a kind under cds.requires.decisions, one per provider: TypeSafe System OneTypeSafe System OneTypeSafe's hosted decision API: one POST endpoint that answers named questions about supplied content with a Jev model and returns the typed answers, the model that answered and the token usage. Its request and response schema is the Jev protocol cap-decisions speaks., SubQ Snap, the clef model on Cloudflare Workers AI, a Laya server, or any Jev-compatible URL under the generic kind. cds add decisions writes that choice into a CAP profile. In TypeScript the choice labels are inferred from the criteria keys, so the selected label is typed as a union of those keys and a handler map that misses one does not compile. In the development and test profiles an application without an explicit kind gets decisions-mock, which answers in-process from fixtures without a server, a token or network access, and npx cap-decisions-mock serves the same answers over HTTP. The package serves no service of its own: it creates no OData endpoint and produces no text, and the action that calls decide(), with the @requires that protects it, belongs to the application.
Facts
LicenceMIT
Where it sits
Lives in
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.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.
Add-on to
@sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.
Flavors
Node.jsfrom its runtime
Requires
@sap/cds^9 || ^10@sap/cdsThe framework it extends: CAP loads the package's cds-plugin.js and adds the decisions required service, which the application reaches with cds.connect.to('decisions'). The peer range is ^9 || ^10.
Optional
@sap/cds-dk@sap/cds-dkThe cds add decisions facet runs inside CAP's cds add command, so it needs the development kit; the package itself does not depend on it.@sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityResolving the named destination: the optional peer package is installed in the CAP application, and the plugin calls its getDestination().SAP Destination serviceSAP Destination serviceHolds the full POST endpoint and the static Authorization header for the provider, so neither is in the application's configuration. The entry is a NoAuthentication destination with a URL.headers.Authorization property; other destination authentication flows are outside the integration's scope.TypeSafe System OneTypeSafe System OneThe endpoint the kind posts to, https://api.typesafe.ai/v1/systemone, with the jev-latest model and a token the kind requires.
Who is behind it
Hendrik NeumannHendrik NeumannMaintains this
In the atlas: maintains 1@hendrik77maintainer
In the atlas: maintains 1@hendrik77maintainer
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
Also, from LLM integration§ 3: Calling a model for inference is not automatically AI training. Section 3 matters when the covered material or application participates in training, model development, refinement or the text-and-data-mining uses it names.
PracticalFunctional boundary
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.
What it declares
Every artifact
- Type
- CDS plugin
- Origin
- Independently maintained
- Runtime
- Node.js
As a CDS plugin
- Declared for
- ^9 || ^10
- Type declarations
- declared
- Distributed through
- does not say
For LLM integration
- Models it reaches
- Other providers
For service integration
- Protocols
- http
Connections
Group by9 of 9 connections
NodeRelationBasis
Functional
LLM integrationLLM integrationCalling a language model with tenant and credential handling solvedSAP and community, narrow by design
provides
stated
provides LLM integration
Calls a decision model over HTTP from a CAP handler with the endpoint and the credentials kept in CAP's configuration: the kind carries the URL, the `modelId` that is sent as `model` and the request limits, the token comes from a secret source or from a BTP destination, and the plugin does the timeout, the retries on 429, 502, 503, 504 and 529, and the error codes. What comes back is one typed answer per named question: a choice label with a probability per key, a score with its legend, or the probability that a yes/no answer is true. There is no text to parse.
“It evaluates `choice`, `score`, and `noul` questions against one text or JSON state, using a decision model such as Jev, Laya or Clef.”“When `true`, connecting fails with `INVALID_CONFIG` unless a `credentials.token` is set, or a `credentials.destination` that supplies an `Authorization` header”“HTTP 429, 502, 503, 504 and 529, and network failures (including interrupted response bodies), are retried at most twice, honoring `Retry-After` or using jittered backoff.”
Calling a language model with tenant and credential handling solved
Service integrationService integrationUsing a remote service as if it were one of your ownSAP and community, narrow by design
provides
stated
provides Service integration
Puts a remote decision endpoint behind a CAP service: the kind holds its URL and limits, `cds.connect.to('decisions')` checks the configuration and rejects an invalid one with `INVALID_CONFIG`, and `decide()` sends an internal CAP `decide` event that an application can hang `before` and `after` handlers on. For work off the network it ships a mock: `decisions-mock` is the kind an application without an explicit one gets in the `development` and `test` profiles, answering in-process from fixtures in `test/data/decisions.json`, with `latencyMs` and `fail` to simulate a slow or failing provider, and `npx cap-decisions-mock` serves the same answers over HTTP so retries, timeouts and tokens are exercised too.
“`decide()` sends an internal CAP `decide` event. Applications can register `before` and `after` handlers on the connected service.”“In the `development` and `test` profiles, an application without an explicit `kind` gets the `decisions-mock` kind. It answers in-process, deterministically and without a server, a token or network access, so `cds watch`, `cds serve` and `cds.test` work out of the box.”“It gives the same answers as the in-process mock over HTTP.”
Using a remote service as if it were one of your own
Technical
SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimesap official, btp
connects to
stated
connects to SAP Destination service
`credentials.destination` is set.
Reads the destination's URL and static headers to reach the provider: the plugin resolves it when the service is created and again for each call, and a destination that is not found, or that carries a bad URL or bad headers, fails the connection.
“The plugin resolves the destination with `getDestination()` when the service is created and for each call; it uses the SDK's cache.”“A destination that is not found, or that has a bad URL or bad headers, still fails the connection.”
Named, credentialed addresses of other systems resolved at runtime
connects to
stated
connects to TypeSafe System One
The `decisions-typesafe` kind is selected.
Posts the state and the questions to `https://api.typesafe.ai/v1/systemone` with `jev-latest` as the model and a bearer token, and reads the typed answers back.
“| `decisions-typesafe` | `https://api.typesafe.ai/v1/systemone` | `jev-latest` | `true` | `choiceOptions`: 255; `scoreCriteria`: 2 to 10 |”“It works with any HTTP endpoint that speaks the Jev protocol (the request and response schema of TypeSafe's System One API), and with providers whose protocol differs through a subclass.”
TypeSafe's hosted decision API: one POST endpoint that answers named questions about supplied content with a Jev model and returns the typed answers, the model that answered and the token usage. Its request and response schema is the Jev protocol cap-decisionscap-decisionsAdds a decisions service to a CAP Node.js application that answers typed questions about one text or JSON state through an HTTP decision endpoint.independent, cap speaks.
@sap/cds@sap/cdsCAP Node.js runtimesap official, cap
needs
stated
needs @sap/cds
The framework it extends: CAP loads the package's `cds-plugin.js` and adds the `decisions` required service, which the application reaches with `cds.connect.to('decisions')`. The peer range is `^9 || ^10`.
“Requirements: Node.js 22 or newer and `@sap/cds` 9 or 10 (the peer range is `^9 || ^10`).”“CAP loads the package's `cds-plugin.js` and adds the `decisions` required service.”
CAP Node.js runtime
@sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and connectivity proxy for the Cloud SDKsap official, cap
optionally needs
stated
optionally needs @sap-cloud-sdk/connectivity
`credentials.destination` names a Destination service entry instead of a `url` and a `token`.
Resolving the named destination: the optional peer package is installed in the CAP application, and the plugin calls its `getDestination()`.
“Install the optional peer package `@sap-cloud-sdk/connectivity` in the CAP application.”
Destination lookup and connectivity proxy for the Cloud SDK
@sap/cds-dk@sap/cds-dkCommand line client and development toolkit for CAPsap official, cap
optionally needs
stated
optionally needs @sap/cds-dk
`cds add decisions` is used to write the configuration; without it the same entries are written by hand.
The `cds add decisions` facet runs inside CAP's `cds add` command, so it needs the development kit; the package itself does not depend on it.
“The `cds add decisions` command (see below) needs `@sap/cds-dk` 9 or 10, like every `cds add`; the package itself does not depend on it.”“Without `@sap/cds-dk`, write the same by hand.”
Command line client and development toolkit for CAP
SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimesap official, btp
optionally needs
stated
optionally needs SAP Destination service
`credentials.destination` is set instead of `url` and `token`.
Holds the full POST endpoint and the static `Authorization` header for the provider, so neither is in the application's configuration. The entry is a `NoAuthentication` destination with a `URL.headers.Authorization` property; other destination authentication flows are outside the integration's scope.
“On SAP BTP, you can set `credentials.destination` to the name of a Destination service entry instead of supplying `url` and `token`.”“This integration reads the destination URL and static headers; other destination authentication flows are outside its scope.”
Named, credentialed addresses of other systems resolved at runtime
optionally needs
stated
optionally needs TypeSafe System One
The `decisions-typesafe` kind is selected.
The endpoint the kind posts to, `https://api.typesafe.ai/v1/systemone`, with the `jev-latest` model and a token the kind requires.
“| `decisions-typesafe` | `https://api.typesafe.ai/v1/systemone` | `jev-latest` | `true` | `choiceOptions`: 255; `scoreCriteria`: 2 to 10 |”
TypeSafe's hosted decision API: one POST endpoint that answers named questions about supplied content with a Jev model and returns the typed answers, the model that answered and the token usage. Its request and response schema is the Jev protocol cap-decisionscap-decisionsAdds a decisions service to a CAP Node.js application that answers typed questions about one text or JSON state through an HTTP decision endpoint.independent, cap speaks.
Download
Where it sits in your app
Download
cap-decisionsAdds a decisions service to a CAP Node.js application that answers typed questions about one text or JSON state through an HTTP decision endpoint.independent, cap
@sap/cds-dkThe command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.sap official, cap
@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, cap
SAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
TypeSafe System OneTypeSafe's hosted decision API: one POST endpoint that answers named questions about supplied content with a Jev model and returns the typed answers, the model that answered and the token usage. Its request and response schema is the Jev protocol cap-decisions speaks.
cap-decisions → TypeSafe System OneStated in the document, data, outbound, sync, under a conditionPosts the state and the questions to
https://api.typesafe.ai/v1/systemone with jev-latest as the model and a bearer token, and reads the typed answers back.If The decisions-typesafe kind is selected.cap-decisions → SAP Destination serviceStated in the document, data, outbound, under a conditionReads the destination's URL and static headers to reach the provider: the plugin resolves it when the service is created and again for each call, and a destination that is not found, or that carries a bad URL or bad headers, fails the connection.If
credentials.destination is set.cap-decisions → @sap/cds-dkDocumented only, under a conditionThe
cds add decisions facet runs inside CAP's cds add command, so it needs the development kit; the package itself does not depend on it.If cds add decisions is used to write the configuration; without it the same entries are written by hand.cap-decisions → @sap-cloud-sdk/connectivityDocumented only, under a conditionResolving the named destination: the optional peer package is installed in the CAP application, and the plugin calls its
getDestination().If credentials.destination names a Destination service entry instead of a url and a token.SAPnot SAP's, or the project's ownstated in the documentunder a condition
Others providing
LLM integrationLLM 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.SAP and community, narrow by design
- llm_clientllm_clientAn ABAP client that gives chat-completion LLM APIs one interface for chat messages, structured output and tool calls across ten providers, from OpenAI and Anthropic to OLLAMA and AWS Bedrock.independent, abapABAP client with one interface to chat-completion LLM APIsfrom ABAP
- abap-agent-runtimeabap-agent-runtimeAn ABAP-native MCP endpoint inside the SAP system: an agent reads the screen of an opted-in abap2UI5 app as structured data, fills its fields and fires its events as the logged-on SAP user.community org, abapABAP-native MCP endpoint that drives opted-in abap2UI5 appsfrom ABAP
- abap_btocs_ollamaabap_btocs_ollamaAn ABAP plugin, built on the B-Tocs ABAP SDK, that calls models served by Ollama through an SM59 RFC destination, implementing four of its API endpoints: generate, tags, show and embeddings.independent, abapB-Tocs ABAP SDK plugin connecting to Ollama modelsfrom ABAP
- SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btpAI runtime on BTP with the Generative AI Hubfrom BTP/BAIP
- cap-java/cds-aicap-java/cds-aiBridges CAP Java to SAP AI Core and adds AI-powered field recommendations to Fiori draft UIs, as two alpha Maven modules with mock fallbacks for local development.sap official, capBridge from CAP Java to SAP AI Core, with Fiori field recommendationsfrom CAP
- @cap-js/ai@cap-js/aiOut-of-the-box value-help recommendations powered by SAP RPT-1, SAP AI Core as a standard CAP service, and an experimental local embedding model behind SQLite's vector functions.sap official, capValue-help recommendations and SAP AI Core as a CAP servicefrom CAP
- cap-llm-plugincap-llm-pluginGenerative AI in a CAP application with the sensitive fields anonymised through SAP HANA before the prompt leaves, so the model never sees the confidential half.independent, capGenerative AI in CAP with fields anonymised through SAP HANAfrom CAP
- @geertjanklaps/cds-toon-ai-protocol-adapter@geertjanklaps/cds-toon-ai-protocol-adapterA protocol adapter that serves CAP data as TOON — Token-Oriented Object Notation — instead of JSON, so a payload bound for a language model costs fewer tokens to send.independent, capProtocol adapter serving CAP data as TOON instead of JSONfrom CAP
- abap-sdk-nwas-xabap-sdk-nwas-xAn ABAP client library for IBM's watsonx.ai and watsonx.ai Runtime APIs, installed into an SAP NetWeaver AS ABAP system through abapGit, generating and refreshing the IAM token from an API key.independent, abapABAP client library for IBM watsonx.ai APIsfrom ABAP
- @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, capVercel AI SDK provider for SAP AI Corefrom CAP
- ui5-cap-ai-featuresui5-cap-ai-featuresBoth halves of an AI text feature in one package: a CDS plugin serving an AIService over SAP AI Core's Orchestration Service, and the be.wl.ai UI5 control library that calls exactly that service.independent, capCDS plugin and UI5 controls for AI text features via SAP AI Corefrom CAP
- Microsoft AI SDK for SAPMicrosoft AI SDK for SAPMicrosoft's ABAP library for calling Azure OpenAI and OpenAI from an SAP application server, wrapping completions, embeddings, fine-tuning and the other operations in ABAP data types, installed with abapGit.partner, abapABAP library for calling Azure OpenAI and OpenAIfrom ABAP
- zllmzllmAn ABAP framework for chaining and orchestrating calls to large language models in pure ABAP, with templated prompts, routing by complexity, response caching and token estimation.independent, abapABAP framework for chaining and orchestrating LLM callsfrom ABAP
- ABAP AI SDKABAP AI SDKSAP's reuse library for calling a large language model from ABAP code, powered by Intelligent Scenario Lifecycle Management and reaching the models in the Generative AI Hub; delivered with SAP BTP ABAP environment, SAP S/4HANA Cloud Public and Private Edition and SAP S/4HANA.sap official, abapSAP reuse library for calling large language models from ABAPfrom ABAP
- @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, capAI Core control plane API surface of SAP's AI SDKfrom CAP
- @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, capShared internals of SAP's AI SDKfrom CAP
- @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, capClient for foundation models via SAP AI Core and Generative AI Hubfrom CAP
- @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, capOrchestration Service client for templating, grounding and maskingfrom CAP
- @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, capClient for prompts kept in SAP's prompt registryfrom CAP
- @saptarishi/cds-plugin-llm@saptarishi/cds-plugin-llmA CAP service kind that puts eleven model providers behind one chat, stream, embed and batch interface, so which backend a service calls is a profile in package.json rather than a change to the handler.independent, capCAP service kind putting eleven model providers behind one APIfrom CAP
- @shahid.la/cds-db-nlquery-mcp@shahid.la/cds-db-nlquery-mcpMCP server that answers plain-English questions against the entities in db/schema.cds — it discovers the schema, generates CQN-backed SQL with real joins, and returns rows.independent, capMCP server answering plain-English questions against a CDS schemafrom CAP
- @ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5SAP's UI elements as standard custom elementsfrom UI5
- abap-sdk-nwasabap-sdk-nwasAn ABAP client library for IBM Watson's Discovery, Language Translator, Natural Language Understanding, Speech to Text, Text to Speech and Assistant services, installed through abapGit.independent, abapAn ABAP client library for IBM Watson's Discovery, Language Translator, Natural Language Understanding, Speech to Text, Text to Speech and Assistant services, installed through abapGit.from ABAP
Service integrationService 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, which is how the address and the credentials are found, and from replication, which is holding the data locally.SAP and community, narrow by design
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Javafrom CAP
- 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, capPrebuilt SAP S/4HANA integration package for CAP projectsfrom CAP
- cds-data-federationcds-data-federationA data federation plugin for SAP CAP applications that declares delegation, caching and replication on a consumption view through CDS annotations, instead of hand-written handlers.independent, capData federation for CAP via delegation, caching and replicationfrom CAP
- @sap/cds-dk@sap/cds-dkThe command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.sap official, capCommand line client and development toolkit for CAPfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
runtimesnode
declared for^9 || ^10
discovered viaGitHub API · hendrik77/cap-decisions
first seen in the atlas
ecosystem and domaincap, ai-and-agents
History in the atlas
- First seen.
For your agent
- Ref
artifact:hendrik77-cap-decisions- JSON
- /artifacts/hendrik77-cap-decisions.json
- MCP
- Connecting an agent