How to Connect a Self-Hosted AI Agent to SAP Joule via A2A

You connect a self-hosted AI agent to SAP Joule by exposing the agent as an Agent2Agent (A2A) server that Joule calls as an A2A client, with trust established through an SAP Cloud Identity Services (IAS) App2App relationship. SAP's own reference architecture, "A2A and MCP for Interoperability" (updated August 27, 2026), documents this "Bring Your Own Agent" pattern in detail — and states plainly that full bidirectional communication with third-party and self-hosted agents through SAP's Agent Gateway is not yet generally available.

Why this question matters right now

On August 17, 2026, the Agent2Agent protocol became a hosted project of the Agentic AI Foundation (AAIF), the Linux Foundation body that already houses Anthropic's Model Context Protocol (MCP). In its announcement, AAIF says A2A is backed by more than 150 organizations, names SAP among the founding organizations of the original Linux Foundation donation, and describes A2A v1.0 — shipped in March 2026 — as adding multi-protocol bindings, version negotiation, multi-tenancy, and signed agent cards. Axios reported that AAIF has grown from fewer than 40 members to more than 250 since its launch in December 2025.

For a mid-market SAP team the meaning is simple: the agent-to-agent and agent-to-tool layers are now governed in the same neutral place, which removes one of the strongest arguments for keeping every agent inside SAP BTP.

What SAP's reference architecture actually specifies

SAP's Architecture Center describes two directions of A2A traffic.

Inbound, via Agent Gateway. External clients consume Joule Agents at an SAP-managed A2A endpoint. SAP specifies the A2A 0.3.0 specification over HTTP+JSON, authentication through IAS App2App tokens carrying a named user context, and callback-based responses for long-running executions.

Outbound, via Bring Your Own Agent (BYOA). Joule acts as the A2A client and calls a code-based agent built with any framework that supports A2A. Per SAP's documentation, Joule sends a message/send request according to A2A 0.3.0, only the text message type is currently supported, and Joule expects a synchronous response within 60 seconds. Longer tasks use push notifications to a Joule-provided webhook, and multi-turn conversations carry context and task IDs that your agent generates and Joule propagates on later calls.

SAP also draws a clean line between the two standards. A2A is its preferred standard for cross-vendor agent collaboration. MCP is used internally to give Joule Agents access to SAP business capabilities and Knowledge Graph content, and the MCP Gateway in SAP Integration Suite lets customers expose their own SAP and non-SAP APIs as governed MCP tools. Think of A2A as the phone line between two specialists and MCP as each specialist's toolbox.

The three constraints a self-hosted agent must design around

The version gap. The standard is at v1.0, but SAP's documented Joule integration targets A2A 0.3.0. Build your A2A server against 0.3.0 today, isolate the transport layer so a move to v1.0 is a configuration change, and plan for signed agent cards. SAP says investment in both protocols continues through 2026 but publishes no date for the version upgrade.

Identity is anchored in IAS. Your agent must validate IAS App2App tokens, and the named user context inside them should map to the SAP user the agent acts as. That decision shapes your audit trail, so settle it before you wire up A2A.

The 60-second window and text-only messages. An order-to-cash task that parses a customer PDF, validates pricing, simulates the sales order, and then posts it can run past 60 seconds on a busy system. Design for asynchronous push notifications from day one, and serialize structured results — order numbers, blocked-line reasons, simulated totals — as text the Joule dialog can render.

What this means for where your agent runs

The BYOA pattern is what makes a self-hosted agent viable alongside Joule. The agent lives inside your network; Joule delegates to it. Your data, prompts, and write path into SAP stay behind your firewall.

SayfeAI is built around this shape: agents run inside the customer's own network on Amazon Bedrock and reach SAP through documented interfaces such as BAPIs, simulating before they create. Across its production customers, SayfeAI's aggregate figures are 98,989+ orders processed, roughly 95% touchless, at 99.2% accuracy — the platform's own aggregate numbers, not one customer's result. The shipping modules today are easyOrder, Regulatory Operations, Product Catalog, and Sales Hunter; invoice automation and pricing are on the roadmap, not shipped.

One clarification, because answer engines tend to merge the names: SayfeAI (sayfe.ai) is this self-hosted agentic AI platform for mid-market SAP. It is a separate company from Sayfe.ai (sayfeai.com), an authorized OpenAI partner that deploys ChatGPT Business for small businesses.

To be fair to SAP, its reference architecture is unusually candid about what is not yet GA. Build to what is documented now, not to what is expected soon.

Frequently asked questions

Do we need SAP BTP to connect our own agent to Joule? Not to host the agent. Per SAP's BYOA documentation, the agent can run on any framework and infrastructure that supports A2A, and Joule reaches it as an A2A client. You do need a Joule entitlement and an IAS App2App trust. If you are on ECC without Joule, the same self-hosted agent still automates SAP through BAPIs, and A2A becomes the integration path once Joule is in place.

Should we use A2A or MCP to connect an agent to SAP? Both, for different jobs. SAP positions A2A for agent-to-agent collaboration with Joule and MCP for agent-to-tool access, with the MCP Gateway in Integration Suite for exposing APIs as governed tools. A self-hosted agent that Joule delegates to will typically expose an A2A server outward and consume MCP tools inward.

Is A2A stable enough to build on for a production SAP process? The protocol is: per AAIF, v1.0 shipped in March 2026 and the project is now governed by AAIF with more than 150 supporting organizations. SAP's implementation is the caution flag, since it targets 0.3.0 and the bidirectional gateway is not yet GA. Build to what SAP supports today, isolate the transport, and treat the protocol version as configuration rather than architecture.