SAP Joule Agents: Joule Agents List, SAP Joule AI Agents and Assistants

SAP draws a distinction on its own product pages that almost every summary blurs, and it matters as soon as you start reading the roadmap. There are two different things with similar names.

Joule Agents are, in SAP's wording, "ready-to-use AI agents that provide business users with decision support and task automation requiring non-deterministic workflows." They "choose from a large set of tools (including Joule skills, other agents, and third-party applications) to action their plans, as well as reflect on the results to draw conclusions and make recommendations." An agent is the thing that does a job: proposing accruals, comparing supplier bids, routing a service case.

Joule Assistants sit a level above. SAP says they "turn intent into action by using deep role and process context to coordinate Joule Agents and execute complex workflows across the business," and that they "surface through Joule Work." An assistant is role-shaped rather than task-shaped. It knows you are a controller or a category manager and it directs the agents that do the individual pieces.

Both are grounded the same way. SAP points them at "a unified, trusted data layer in SAP Business Data Cloud, enriched with business semantics and powered by SAP Knowledge Graph," which is the mechanism behind SAP's claim that the agents understand how data, processes and policies connect rather than reading isolated records.

One consequence worth noting early: when a licensing conversation refers to "activating three Joule assistants," it means the coordinating layer, not three individual task agents. The two words are not interchangeable in a contract.

SAP organizes the catalog into five domains, branded as the Autonomous Suite at Sapphire 2026: Autonomous Finance, Autonomous Spend, Autonomous Supply Chain, Autonomous HCM and Autonomous CX. The full 224 is not published as a single public list, and SAP surfaces it as browsable groups by business function instead. The named agents below are the ones SAP and its launch coverage have identified specifically, with the availability guidance stated at announcement.

Two things stand out in that table. The first is how heavily the named agents cluster in finance and spend, which is where SAP has the deepest process coverage and where the audit trail matters most. The second is that several entries are assistants rather than agents, sitting in the same announcements, which is part of why the headline numbers get repeated inconsistently.

Fewer than 224. That number counts what SAP announced across the Autonomous Suite, not what is generally available in a production tenant, and the gap is the single most useful thing to understand before you plan around it.

Forrester, reviewing the Sapphire 2026 announcements, put it plainly: "Most of the 224 agents and 51 assistants sit in mixed GA, early-adopter, and preview status." SAP Insider reported the Autonomous Suite itself as "developed under an ISO-certified process designed for SOX audit compatibility," with "GA targeting Q3 or later." So the suite as a whole is a second-half-of-2026 story even though individual agents shipped earlier.

Forrester added a caveat about the ones that did ship earlier, describing those GA dates as "demo-ready capabilities, not full enterprise readiness at Fortune 500 scale." Two more specifics from the same analysis are worth carrying into a planning conversation: agent-to-agent interoperability inside Joule Work, the piece that makes agents coordinate rather than run in isolation, is not available until Q4 2026, and company memory launched with "zero public production references at announcement."

None of that makes the roadmap unserious. SAP is shipping, and the finance and HCM agents named above have dates attached. It does mean the practical question is never "how many agents does SAP have." It is "which three agents do I need, what status is each one in, and what is the date on the one that gates the others."

How do you check the real status of a specific Joule agent?

Check the agent individually rather than trusting a suite-level statement. SAP publishes per-product roadmap entries, and your account team can confirm whether a given agent is GA, in an early adopter program, or in preview for your region and edition. Ask for the status in writing per agent, because a single announcement routinely contains all three.

This is the gate that ends most Joule conversations, and it has nothing to do with budget. Joule agents are a cloud ERP capability. RISE with SAP and GROW with SAP customers are in scope. Classic on-premise S/4HANA, SAP ECC and SAP Business One have no native Joule access.

SAP Insider's Sapphire coverage described the boundary in terms of commitment rather than technology: AI capabilities are restricted to customers "on their transformation journey" to cloud ERP, and on-premise ECC customers can reach agents only if they have "already committed to transforming." In practice that means the migration is the prerequisite, not a later optimization.

There is also a contractual detail in the updated RISE and GROW offerings that is easy to miss and worth reading carefully: they include "a contractual commitment to activate three Joule assistants in Year 1." That is an obligation on the customer side, not just an entitlement. If you are negotiating a renewal, understand which three assistants you are agreeing to stand up and who owns that work internally.

If your estate lands in the bottom three rows, the honest answer is that the Joule roadmap is not a plan you can execute this year. Our SAP AI agents page covers what connects to the SAP you actually run today, including ECC and Business One.

Business AI Base, which covers embedded AI and the interactive Joule assistant, has been bundled with RISE with SAP and S/4HANA Cloud since July 2025. The agents live in Joule Premium, which is a paid add-on that consumes AI Units as it works. SAP does not publish a public rate card for AI Units, so every figure below comes from licensing advisors reading real quotes rather than from SAP, and should be treated as a benchmark to negotiate against rather than a price.

The structural point that matters more than any single number: agents are not priced like chat. Advisors consistently report that an agentic task consumes roughly 5 to 10 times what an interactive prompt consumes, because an agent runs multiple reasoning steps, calls tools, and reflects on results. Reported per-step consumption is tiered by agent complexity, at roughly 0.005 AI Units per step for basic agents, 0.01 for standard, and 0.025 for advanced.

Two commercial details are worth putting in front of whoever signs. Overage, charged once included units are exhausted, is reported at 150 to 200 percent of contracted per-unit rates, which makes an underestimate expensive rather than merely wrong. And use-based pricing became the default at SAP cloud renewal from July 2026, so a renewal is the moment this model arrives whether or not you asked for it. Forrester flagged the follow-on effect bluntly, warning that "the 2027 pricing cliff is unmodeled in most customer 2026 budgets."

Our SAP Joule pricing breakdown goes through AI Units, the per-action numbers advisors report, and how to model a budget before signing.

Ready-made agents are only half the story. The agent builder in Joule Studio reached general availability in Q1 2026, which is what turned Joule from a fixed catalog into a platform. SAP describes the build experience as creating agents by "simply describing desired business outcome in plain language," with teams able to work low-code or pro-code and to "leverage agent frameworks such as LangChain and LlamaIndex for full flexibility and control."

At Sapphire 2026 SAP announced Joule Studio 2.0 with a fully managed agent builder, which removes the need to provision Cloud Foundry or AI Core yourself, targeting GA in Q3 2026. Three interoperability pieces sit alongside it and are the parts worth understanding if you are planning an architecture rather than a pilot:

The A2A direction is the strategically interesting one. It means SAP is not assuming every agent in your landscape will be an SAP agent, which is the same conclusion Microsoft reached when it built a registry that syncs agents from outside platforms. If you are mapping how agent governance is converging across vendors, our Microsoft Agent 365 page covers the equivalent control plane on the Microsoft side.

SAP AI Agent Hub is the governance surface, and SAP positions it as vendor-agnostic rather than SAP-only. It offers a centralized dashboard giving "a clear, unified view of all agents in use," explicitly including custom and third-party agents, plus a KPI dashboard covering governance, adoption and ROI. SAP calls it a "single, vendor-agnostic command center" for discovering, inventorying and governing agents across the landscape.

That framing is a tell about where enterprise agent management is heading. The assumption is no longer that you buy agents from one vendor; it is that you will end up with agents from several and need one inventory. Anyone who has watched shadow IT arrive will recognize the shape of the problem.

What model does SAP Joule use?

Anthropic's Claude is embedded in Joule as part of SAP's partner ecosystem, and coverage of the Sapphire 2026 Autonomous Suite describes Claude as the primary reasoning layer behind the agents. Forrester treated that as a genuine risk rather than a feature, warning that "Claude as the anchor creates concentration risk that becomes board-level in regulated industries within 24 months." Whether you weigh that as a concern depends on your regulator and your appetite for model portability, but it belongs in an architecture review.

How much time do Joule agents actually save?

SAP's headline claim is a reduction in time spent on multi-step workflows of up to 75 percent. Read the footnote before you use that number in a business case: SAP states the figures are "assumed for consumer products company with €1 billion in revenue and 2,000 employees," that annual benefits "result from one or more value drivers," and that the source is SAP Value Management. It is a model, not a measurement from your estate, and it describes a large company with a specific profile.

Plenty of SAP shops read all of the above and land in the same place: the agents they want are preview-only, or their estate is on-premise, or the AI Unit commitment is not something they can size honestly this year. That is a common position, not a failure of planning.

The alternative is straightforward. A ready-made agent connects to the SAP you already run through the interfaces you already expose, usually OData services on S/4HANA, the Service Layer or DI API on Business One, or whatever middleware sits in front of ECC. It does the same repetitive work: matching invoices to purchase orders and goods receipts, chasing suppliers for missing documents, keeping master data clean, following up overdue receivables. It runs at a published flat rate instead of a metered one, and it does not require a migration first.

What it does not do is reason across the SAP Knowledge Graph the way a native Joule agent does. That is a real difference and worth being honest about. For high-volume, rules-clear work in AP and master data, it rarely matters. For cross-functional planning work, it does.

Browse the agents above by category, or start with the finance agents if your first target is the AP and close workload most SAP teams start with.