{"ref":"capability:agent-systems-access","page":"/capabilities/agent-systems-access","json":"/capabilities/agent-systems-access.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"agent-systems-access","name":"Agent access to your systems","domain":"ai-and-agents","ecosystems":["btp","abap","cap","commerce","successfactors"],"universal":true,"description":"Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).","short":"Giving an AI agent access to the systems you run over MCP","core_coverage":{"state":"core-and-community","what_core_does":"SAP publishes two servers of its own on this door. [MCP Server for SAP BTP Administration](artifact:sap-btp-administration-mcp) puts account, security, service and connectivity operations behind one hosted endpoint, discovered by the client rather than configured per operation, and the [SAP LeanIX MCP Server](artifact:sap-leanix-mcp-server) exposes selected enterprise-architecture APIs as typed tools. Both act under the caller's own authorisation.","where_it_stops":"The assessed SAP servers expose operations of BTP Administration and LeanIX under the caller's authorisation; this coverage does not establish a general gateway for arbitrary SAP Application APIs.","sources":[{"url":"https://help.sap.com/docs/btp/sap-business-technology-platform/account-administration-using-mcp-servers","title":"Account Administration Using MCP Servers — SAP Help Portal","checked":"2026-09-09","quote":"aggregates four administration domains — accounts, security, services, and connectivity — behind a single endpoint"},{"url":"https://help.sap.com/docs/leanix/ea/mcp-server","title":"MCP Server — SAP LeanIX, SAP Help Portal","checked":"2026-09-09","quote":"SAP LeanIX uses MCP to expose selected APIs as AI tools"}],"assessed_at":"2026-10-09","relationship":"narrow-by-design"},"coverage_by_ecosystem":{"abap":{"state":"community-only","assessed_at":"2026-10-09","where_it_stops":"At what two community servers expose from outside: RFC-enabled function modules as tools, and a read-only view of the system's security posture. SAP's own ABAP MCP Server runs inside ABAP Development Tools and lets an agent develop against the system, which is [agent access to your code](capability:agent-code-access) and not this.","note":"community-only is a assessment of the corpus: the providers are independent and SAP publishes nothing that reaches into a running ABAP system for an agent."},"cap":{"state":"community-only","assessed_at":"2026-10-09","where_it_stops":"The official CAP MCP adapters are intended only for custom CAP application services and must not be used as a gateway or proxy for SAP Application APIs. Wrapping an SAP Application API in a CAP service does not remove that restriction.","note":"A bridge design needs evidence for both the remote-service integration and the selected MCP implementation; CAP integration support alone does not establish agent access to a particular target API.","community_adds":"[cap-mcp-bridge](artifact:sanoberrehman-cap-mcp-bridge) runs outside a CAP or other OData V4 service and derives MCP tools from its metadata, without per-service code. That metadata-based access is a different implementation from a CAP application that integrates a remote service and exposes selected operations through an MCP adapter.","sources":[{"url":"https://cap.cloud.sap/docs/guides/ai/cap-mcp","title":"Model Context Protocol Adapter | capire","quote":"The CAP MCP adapter must not be used as a gateway or proxy for SAP Application APIs.","checked":"2026-10-12"},{"url":"https://cap.cloud.sap/docs/guides/integration/calesi","title":"CAP-Level Service Integration | capire","quote":"Remote services represented as CAP services, which you can consume as if they were local","checked":"2026-10-12"},{"url":"https://github.com/SanoberRehman/cap-mcp-bridge","title":"SanoberRehman/cap-mcp-bridge — README","quote":"cap-mcp-bridge runs outside the service and consumes `$metadata` over HTTP.","checked":"2026-10-12"}]},"commerce":{"state":"community-only","assessed_at":"2026-10-09","where_it_stops":"At reading a developer's own running instance. The door's one provider, [hybris-mcp-lite](artifact:andreescocard-hybris-mcp-lite), exposes a read-only slice of HAC and states local and development instances only, so what an agent reaches here is what HAC will answer about the system in front of the developer — nothing that writes, and nothing a deployed storefront serves to an agent of its own.","note":"One provider and it is independent, so community-only is a assessment of the corpus. No SAP-published provider of this capability is behind this door in the corpus, which may be absence of evidence rather than evidence of absence; the product itself is [SAP Commerce Cloud](external:sap-commerce-cloud), an external, and never an artifact here."},"successfactors":{"state":"community-only","assessed_at":"2026-10-09","where_it_stops":"At what one community server exposes: SuccessFactors' OData APIs curated into tools, reached with the caller's own credentials. SAP publishes no MCP server for SuccessFactors that the atlas has read.","note":"community-only is a assessment of the corpus on the day the SAP SuccessFactors door opened (docs/concepts/product-doors.md): one provider, independent, moved here from the BTP door. SAP's own answer is not assessed."}},"normative_relevance":[{"instrument":"instrument:sap-api-policy-v4-2026a","prominence":"prominent","sections":["1.1","1.2","2.2.2"],"applies_when":"An MCP server uses SAP APIs to supply tools, resources or data to an agent.","note":"MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.","sources":[{"url":"https://help.sap.com/doc/sap-api-policy/latest/en-US/API_Policy_latest.pdf","title":"SAP API Policy v.4.2026a","checked":"2026-09-16","quote":"verify that each endpoint for Documented Use is a Published API"}]},{"instrument":"instrument:sap-developer-license-3-2-cap","prominence":"prominent","sections":["1","3"],"applies_when":"An MCP server uses SAP APIs to supply tools, resources or data to an agent.","note":"The CAP developer agreement can apply alongside the API Policy. Ordinary agent inference is not automatically AI training; section 3 becomes relevant when covered materials or applications are used to train, develop or refine a model or system.","applies_to":{"ecosystems":["cap"]},"sources":[{"url":"https://cap.cloud.sap/resources/license/developer-license-3_2_CAP.txt","title":"SAP Developer License Agreement 3.2 CAP","checked":"2026-09-16","quote":"for the purpose of training (developing) artificial intelligence models or systems"}]}],"history":[{"date":"2026-10-09","field":"entry","from":null,"to":"created","reason":"Split out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling."},{"date":"2026-10-12","field":"core_coverage.where_it_stops","from":"At SAP's own products on BTP. SAP ships no server here for S/4HANA, SuccessFactors, Commerce, Datasphere, Analytics Cloud, HANA Cloud or the Integration Suite runtime; every server that reaches those is the community's, each with its own authentication and its own read or write boundary, stated on its page. The [Integration Suite MCP gateway](artifact:btp-api-management) is the other side of this concern: it turns an API you already manage into a server, which is [serving over MCP](capability:mcp-servers), not reaching in.","to":"The assessed SAP servers expose operations of BTP Administration and LeanIX under the caller's authorisation; this coverage does not establish a general gateway for arbitrary SAP Application APIs.","reason":"Remove the exclusive-direction claim and the blanket absence claim. Retain the documented scope of the assessed servers without surveying or reclassifying the BTP provider inventory."},{"date":"2026-10-12","field":"coverage_by_ecosystem.cap","from":"{\"state\": \"community-only\", \"assessed_at\": \"2026-10-09\", \"where_it_stops\": \"At a generic bridge pointed at a running CAP or OData V4 service from outside, reading its metadata into tools. A CAP service that exposes itself through the @mcp adapter is [serving over MCP](capability:mcp-servers), SAP's own answer on this door for the other direction.\", \"note\": \"community-only is a reading of the corpus on the day the concern was split out of MCP servers: one provider, independent.\"}","to":"{\"state\": \"community-only\", \"assessed_at\": \"2026-10-09\", \"where_it_stops\": \"The official CAP MCP adapters are intended only for custom CAP application services and must not be used as a gateway or proxy for SAP Application APIs. Wrapping an SAP Application API in a CAP service does not remove that restriction.\", \"note\": \"A bridge design needs evidence for both the remote-service integration and the selected MCP implementation; CAP integration support alone does not establish agent access to a particular target API.\", \"community_adds\": \"[cap-mcp-bridge](artifact:sanoberrehman-cap-mcp-bridge) runs outside a CAP or other OData V4 service and derives MCP tools from its metadata, without per-service code. That metadata-based access is a different implementation from a CAP application that integrates a remote service and exposes selected operations through an MCP adapter.\", \"sources\": [{\"url\": \"https://cap.cloud.sap/docs/guides/ai/cap-mcp\", \"title\": \"Model Context Protocol Adapter | capire\", \"quote\": \"The CAP MCP adapter must not be used as a gateway or proxy for SAP Application APIs.\", \"checked\": \"2026-10-12\"}, {\"url\": \"https://cap.cloud.sap/docs/guides/integration/calesi\", \"title\": \"CAP-Level Service Integration | capire\", \"quote\": \"Remote services represented as CAP services, which you can consume as if they were local\", \"checked\": \"2026-10-12\"}, {\"url\": \"https://github.com/SanoberRehman/cap-mcp-bridge\", \"title\": \"SanoberRehman/cap-mcp-bridge — README\", \"quote\": \"cap-mcp-bridge runs outside the service and consumes `$metadata` over HTTP.\", \"checked\": \"2026-10-12\"}]}","reason":"Clarify complementary capability boundaries and retain the official CAP adapter prohibition. Distinguish the external metadata client from an application integration layer; preserve the existing provider inventory, coverage state and assessment date."},{"date":"2026-10-12","field":"description","from":"Giving an AI agent a way into an SAP system you run — its business data, its configuration and the operations on it — through a server that stands between the agent and the system and speaks the Model Context Protocol. The sibling of [agent access to your code](capability:agent-code-access), which is the development-time side; this is the running landscape: SuccessFactors' OData APIs, a Datasphere tenant, BTP's own administration, a Commerce instance, an ABAP system's function modules. The other direction, exposing what *you* built to agents, is [serving your application over MCP](capability:mcp-servers), and the two do not substitute for each other: a server that reads SuccessFactors does nothing for your CAP service, and the CAP adapter does nothing for SuccessFactors.","to":"Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. A CAP application can form the integration layer between the agent and a target system, while [Serve your application over MCP](capability:mcp-servers) describes how its service contract is exposed; one solution can address both concerns when its implementation supports that use. Supported target APIs, authentication, read/write boundaries and gateway restrictions belong to the specific implementations and scoped assessments; development assistance belongs to [Agent access to your code](capability:agent-code-access).","reason":"Maintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged."},{"date":"2026-10-17","field":"description","from":"Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. A CAP application can form the integration layer between the agent and a target system, while [Serve your application over MCP](capability:mcp-servers) describes how its service contract is exposed; one solution can address both concerns when its implementation supports that use. Supported target APIs, authentication, read/write boundaries and gateway restrictions belong to the specific implementations and scoped assessments; development assistance belongs to [Agent access to your code](capability:agent-code-access).","to":"Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).","reason":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit."}],"drafted_with_ai":true,"framing_by_ecosystem":{"cap":{"description":"Giving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. A CAP application can form the integration layer between the agent and a target system, while [Serve your application over MCP](capability:mcp-servers) describes how its service contract is exposed; one solution can address both concerns when its implementation supports that use. Supported target APIs, authentication, read/write boundaries and gateway restrictions belong to the specific implementations and scoped assessments; development assistance belongs to [Agent access to your code](capability:agent-code-access)."}}},"sap_delivery":{"door":"btp","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:sap-btp-administration-mcp","name":"MCP Server for SAP BTP Administration","json":"/artifacts/sap-btp-administration-mcp.json"},{"ref":"artifact:sap-leanix-mcp-server","name":"SAP LeanIX MCP Server","json":"/artifacts/sap-leanix-mcp-server.json"},{"ref":"artifact:sap-samples-hana-cli-claude-plugin","name":"SAP-samples/hana-cli-claude-plugin","json":"/artifacts/sap-samples-hana-cli-claude-plugin.json"},{"ref":"artifact:sap-samples-hana-developer-cli-tool-example","name":"SAP-samples/hana-developer-cli-tool-example","json":"/artifacts/sap-samples-hana-developer-cli-tool-example.json"}]},"by_flavor":{}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[{"task":{"id":"access-external-system-through-mcp-service","name":"Access an external system through an application MCP service","outcome":"An AI agent queries external system data or invokes selected external operations through an application-owned service contract exposed over MCP.","boundary":"The application integrates the target system and selects the data and operations exposed to an agent. This connects [Agent access to your systems](capability:agent-systems-access), [Service integration](capability:service-integration) and [Serve your application over MCP](capability:mcp-servers); direct agent access to an external endpoint without the application layer is a separate design. Cross-system atomic transactions and development-assistance tools are outside this outcome.","origin":"Maintainer-requested CAP bridge use case after acceptance of the complementary MCP capability boundaries (ADR-0066).","aliases":["CAP as a bridge to an external system","wrap an external service in CAP and expose it through MCP","give an AI agent access to remote data through CAP","CAP MCP facade"],"requirement_dimensions":["target API family and permitted use","external protocol","allowed read/write operations","runtime","transport","client and backend authorization","deployment","tenancy"],"primary_capability":"capability:mcp-servers","drafted_with_ai":true,"related_capabilities":[{"ref":"capability:agent-systems-access","role":"Reach external system data and operations through the application."},{"ref":"capability:service-integration","role":"Connect the application service to the external system."}]},"assessment_home":"capability:mcp-servers","assessments":[{"ref":"usecase:access-external-system-through-mcp-service-cap-java-custom-api","ecosystem":"cap","flavors":["java"]},{"ref":"usecase:access-external-system-through-mcp-service-cap-java-sap-api","ecosystem":"cap","flavors":["java"]},{"ref":"usecase:access-external-system-through-mcp-service-cap-node-custom-api","ecosystem":"cap","flavors":["node"]},{"ref":"usecase:access-external-system-through-mcp-service-cap-node-sap-api","ecosystem":"cap","flavors":["node"]}]}],"options":[{"ref":"artifact:abap2ui5-mcp-server","name":"@abap2ui5/mcp-server","json":"/artifacts/abap2ui5-mcp-server.json","ecosystem":"abap","origin_ring":"community-org"},{"ref":"artifact:mariodefelipe-sap-datasphere-mcp","name":"@mariodefe/sap-datasphere-mcp","json":"/artifacts/mariodefelipe-sap-datasphere-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:abap2ui5-vscode-extension","name":"abap2UI5 for VS Code","json":"/artifacts/abap2ui5-vscode-extension.json","ecosystem":"abap","origin_ring":"community-org"},{"ref":"artifact:freight-art-abapsmith","name":"abapsmith","json":"/artifacts/freight-art-abapsmith.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:lemaiwo-ai-core-mcp-server","name":"AI Core MCP Server","json":"/artifacts/lemaiwo-ai-core-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lemaiwo-btp-cf-mcp-server","name":"BTP CF MCP Server","json":"/artifacts/lemaiwo-btp-cf-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lemaiwo-btp-mcp-server","name":"BTP MCP Server","json":"/artifacts/lemaiwo-btp-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lemaiwo-btp-sap-odata-to-mcp-server","name":"btp-sap-odata-to-mcp-server","json":"/artifacts/lemaiwo-btp-sap-odata-to-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:consetto-calmcp","name":"calmcp","json":"/artifacts/consetto-calmcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:sanoberrehman-cap-mcp-bridge","name":"cap-mcp-bridge","json":"/artifacts/sanoberrehman-cap-mcp-bridge.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:lemaiwo-ci-mcp-server","name":"CI MCP Server","json":"/artifacts/lemaiwo-ci-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:gregorwolf-cloud-alm-itsm-mcp","name":"cloud-alm-itsm-mcp","json":"/artifacts/gregorwolf-cloud-alm-itsm-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:costinggeek-sap-mcp","name":"CostingGeek/sap-mcp","json":"/artifacts/costinggeek-sap-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:vadimklimov-cpi-mcp-server","name":"cpi-mcp-server","json":"/artifacts/vadimklimov-cpi-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:hatrigt-hana-mcp-server","name":"hana-mcp-server","json":"/artifacts/hatrigt-hana-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:andreescocard-hybris-mcp-lite","name":"hybris-mcp-lite","json":"/artifacts/andreescocard-hybris-mcp-lite.json","ecosystem":"commerce","origin_ring":"independent"},{"ref":"artifact:yannick-thirion-klystron","name":"Klystron","json":"/artifacts/yannick-thirion-klystron.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-btp-administration-mcp","name":"MCP Server for SAP BTP Administration","json":"/artifacts/sap-btp-administration-mcp.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:1nbuc-mcp-integration-suite","name":"mcp-integration-suite","json":"/artifacts/1nbuc-mcp-integration-suite.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:1nbuc-mcp-is-tpm","name":"mcp-is-tpm","json":"/artifacts/1nbuc-mcp-is-tpm.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:keelside-mcp-sap-cpi","name":"mcp-sap-cpi","json":"/artifacts/keelside-mcp-sap-cpi.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:rahulsethi-sap-datasphere-mcp","name":"mcp-sap-datasphere-server","json":"/artifacts/rahulsethi-sap-datasphere-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:derekvincent-mcp-sap-focusedrun","name":"mcp-sap-focusedrun","json":"/artifacts/derekvincent-mcp-sap-focusedrun.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:midasol-sap-mcp-server","name":"midasol/sap-mcp-server","json":"/artifacts/midasol-sap-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:oisee-odata-mcp","name":"odata_mcp","json":"/artifacts/oisee-odata-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:oisee-odata-mcp-go","name":"odata_mcp_go","json":"/artifacts/oisee-odata-mcp-go.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lemaiwo-odata-mcp-proxy","name":"odata-mcp-proxy","json":"/artifacts/lemaiwo-odata-mcp-proxy.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:yassinbahri-pyrfc-mcp","name":"pyrfc-mcp","json":"/artifacts/yassinbahri-pyrfc-mcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-leanix-mcp-server","name":"SAP LeanIX MCP Server","json":"/artifacts/sap-leanix-mcp-server.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:jumenengels-sac-mcp","name":"sap_analytics_cloud_mcp","json":"/artifacts/jumenengels-sac-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:rahulsethi-sap-bdc-mcp","name":"sap-bdc-mcp","json":"/artifacts/rahulsethi-sap-bdc-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:mariodefelipe-sap-bdc-mcp-server","name":"sap-bdc-mcp-server","json":"/artifacts/mariodefelipe-sap-bdc-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:romankorim-sap-mcp-server","name":"sap-mcp-server","json":"/artifacts/romankorim-sap-mcp-server.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:lopezmas-sap-pi-mcp-server","name":"sap-pi-mcp-server","json":"/artifacts/lopezmas-sap-pi-mcp-server.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:sap-samples-hana-cli-claude-plugin","name":"SAP-samples/hana-cli-claude-plugin","json":"/artifacts/sap-samples-hana-cli-claude-plugin.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-samples-hana-developer-cli-tool-example","name":"SAP-samples/hana-developer-cli-tool-example","json":"/artifacts/sap-samples-hana-developer-cli-tool-example.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:syntaai-sap-security-mcp","name":"sap-security-mcp","json":"/artifacts/syntaai-sap-security-mcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:aiadiguru-sf-mcp","name":"SF-MCP","json":"/artifacts/aiadiguru-sf-mcp.json","ecosystem":"successfactors","origin_ring":"independent"},{"ref":"artifact:skybuffer-ai-mcp-server","name":"Skybuffer AI MCP server","json":"/artifacts/skybuffer-ai-mcp-server.json","ecosystem":"abap","origin_ring":"independent"}],"samples":[],"explained_by":[{"ref":"content:devtoberfest-2026-int-21-mcp-gateway-in-practice","name":"MCP Gateway in Practice: Architecture, configuration, and hands-on","json":"/content/devtoberfest-2026-int-21-mcp-gateway-in-practice.json"},{"ref":"content:teched-2026-in261","name":"Model context protocol (MCP) unlocked: Enable governed access to AI agents","json":"/content/teched-2026-in261.json"},{"ref":"content:teched-2026-st104","name":"SAP Integration Suite as the foundation for enterprise agentic AI","json":"/content/teched-2026-st104.json"},{"ref":"content:teched-2026-tm100","name":"Speed up your cloud journey with agentic data management and configuration","json":"/content/teched-2026-tm100.json"},{"ref":"content:teched-2026-tm267","name":"Transform your configuration of SAP S/4HANA Cloud with agentic AI","json":"/content/teched-2026-tm267.json"}],"normative_context":[{"ref":"instrument:sap-api-policy-v4-2026a","name":"SAP API Policy","json":"/instruments/sap-api-policy-v4-2026a.json","prominence":"prominent","sections":["1.1","1.2","2.2.2"]},{"ref":"instrument:sap-developer-license-3-2-cap","name":"SAP Developer License Agreement","json":"/instruments/sap-developer-license-3-2-cap.json","prominence":"prominent","sections":["1","3"]}]}}