You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/_partials/acb-start-desktop.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ If an Anypoint Platform session is active in any of your browsers when you insta
86
86
[[update-pack]]
87
87
=== Update Anypoint Extension Pack
88
88
89
-
If Anypoint Extension Pack is installed on your desktop IDE, update to the latest version of the extension pack by following VS Code instructions in https://code.visualstudio.com/docs/editor/extension-marketplace#_update-an-extension-manually[Update an extension manually^].
89
+
If Anypoint Extension Pack is installed on your desktop IDE, update to the latest version of the extension pack by following VS Code instructions in https://code.visualstudio.com/docs/configure/extensions/extension-marketplace#_update-an-extension-manually[Update an extension manually^].
90
90
91
91
[[uninstall-pack]]
92
92
=== Uninstall Anypoint Extension Pack
@@ -103,6 +103,6 @@ To uninstall:
103
103
. In the Anypoint Extension Pack tab that opens, click *Uninstall*.
104
104
. To remove the Anypoint Code Builder extensions from the Extensions panel, click *Reload* on one of the extensions.
105
105
106
-
For additional guidance, see the VS Code documentation, https://code.visualstudio.com/docs/editor/extension-marketplace#_manage-extensions[Manage extensions^].
106
+
For additional guidance, see the VS Code documentation, https://code.visualstudio.com/docs/configure/extensions/extension-marketplace#_manage-extensions[Manage extensions^].
@@ -127,4 +127,4 @@ Deploy your agent network instance to a deployment target. You can deploy to a C
127
127
* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]
128
128
* xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-project-deploy[Deploy Your Network Using the Anypoint CLI]
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-agent-networks.adoc
+75-9Lines changed: 75 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,67 @@
1
1
= Building Agent Networks for Agent Fabric
2
2
3
-
Agent Fabric manages and coordinates the execution of agents across your enterprise, regardless of where they're deployed. Agent Fabric solves the problem of integrating and automating complex processes that involve multiple agents and tools.
3
+
An agent network is a coordinated group of agents, brokers, LLMs, and MCP servers that acts as a central hub for defining, validating, and executing agentic processes across your enterprise.
4
4
5
-
Complex tasks often require a series of steps, with each step handled by a different agent or tool. Managing this process manually is difficult and error-prone. Agent networks (networks of agents in a domain) act as central hubs for defining, validating, and executing these multi-step processes.
5
+
An agent network provides the building blocks of your agentic deployment while MuleSoft Agent Fabric helps you maximize the potential of every AI agent with centralized discovery, orchestration across agents and tools, cross-ecosystem governance, and full transparency into agentic interactions.
6
6
7
-
Define your agent network in a simple, human-readable YAML file in Anypoint Code Builder. This approach abstracts away the underlying technical complexities so you focus on the business constraints and context of your process without needing to understand the inner workings of the orchestration engine.
7
+
You define your agent network in a simple, human-readable YAML file in Anypoint Code Builder. This approach abstracts away the underlying technical complexities, allowing you to focus on the business constraints and context of your process without needing to understand the inner workings of the orchestration engine.
8
8
9
-
Don't worry, we give you a head start by providing you with a YAML template in your agent network project. MuleSoft Vibes can help you configure it for your business environment, publish agent network assets to Anypoint Exchange, and deploy your agent network instance.
9
+
At the start of a new agent network project, we provide a YAML template to give you a head start. You can use MuleSoft Vibes to configure your network, publish the assets to Anypoint Exchange, and deploy your agent network instance.
10
10
11
-
For more information about Agent Fabric, see xref:agent-fabric::index.adoc[].
11
+
[[key-benefits]]
12
+
== Key Benefits of Agent Networks
12
13
14
+
Create robust, automated agent networks with these key benefits.
15
+
16
+
* Simplified Development
17
+
+
18
+
Define your agent processes in an intentional way using a simple YAML file, which is easier and faster than writing complex code.
19
+
* Safety and Governance
20
+
+
21
+
Ensure control and compliance across every agent and tool interaction with enterprise-grade governance.
22
+
* Observability
23
+
+
24
+
Gain insight into agent actions with a visual trace of their decision-making.
25
+
* Flexibility
26
+
+
27
+
Coordinate any type of agent and tool, regardless of where it’s built and deployed so you can build a diverse network of agents.
28
+
* Tool and Agent Invocation
29
+
+
30
+
Manage the invocation of both deterministic (tool-based) and probabilistic (LLM-based) actions.
31
+
32
+
[[example-use-case]]
33
+
== Example Use Case: Employee Onboarding
34
+
35
+
In this example, the goal is to seamlessly activate a new hire across HR, IT, Security, and Facilities with a single, policy‑governed experience.
36
+
37
+
Here’s how it works:
38
+
39
+
* Discover
40
+
+
41
+
Publish existing agents and tools (HRIS, Identity, ITSM, Payroll, Facilities, LMS) in Anypoint Exchange for reuse.
42
+
* Orchestrate
43
+
+
44
+
An agent broker decomposes the task of onboarding the new hire (create HR record, provision identity, assign hardware, grant app access, enroll in benefits and training), calling MCP and A2A agents as needed, with human‑in‑the‑loop approvals where required.
45
+
* Govern
46
+
+
47
+
Flex Gateway enforces authentication, least‑privilege access, and guardrails. API Manager policies ensure consistent controls across all calls and data exchanges.
48
+
* Observe
49
+
+
50
+
Monitoring and traces (beta) give end‑to‑end visibility into progress, failures, and latency. Visualization shows which agents interacted and where bottlenecks occurred.
51
+
Reuse
52
+
+
53
+
The onboarding definition (YAML) is versioned and shareable, enabling rapid adaptation for roles, regions, or subsidiaries without rebuilding flows.
54
+
* Trust and Compliance
55
+
+
56
+
Centralized credentials, audit trails, and policy inheritance support security, privacy, and regulatory requirements (PII handling, approvals, and separation of duties).
57
+
58
+
With this experience, you get faster time‑to‑productivity, fewer handoffs, lower error rates, and a consistent new‑hire experience across the enterprise.
59
+
60
+
[[agent-network-components]]
13
61
== Agent Network Components
14
62
15
-
Agent networks support brokers, A2A-compliant agents, and Model Context Protocol (MCP) servers.
63
+
An agent network is a collection of agents, brokers, LLMs, and MCP servers that are connected to each other. Agent networks use LLMs for reasoning and planning capabilities and integrate with Anypoint Connector for MCP (Model Context Protocol) and Anypoint Connector for Agent2Agent (A2A) communication.
16
64
17
-
Agent network::
18
-
A collection of agents, brokers, LLMs, and MCP servers that are connected to each other.
19
65
Broker::
20
66
An intelligent routing service that coordinates task delegation across specialized A2A-compliant agents in your enterprise.
21
67
A broker is defined by the agents and MCP servers it can leverage to accomplish tasks.
@@ -36,6 +82,11 @@ A service that implements the Model Context Protocol (MCP) to expose tools and d
36
82
MCP servers can be defined either locally in the agent network or externally in a different agent network or elsewhere in your company.
37
83
Your agent network can use both locally defined and externally defined MCP servers to complete tasks.
38
84
85
+
[[agent-networks-code-builder]]
86
+
=== Agent Networks in Anypoint Code Builder
87
+
88
+
When you create agent networks, the Anypoint Code Builder canvas shows the brokers, agent, and MCP servers you've configured.
89
+
39
90
image::af-agent-network-canvas.png["Anypoint Code Builder canvas showing brokers, agents, and MCP servers"]
40
91
41
92
[calloutlist]
@@ -60,6 +111,20 @@ These servers will be published to Exchange.
60
111
The asset might also be published to Exchange.
61
112
. An asset that has been added to this agent network project from Exchange.
62
113
114
+
[[agent-network-architecture]]
115
+
== Agent Network Architecture
116
+
117
+
This diagram shows an agent network with agents and MCP servers, traffic through Flex Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer.
118
+
119
+
image::agent-fabric-architecture.png[Agent Fabric showing agents and MCP servers defined in YAML and published to Exchange, with traffic through Flex Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer]
120
+
121
+
[calloutlist]
122
+
. Publish the agentic assets to Anypoint Exchange for discovery and reuse after you define the agent network (brokers, agents, MCP servers) in the agent network YAML in Anypoint Code Builder.
123
+
. Deploy the agentic assets to CloudHub 2.0 (managed in Runtime Manager).
124
+
. Enforce policies on incoming traffic to the network with an ingress Flex Gateway, which sits in front of broker and API endpoints.
125
+
. Enforce policies, manage connections, and emit telemetry data with an egress Flex Gateway, which sits on outbound paths from brokers and agents to external agents and services.
126
+
. Collect logs, metrics, and traces from Flex Gateway and runtimes in Anypoint Monitoring.
127
+
63
128
[[llm-support]]
64
129
== Large Language Models
65
130
@@ -82,7 +147,7 @@ Agent network brokers support the latest Gemini and OpenAI models.
82
147
** Gemini 3 Flash
83
148
** Gemini 3 Pro
84
149
85
-
For more information about these models, see the https://platform.openai.com/docs/models[OpenAI] and https://ai.google.dev/gemini-api/docs/models[Gemini] documentation.
150
+
For more information about these models, see the https://developers.openai.com/api/docs/models[OpenAI] and https://ai.google.dev/gemini-api/docs/models[Gemini] documentation.
86
151
87
152
The following table details the requirements and recommended models.
88
153
@@ -108,6 +173,7 @@ a|
108
173
109
174
Agent network supports text-based prompts and responses. Image and binary message types aren't supported.
110
175
176
+
[[a2a-protocol]]
111
177
== A2A Protocol
112
178
113
179
The Agent2Agent (A2A) Protocol governs agent-to-agent communication. This protocol powers orchestration, observability, and governance features in agent networks. MuleSoft supports v0.3.0 of the A2A Protocol Specification.
0 commit comments