What problem does it solve? Teams connecting tools, middleware, AI agents, or data pipelines to SAP often cannot tell whether a given interface is a Published API permitted for their use case, and SAP publishes no binary compliant/not-compliant decision matrix. This Skill produces a conservative, evidence-based technical assessment with a confidence level, an evidence ledger, and concrete questions to raise with SAP. ## Core Features & Use Cases - Policy Alignment Assessment: Classifies a scenario as Likely aligned, Likely not aligned, Needs SAP confirmation, or Not assessable from provided facts, based on SAP API Policy v.4.2026a and FAQ v1.2. - Evidence Gathering Playbooks: Guides runtime checks of SAP Docs, API Hub, SAP Notes, Roadmap, and ARC-1 MCP servers with a source-authority hierarchy and confidence rubric. - Inventory Scan Mode: Triages a whole list of interfaces (OData services, RFC/BAPIs, CDS views, custom Z/Y objects) into a timestamped status table with a portfolio verdict. - Use Case: An architect asks whether an AI agent may call S/4HANA OData services through a custom MCP server; the Skill checks Published-API status, agentic-access controls (§2.2.2a), and endorsed pathways like the Integration Suite MCP Gateway, then returns a sourced assessment. ## Quick Start Ask the assistant to assess whether your planned way of calling a specific SAP API or interface is allowed under the SAP API Policy, naming the product, deployment, and interface.
