{"ref":"content:ac-agentic-ai-and-ai-agents","page":"/content/ac-agentic-ai-and-ai-agents","json":"/content/ac-agentic-ai-and-ai-agents.json","generated":"2026-10-30","drafted_with_ai":true,"entity":{"id":"ac-agentic-ai-and-ai-agents","title":"Agentic AI & AI Agents","url":"https://architecture.learning.sap.com/docs/ref-arch/98efa0","content_type":"reference-architecture","explains":["capability:agent-tooling","capability:mcp-servers","capability:tool-governance","capability:authentication"],"summary":"SAP's target picture for AI agents: Joule as the engagement layer — Joule Work, Joule Assistants, Joule Agents — with custom agents from customers, partners and SAP teams connecting through A2A for agent-to-agent collaboration and MCP for tool connectivity, on the SAP Business AI Platform. It says up front that parts are not generally available yet, in particular bidirectional communication with third-party agents through the Agent Gateway, so it reads as direction with the building blocks named rather than a design to copy today.","short":"SAP target picture for AI agents with Joule and A2A","authors":["actor:sap-architecture-center"],"published":"2026-08-27","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center — title, contributors and last_update","checked":"2026-09-06"}],"provenance":{"discovered_via":[{"source":"source:architecture-center"}],"first_seen":"2026-09-06"},"drafted_with_ai":true,"published_on":"source:architecture-center","parts":[{"actor":"Business user","key":"user","role":"expresses a goal in Joule, which orchestrates actions across SAP and non-SAP systems","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Users express a goal and Joule orchestrates actions across SAP and non-SAP systems to get it done."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/8-ai-agent-identity/readme.md","title":"RA0029 8-ai-agent-identity/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The user accesses SAP Joule through an application client (mobile or desktop)."}]},{"actor":"Developer","key":"developer","role":"works in their own IDE with the Joule Studio CLI and a coding agent connected via MCP","paths":["joule-studio-pro-code"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The **Pro-Code Flow** uses the Joule Studio CLI (`jl`) with a coding agent (Claude Code or OpenCode) connected via MCP."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"You work locally in your own IDE — the same IBD phases apply, but the coding agent drives implementation."}]},{"actor":"Third-party AI agents and clients","key":"third-party-agents","role":"consume Joule Agents via the Agent Gateway over A2A, or are orchestrated by Joule for SAP-specific tasks","area":"thirdparty","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**AI Agents & Clients:** Google Cloud, Microsoft Azure, AWS, IBM Cloud and other AI platforms and clients — either consuming Joule Agents via the Agent Gateway (A2A) or being orchestrated by Joule for SAP-specific tasks."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Inbound (Agent Gateway — A2A):** Third-party AI platforms and clients consume Joule Agents through the Agent Gateway via A2A. Google Vertex AI, Microsoft Copilot Studio, AWS Bedrock and others can delegate SAP-specific tasks to Joule Agents, with trust established via SAP Cloud Identity Services."}]},{"actor":"External MCP clients","key":"mcp-clients","role":"connect to SAP business capabilities as tools through the MCP Gateway, Microsoft Copilot Studio among them","area":"thirdparty","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Third-Party MCP Access:** External MCP clients — such as Microsoft Copilot Studio — can connect to SAP business capabilities via the MCP Gateway in SAP Integration Suite, providing governed, enterprise-grade tool access without custom MCP server development."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"In this pattern, Copilot Studio acts as the **MCP client**, and the **MCP Gateway in SAP Integration Suite** acts as the governed entry point that exposes SAP APIs, integration flows, and data sources as MCP-compliant tools."}]},{"ref":"artifact:sap-joule","key":"joule","role":"unified AI engagement layer: Joule Work, Joule Assistants and Joule Agents, with the Joule Orchestrator routing requests to agents","area":"baip","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"SAP's approach centers on **Joule** as the unified AI engagement layer: **Joule Work** is where users express intent and AI orchestrates outcomes across systems; **Joule Assistants** coordinate agents across business functions; and **Joule Agents** handle the specific, multi-step tasks that drive real process automation."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"All of this is powered by the **Joule Orchestrator (Agent Harness)**: a multi-step reasoning and orchestration engine that routes requests to agents and loads the tools and skills needed to execute them, including built-in capabilities for grounding and data access across SAP's application landscape."}]},{"ref":"artifact:btp-ai-core","key":"managed-runtime","role":"managed runtime where Joule Studio agents execute","area":"baip","paths":["joule-studio-low-code","joule-studio-pro-code"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/4-integrate-ai-agents-with-joule/readme.md","title":"RA0029 4-integrate-ai-agents-with-joule/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Execution:** When a user's prompt matches the agent's purpose, Joule invokes the corresponding Dialog Function, which in turn delegates the execution to the managed runtime on SAP AI Core where the agent logic resides."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Managed Runtime:** Agents deploy to the SAP-managed runtime — SAP handles scaling, monitoring, and operations. Solutions are accessible immediately after deployment."}]},{"ref":"artifact:sap-joule-work-dev-cli","key":"jl","role":"Joule Studio CLI: initialising projects, managing deployments and connecting to Joule Studio landscapes","paths":["joule-studio-pro-code"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Joule Studio CLI (`jl`):** Command-line interface for initializing projects, managing deployments, and connecting to Joule Studio landscapes."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Managed Runtime:** Same deployment target as the Low-Code Flow — solutions deploy via `jl solution deploy` and register automatically with Joule."}]},{"ref":"artifact:sap-cds","key":"cap","role":"orchestration framework structuring the pro-code agent's use case logic, data management and service integration","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The **SAP Cloud Application Programming Model (CAP)** serves as the orchestration framework for structuring agent use case logic, data management and service integration."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Custom Agents — Bring Your Own Agent:** Pro-code AI agents built with SAP Cloud SDK for AI (Python or TypeScript), deployed in the customer's BTP subaccount and connected to Joule via the A2A protocol."}]},{"ref":"artifact:sap-ai-sdk-orchestration","key":"ai-sdk","role":"SAP Cloud SDK for AI: type-safe access to the Generative AI Hub, foundation models and AI-specific services","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Cloud SDK for AI:** The primary SDK for building pro-code agents on SAP BTP. Provides type-safe abstractions for interacting with Generative AI Hub, foundation models and AI-specific services. Supports both Python and TypeScript/JavaScript development and integrates with popular agent frameworks like LangGraph, AG2 (AutoGen), CrewAI, Smolagents and others."}]},{"ref":"artifact:btp-ai-core","key":"genai-hub","role":"Generative AI Hub: harmonized orchestration service layer with foundation model access","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Generative AI Hub:** Central AI capabilities platform delivered as features within SAP AI Core and SAP AI Launchpad:"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Harmonized Orchestration Service Layer:** Unified API layer providing access to foundation models with built-in capabilities including:"}]},{"ref":"artifact:btp-ai-launchpad","key":"ai-launchpad","role":"managing AI scenarios, deployments and configurations","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP AI Launchpad:** Centralized interface for managing AI scenarios, deployments and configurations"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Generative AI Hub:** Central AI capabilities platform delivered as features within SAP AI Core and SAP AI Launchpad:"}]},{"ref":"artifact:btp-hana-cloud","key":"hana","role":"Vector Engine for semantic retrieval and RAG, Knowledge Graph Engine for reasoning over SAP business objects","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP HANA Cloud:** Provides critical data services for AI agents:"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Vector Engine:** High-performance vector search for semantic retrieval and RAG (Retrieval-Augmented Generation) patterns"}]},{"ref":"artifact:btp-destination","key":"destination","role":"destination management for SAP cloud solutions, third-party applications and on-premise systems","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Destination Service:** Centralized destination management for accessing SAP Cloud Solutions, third-party applications and on-premise systems via HTTPS protocols"}]},{"ref":"artifact:btp-connectivity","key":"connectivity","role":"connectivity to on-premise systems via SAP Cloud Connector","area":"btp","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Connectivity Service:** Secure connectivity to on-premise systems via SAP Cloud Connector"}]},{"ref":"artifact:sap-cloud-connector","key":"scc","role":"reach into on-premise systems","paths":["bring-your-own-agent"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Connectivity Service:** Secure connectivity to on-premise systems via SAP Cloud Connector"}]},{"ref":"artifact:btp-integration-suite","key":"integration-suite","role":"MCP Gateway exposing SAP and non-SAP APIs as governed MCP tools, and A2A Connectivity between SAP and third-party agents","area":"btp","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**MCP Gateway:** Customer-managed, governed MCP exposure for SAP and non-SAP APIs. Provides enterprise-grade tool access with security, rate limiting, observability and lifecycle management built in — without requiring custom MCP server development."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**A2A Connectivity:** Governed, customer-controlled Agent-to-Agent (A2A) communication between SAP-native agents and third-party agents, or between heterogeneous third-party agents."}]},{"ref":"artifact:btp-cloud-identity-services","key":"cids","role":"identity hub for human and agent identities: authentication, authorization and identity federation","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Cloud Identity Services** is the identity hub — managing authentication, authorization and identity federation across all connections."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/8-ai-agent-identity/readme.md","title":"RA0029 8-ai-agent-identity/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"SAP Cloud Identity Services acts as the central identity hub for both human identities and agent identities."}]},{"ref":"external:sap-successfactors","key":"successfactors","role":"SAP cloud solution the agents connect to and the gateway's tools act on","area":"sapcloud","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Integration with SAP Systems:** Seamless connectivity to SAP S/4HANA, SAP SuccessFactors, SAP Concur, SAP Customer Experience, SAP Business Networks and other SAP Cloud Solutions"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP S/4HANA, SuccessFactors, Concur, Customer Experience, Business Data Cloud, custom MCP servers, third-party APIs** | The authoritative systems the tools act on"}]},{"ref":"artifact:btp-business-data-cloud","key":"bdc","role":"governed SAP analytics data the gateway's tools act on","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP S/4HANA, SuccessFactors, Concur, Customer Experience, Business Data Cloud, custom MCP servers, third-party APIs** | The authoritative systems the tools act on"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"\"Summarize Q2 revenue variance by region\" — the agent grounds its answer in governed SAP analytics data rather than ungoverned exports."}]},{"slot":"capability:mcp-servers","key":"external-tools","role":"external MCP servers and APIs that extend agent capabilities","area":"thirdparty","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Tools:** External MCP Servers and APIs that extend agent capabilities and provide additional data sources and actions."}]},{"slot":"capability:mcp-servers","key":"custom-mcp-server","role":"custom MCP server a customer or partner builds and operates on SAP BTP","area":"btp","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/readme.md","title":"RA0029 10-third-party-mcp-access/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"A customer or partner builds and operates a custom MCP server, deploying it on SAP BTP (Cloud Foundry, Kyma, or a containerized workload)."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/readme.md","title":"RA0029 10-third-party-mcp-access/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"This pattern places full operational and security responsibility, including the application code, SAP BTP configuration, credential lifecycle and security hardening, on the customer or partner deploying it. Hosting on SAP BTP reduces infrastructure risk but does not automatically provide governance tooling."}]}],"paths":[{"key":"joule-studio-low-code","name":"Built in Joule Studio's browser-based Low-Code Flow, deployed to the SAP-managed runtime","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Custom agents can be built in Joule Studio and deployed to the SAP-managed runtime or developed and deployed to a customer-managed BTP subaccount."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Two flows are available: a **Low-Code Flow** using the visual, browser-based builder (no local setup required), and a **Pro-Code Flow** using your own IDE with the Joule Studio CLI and a coding agent connected via MCP."}]},{"key":"joule-studio-pro-code","name":"Built in Joule Studio's Pro-Code Flow with the jl CLI and a coding agent, deployed to the SAP-managed runtime","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Two flows are available: a **Low-Code Flow** using the visual, browser-based builder (no local setup required), and a **Pro-Code Flow** using your own IDE with the Joule Studio CLI and a coding agent connected via MCP."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The **Pro-Code Flow** uses the Joule Studio CLI (`jl`) with a coding agent (Claude Code or OpenCode) connected via MCP."}]},{"key":"bring-your-own-agent","name":"Bring your own agent: built with SAP Cloud SDK for AI and CAP in the customer's BTP subaccount, connected to Joule over A2A","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Custom agents can be built in Joule Studio and deployed to the SAP-managed runtime or developed and deployed to a customer-managed BTP subaccount."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Bring Your Own Agent:** Develop agents with full programmatic control using SAP Cloud SDK for AI (Python or TypeScript) and integrate popular frameworks (LangGraph, AG2, CrewAI, Smolagents). Deploy to the customer's BTP subaccount as a self-managed runtime and connect to Joule via the A2A protocol."}]}],"areas":[{"key":"baip","kind":"sap-cloud","label":"SAP Business AI Platform, SAP-managed","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The architecture centers on the **SAP Business AI Platform** — SAP-managed, encompassing Joule Work and its agent runtime — and the **SAP Autonomous Suite**, where agents execute across all lines of business."}]},{"key":"btp","kind":"subaccount","label":"Customer's BTP subaccount","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The customer's own BTP subaccount hosts self-managed agents and integrations — connected to the SAP Business AI Platform via A2A and MCP."}]},{"key":"sapcloud","kind":"sap-cloud","label":"SAP Cloud Solutions","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Destination Service:** Centralized destination management for accessing SAP Cloud Solutions, third-party applications and on-premise systems via HTTPS protocols"}]},{"key":"thirdparty","kind":"third-party","label":"3rd Party Integration","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"External AI platforms, clients and tools connect to the SAP agent ecosystem via open standards — either consuming Joule Agents or providing additional capabilities to agents."}]}],"edges":[{"from":"user","to":"joule","kind":"data","for":"expresses a goal; Joule orchestrates actions across SAP and non-SAP systems to get it done","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Users express a goal and Joule orchestrates actions across SAP and non-SAP systems to get it done."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/8-ai-agent-identity/readme.md","title":"RA0029 8-ai-agent-identity/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The user accesses SAP Joule through an application client (mobile or desktop)."}]},{"from":"joule","to":"cids","kind":"authentication","for":"authenticates the user via SAP Cloud Identity Services, with optional federation to a corporate identity provider","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/8-ai-agent-identity/readme.md","title":"RA0029 8-ai-agent-identity/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"SAP Joule authenticates the user via SAP Cloud Identity Services (with optional federation to a corporate Identity Provider)."}]},{"from":"joule","to":"managed-runtime","kind":"data","for":"invokes the Dialog Function, which delegates the execution to the managed runtime on SAP AI Core where the agent logic resides","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/4-integrate-ai-agents-with-joule/readme.md","title":"RA0029 4-integrate-ai-agents-with-joule/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Execution:** When a user's prompt matches the agent's purpose, Joule invokes the corresponding Dialog Function, which in turn delegates the execution to the managed runtime on SAP AI Core where the agent logic resides."}]},{"from":"joule","to":"cap","kind":"data","protocol":"a2a","for":"acting as an A2A client, sends the task to the pro-code agent's A2A server endpoint","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Joule, acting as an **A2A client**, sends a request to the remote agent's **A2A server** endpoint. The request contains the task details and necessary context."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Agent2Agent (A2A) Protocol:** Pro-code agents expose A2A-compliant server endpoints to integrate with Joule, enabling external systems to delegate tasks to custom agents"}]},{"from":"cap","to":"cids","kind":"trust","for":"an IAS App2App trust relationship between Joule and the agent server secures the inbound communication and validates server updates","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"To ensure secure inbound communication and validate server updates, an Identity Authentication Service (IAS) App2App trust relationship must be established between Joule and the target agent server."}]},{"from":"developer","to":"jl","kind":"data","for":"initialises the project and manages deployments from their own IDE","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Joule Studio CLI (`jl`):** Command-line interface for initializing projects, managing deployments, and connecting to Joule Studio landscapes."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"You work locally in your own IDE — the same IBD phases apply, but the coding agent drives implementation."}]},{"from":"jl","to":"managed-runtime","kind":"provisioning","for":"deploys the solution with jl solution deploy to the managed runtime, which registers it automatically with Joule","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/2-building-ai-agents-with-joule-studio/readme.md","title":"RA0029 2-building-ai-agents-with-joule-studio/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Managed Runtime:** Same deployment target as the Low-Code Flow — solutions deploy via `jl solution deploy` and register automatically with Joule."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/4-integrate-ai-agents-with-joule/readme.md","title":"RA0029 4-integrate-ai-agents-with-joule/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Execution:** When a user's prompt matches the agent's purpose, Joule invokes the corresponding Dialog Function, which in turn delegates the execution to the managed runtime on SAP AI Core where the agent logic resides."}]},{"from":"ai-sdk","to":"genai-hub","kind":"data","for":"accesses foundation models through the harmonized orchestration service layer's unified API, with prompt templates, grounding data and safety controls","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Foundation Model Access:** The agent leverages Generative AI Hub's harmonized orchestration service layer to access foundation models through a unified API, utilizing prompt templates, grounding data and safety controls (data masking, I/O filtering)."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Cloud SDK for AI:** The primary SDK for building pro-code agents on SAP BTP. Provides type-safe abstractions for interacting with Generative AI Hub, foundation models and AI-specific services. Supports both Python and TypeScript/JavaScript development and integrates with popular agent frameworks like LangGraph, AG2 (AutoGen), CrewAI, Smolagents and others."}]},{"from":"cap","to":"hana","kind":"data","for":"queries the Vector Engine for semantic search and the Knowledge Graph for domain-specific reasoning over SAP business objects","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Data & Knowledge Integration:** Agents query SAP HANA Cloud's Vector Engine for semantic search and leverage Knowledge Graph for domain-specific reasoning over SAP business objects."}]},{"from":"cap","to":"destination","kind":"data","for":"accesses SAP and non-SAP systems using the Destination service, through CAP's built-in connectivity","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Service Integration:** Through CAP's built-in connectivity, agents access SAP and non-SAP systems using SAP Destination Service and SAP Connectivity Service, ensuring secure and governed integrations."}]},{"from":"cap","to":"connectivity","kind":"data","for":"reaches on-premise systems using the Connectivity service, through CAP's built-in connectivity","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Service Integration:** Through CAP's built-in connectivity, agents access SAP and non-SAP systems using SAP Destination Service and SAP Connectivity Service, ensuring secure and governed integrations."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP Connectivity Service:** Secure connectivity to on-premise systems via SAP Cloud Connector"}]},{"from":"cap","to":"successfactors","kind":"data","for":"connects to SAP cloud solutions, SAP SuccessFactors among them","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Integration with SAP Systems:** Seamless connectivity to SAP S/4HANA, SAP SuccessFactors, SAP Concur, SAP Customer Experience, SAP Business Networks and other SAP Cloud Solutions"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Service Integration:** Through CAP's built-in connectivity, agents access SAP and non-SAP systems using SAP Destination Service and SAP Connectivity Service, ensuring secure and governed integrations."}]},{"from":"cap","to":"integration-suite","kind":"data","protocol":"mcp","for":"consumes tools and capabilities through SAP Integration Suite-managed MCP servers","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Custom Agents leverage SAP Integration Suite-managed MCP Servers for tool and capability consumption."}]},{"from":"cap","to":"external-tools","kind":"data","protocol":"mcp","for":"queries MCP servers to discover tools and invokes the required tool via the MCP interface","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"It queries relevant **MCP servers** to discover available tools."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**MCP Tool Invocation:** The agent invokes the required tool via the MCP interface, passing the necessary parameters. The MCP server processes the request and returns the result."}]},{"from":"third-party-agents","to":"joule","kind":"data","protocol":"a2a","for":"consume Joule Agents through the Agent Gateway via A2A; SAP says this communication through the Agent Gateway is not yet supported","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Inbound (Agent Gateway — A2A):** Third-party AI platforms and clients consume Joule Agents through the Agent Gateway via A2A. Google Vertex AI, Microsoft Copilot Studio, AWS Bedrock and others can delegate SAP-specific tasks to Joule Agents, with trust established via SAP Cloud Identity Services."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"In particular the bidirectional communication with 3rd-party and self-hosted agents through Agent Gateway is not yet supported."}]},{"from":"joule","to":"third-party-agents","kind":"data","protocol":"a2a","for":"orchestrates external agents built with any A2A-compliant framework for SAP-specific tasks","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Outbound (Bring Your Own Agent — A2A):** Joule orchestrates external agents built with any A2A-compliant framework. Supports synchronous communication, asynchronous callbacks for long-running tasks and multi-turn conversations with context handling."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**AI Agents & Clients:** Google Cloud, Microsoft Azure, AWS, IBM Cloud and other AI platforms and clients — either consuming Joule Agents via the Agent Gateway (A2A) or being orchestrated by Joule for SAP-specific tasks."}]},{"from":"third-party-agents","to":"cids","kind":"authentication","for":"external clients authenticate using IAS App2App dependencies, establishing a trust relationship with Joule","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md","title":"RA0029 5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Authentication:** External clients authenticate using IAS App2App dependencies, establishing a trust relationship between the external application and Joule"}]},{"from":"third-party-agents","to":"integration-suite","kind":"data","protocol":"a2a","for":"consume Joule Agents and other third-party agents through the A2A Connectivity of SAP Integration Suite","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md","title":"RA0029 5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"SAP Integration Suite provides the **A2A Connectivity** that enables external clients and applications to seamlessly consume Joule Agents and other 3rd party Agents through the A2A protocol."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Agent2Agent (A2A) connectivity via SAP Integration Suite**, for governed, enterprise-grade multi-party interaction between SAP and 3rd Party agents."}]},{"from":"integration-suite","to":"joule","kind":"data","protocol":"a2a","for":"delegates the A2A call to the Agent Gateway, which routes it to the Joule Agent","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Agent2Agent (A2A) connectivity via SAP Integration Suite**, for governed, enterprise-grade multi-party interaction between SAP and 3rd Party agents."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Agent to Agent interaction in SAP Integration Suite delegates the call to Agent Gateway to ensure common security and controlled access."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md","title":"RA0029 5-integrate-joule-agents-and-tools-into-your-ecosystem/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Execution:** The Agent Gateway routes the request to the appropriate Joule Agent (whether low-code or pro-code)"}]},{"from":"mcp-clients","to":"integration-suite","kind":"data","protocol":"mcp","for":"a Copilot Studio agent connects to the MCP Gateway over MCP with the Streamable HTTP transport and authenticates with OAuth 2.0","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The Copilot Studio agent connects to the gateway over **MCP using the Streamable HTTP transport** and authenticates with **OAuth 2.0**."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/readme.md","title":"RA0029 readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Third-Party MCP Access:** External MCP clients — such as Microsoft Copilot Studio — can connect to SAP business capabilities via the MCP Gateway in SAP Integration Suite, providing governed, enterprise-grade tool access without custom MCP server development."}]},{"from":"integration-suite","to":"cids","kind":"authentication","protocol":"oidc","for":"the MCP Gateway validates the token (OIDC) and SAP Cloud Identity Services resolves it to the SAP identity","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The MCP Gateway validates the token (OIDC), and SAP Cloud Identity Services resolves it to the corresponding SAP identity"}]},{"from":"integration-suite","to":"successfactors","kind":"data","for":"validates the token, applies governance policy and routes the tool call to the underlying SAP system","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The gateway validates the token, applies governance policy, and routes the request to the underlying SAP or non-SAP system."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP S/4HANA, SuccessFactors, Concur, Customer Experience, Business Data Cloud, custom MCP servers, third-party APIs** | The authoritative systems the tools act on"}]},{"from":"integration-suite","to":"bdc","kind":"data","for":"routes the tool call to governed SAP analytics data","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"The gateway validates the token, applies governance policy, and routes the request to the underlying SAP or non-SAP system."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**SAP S/4HANA, SuccessFactors, Concur, Customer Experience, Business Data Cloud, custom MCP servers, third-party APIs** | The authoritative systems the tools act on"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md","title":"RA0029 10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"\"Summarize Q2 revenue variance by region\" — the agent grounds its answer in governed SAP analytics data rather than ungoverned exports."}]},{"from":"integration-suite","to":"external-tools","kind":"data","for":"exposes third-party APIs and external MCP servers as MCP-compliant tools under the same governed entry point","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Flexible Exposure:** SAP APIs, third-party APIs, external MCP servers, integrations, and data sources can all be exposed as MCP-compliant tools"}]},{"from":"mcp-clients","to":"custom-mcp-server","kind":"data","protocol":"mcp","for":"a third-party or custom MCP server connects the agent platform to SAP APIs, with the operational responsibility on whoever deploys it","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/readme.md","title":"RA0029 10-third-party-mcp-access/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"Customers and partners building custom MCP servers or using third-party MCP servers to connect agent platforms to SAP APIs **should be aware of these open concerns and the controls required to address them**, covered in detail below."},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/readme.md","title":"RA0029 10-third-party-mcp-access/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"A customer or partner builds and operates a custom MCP server, deploying it on SAP BTP (Cloud Foundry, Kyma, or a containerized workload)."}]},{"from":"custom-mcp-server","to":"cids","kind":"authentication","for":"every inbound request to the MCP server and every outbound call to an SAP API is authenticated through identity and access management flows managed in SAP Cloud Identity Services","sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/10-third-party-mcp-access/readme.md","title":"RA0029 10-third-party-mcp-access/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Authentication & Authorization:** Every inbound request to the MCP server and every outbound call to an SAP API must be authenticated. Use identity and access management flows managed through [SAP Cloud Identity Services](https://help.sap.com/docs/cloud-identity-services). Never store long-lived credentials in MCP servers."}]}],"roles":[{"key":"engagement-layer","part":"joule"},{"key":"custom-agent","name":"Custom agent, bring your own agent","capability":"capability:agent-tooling","protocol":"a2a","direction":"in","parts":["cap","ai-sdk"],"sources":[{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/3-bring-your-own-agent/readme.md","title":"RA0029 3-bring-your-own-agent/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"**Agent2Agent (A2A) Protocol:** Pro-code agents expose A2A-compliant server endpoints to integrate with Joule, enabling external systems to delegate tasks to custom agents"},{"url":"https://raw.githubusercontent.com/SAP/architecture-center/main/docs/ref-arch/RA0029/1-a2a-and-mcp/readme.md","title":"RA0029 1-a2a-and-mcp/readme.md in SAP/architecture-center","checked":"2026-10-09","quote":"For pro-code agents, exposing an **A2A-Server endpoint** is the primary mechanism for integrating with Joule."}]}],"history":[{"date":"2026-10-09","field":"parts","from":null,"to":"21 parts, 26 edges, 4 areas","reason":"Filled from SAP's own readmes at the maintainer's request; the AI-native door reads these designs. Every part names what the graph holds; what it lacks is listed as candidates in the curation note."},{"date":"2026-10-09","field":"explains","from":"agent-tooling, mcp-servers, tool-governance","to":"agent-tooling, mcp-servers, tool-governance, authentication","reason":"The agent identity page describes SAP Cloud Identity Services as the identity hub for human and agent identities, with authentication, provisioning and authorization for agents as a class of actors, which is this concern for agents."}]},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"good","evidence":"up as of 2026-10-30"},{"label":"Source updated","tier":"good","evidence":"2026-10-26 by the publisher"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"good","evidence":"no recorded change after 2026-08-27"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":null,"unit":"views"},{"value":null,"unit":"comments"},{"value":null,"unit":"likes"}]},"signals":{"crawled_at":"2026-10-30","reachable":true,"source_updated":"2026-10-26"},"series":null,"edges":{"authors":[{"ref":"actor:sap-architecture-center","name":"SAP Architecture Center","json":"/actors/sap-architecture-center.json"}]}}