--- schema_version: "1" id: 8f75f0401df6240ae1d69eb30f77e616e5d0743278710a2ac2af5d4fe55c441a title: Getting Started with Agent Networks collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/agent-network/latest/af-get-started.md canonical_url: https://docs.mulesoft.com/agent-network/latest/af-get-started source_site: docs.mulesoft.com content_type: documentation content_hash: 9f9b84405db0260ebf4de7b1cbb805ac602078d63b32c7fb29d00019d957af86 description: MuleSoft Documentation Site release: "2.0" latest: true --- --- product: Building Agent Networks version: 2.0 is-latest-version: true --- # Getting Started with Agent Networks > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Creating agent networks is a multi-step process. Review these prerequisites and task overviews to make sure you can create agent networks efficiently. ## Before You Begin Before you get started, review these prerequisites. ### Anypoint Platform Requirements and Permissions
Anypoint Platform ComponentRequired Permissions

Runtime Manager

  • Manage Servers

  • Create Applications

  • Read Servers

Anypoint Code Builder

  • Anypoint Code Builder

  • Mule Developer Generative AI User

Anypoint Design Center

Design Center Developer

API Manager

  • Deploy API Proxies

  • Manage Policies

Exchange

Exchange Contributor

Usage

Usage Viewer

CloudHub 2.0 or Runtime Fabric

Runtime Fabric permissions or CloudHub 2.0 permissions

See [Permissions by Product in Anypoint Platform](https://docs.mulesoft.com/access-management/permissions-by-product) for a list of all Anypoint Platform permissions. ### Additional Requirements To complete these tasks, you also need: - Your Anypoint Platform credentials - [Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-acb) Allowlist Anypoint Code Builder URLs. For more information, see [Allow URLs and Antivirus Exclusions for Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/urls-to-allow). - [Omni Gateway Ingress and Egress gateways](https://docs.mulesoft.com/gateway/latest/gateway-managed-ingress-egress) ### MuleSoft Vibes Requirements (Optional) If you plan to use MuleSoft Vibes to create agent network projects, make sure you meet [the requirements](https://docs.mulesoft.com/anypoint-code-builder/mulesoft-vibes#before-you-begin-vibes). ### CLI Requirements (Optional) If you’re using the Anypoint CLI to create agent network projects, ensure you meet these requirements. - Node 20 (v20.19.4) or later. See [Nodejs.org](https://nodejs.org/en). - Java 17 or later. Set the `JAVA_HOME` environment variable. - [Anypoint CLI Agent Fabric Plugin](https://www.npmjs.com/package/mulesoft-anypoint-cli-agent-fabric-plugin) ## Task Overview ### Step 1: Set Up Your Agent Network 1. Use Anypoint Runtime Manager to set up a space in CloudHub 2.0 or deployment target in Runtime Fabric. See [Set Up the Space or Deployment Target for Your Environment](#setup-space). 2. Set up Omni Gateways for the space or deployment target. - If using Anypoint Code Builder, see [Set Up Agent Network Gateways for the Space or Deployment Target](#setup-gateways). - If using the Anypoint CLI, see the [setup gateways command reference](https://docs.mulesoft.com/agent-network/latest/af-build-agent-networks-in-a-ci-cd-environment#agent-network-setup-gateways). ### Step 2: Create a Project Now you’re ready to create an agent network project. Choose one of these methods. - [Create a Network Using MuleSoft Vibes](https://docs.mulesoft.com/agent-network/latest/af-create-agent-network#create-dev-agent) - [Create a Network Using Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-create-agent-network#create-acb) - [Create a Network Using the Anypoint CLI](https://docs.mulesoft.com/agent-network/latest/af-create-agent-network#create-cli) ### Step 3: Define Your Agent Network Specification After you create your agent network project, configure `agent-network.yaml` and `exchange.json` to reflect the structure of your network. - [Define a Network Using MuleSoft Vibes](https://docs.mulesoft.com/agent-network/latest/af-define-your-agent-network-specification#define-dev-agent) - [Define Your Network in Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-define-your-agent-network-specification#define-acb-ide) ### Step 4: Publish Your Agent Network Assets Build and publish your agent network project as Anypoint Exchange assets. When you publish the agent network, an asset is created in Exchange for each broker, agent, and MCP server that’s in your agent network. - [Publish Your Network Using MuleSoft Vibes](https://docs.mulesoft.com/agent-network/latest/af-publish-agent-network-assets#publish-dev-agent) - [Publish Your Network Using Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-publish-agent-network-assets#publish-acb) - [Publish Your Network Using the Anypoint CLI](https://docs.mulesoft.com/agent-network/latest/af-build-agent-networks-in-a-ci-cd-environment#agent-network-project-publish) ### Step 5: Deploy Your Agent Network Instances Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 shared space, a CloudHub 2.0 private space, or to a Runtime Fabric target. - [Deploy Your Network Using MuleSoft Vibes](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets#deploy-dev-agent) - [Deploy Your Network Using Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets#deploy-acb) - [Deploy Your Network Using the Anypoint CLI](https://docs.mulesoft.com/agent-network/latest/af-build-agent-networks-in-a-ci-cd-environment#agent-network-project-deploy) ## Set Up the Space or Deployment Target for Your Environment To deploy an agent network, you need a space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric. CloudHub 2.0 supports shared spaces and private spaces. Use a shared space if you don’t require dedicated infrastructure. Use a private space if you need workload isolation or have other requirements that a shared space doesn’t satisfy. Depending on your deployment target: - CloudHub 2.0 shared space: No setup is required. Every Anypoint Platform organization includes a shared space that’s available to all business groups and environments. - CloudHub 2.0 private space: 1. Create a private space in CloudHub 2.0 or verify that you can access an existing private space. To create a private space, see [Creating Private Spaces](https://docs.mulesoft.com/cloudhub-2/ps-create-configure). We recommend naming the private space `agent-network-space`. 2. [Associate the new or existing private space with the business groups and environments](https://docs.mulesoft.com/cloudhub-2/ps-config-env) where you plan to deploy your agent network. You must complete this step so that the private space appears as a valid deployment target in Anypoint Code Builder and Anypoint CLI. - Runtime Fabric: Create a deployment target for Runtime Fabric. For information about Runtime Fabric deployments, see [Managed Omni Gateway on Runtime Fabric](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up#rtf). Agent networks on Runtime Fabric use Object Store in one of two modes: - **Non-persistent** (default): No additional setup required. - **Persistent**: Requires a persistence gateway. For setup instructions, see [Persistence Gateway](https://docs.mulesoft.com/runtime-fabric/latest/persistence-gateway). ## Set Up Agent Network Gateways for the Space or Deployment Target After you set up a target space, use the `MuleSoft: Set Up Agent Network Gateways` command to create the gateways required for deployment in either CloudHub 2.0 or Runtime Fabric. For agent networks, you need at least one Managed Omni Gateway in your environment. A single gateway can handle both ingress and egress traffic, which is the recommended configuration. A single gateway simplifies operations by providing unified policy enforcement, centralized observability, and one deployment to manage and scale. This configuration also reduces the cost of using multiple gateways. If needed, you can use separate gateways for ingress and egress traffic in a private space. For more information about gateways, see [Omni Gateway Deployment Models](https://docs.mulesoft.com/gateway/latest/gateway-architecture-basic-deployments). For more information about Runtime Fabric deployments, see [Managed Omni Gateway on Runtime Fabric](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up#rtf). > [!IMPORTANT] For Runtime Fabric deployments, you must register an external ingress domain on your > Managed Omni Gateway in Runtime Manager before you deploy an agent network. Running a gateway > without inbound transport is a valid configuration, but agent network broker deployment requires > an inbound ingress endpoint. > > To add an ingress endpoint, see the instructions for > [deploying a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up#deploy-a-managed-omni-gateway). 1. In Anypoint Code Builder, from the Command Palette, run the command **MuleSoft: Set Up Agent Network Gateways**. 2. If you’re not logged in, log in to your Anypoint Platform account. 3. Select the business group and environment. 4. Select the deployment target: - **Shared Space**: The command creates one gateway named `agent-network-shared-gw` that handles both ingress and egress traffic. - **Private Space**: Select the target space, then choose a gateway configuration: - **Single Gateway** (recommended): The command creates one gateway named `agent-network-gw` that handles both ingress and egress traffic. - **Separate Ingress & Egress**: The command creates two gateways: - `agent-network-ingress-gw` (with public and internal endpoint) - `agent-network-egress-gw` (with internal endpoint only) If you didn’t associate the private space with the business group and environment, you see an error. If a gateway with the expected name already exists in the selected space, the command doesn’t recreate it. > [!IMPORTANT] After you deploy an agent network, you cannot redeploy it to a different target or > gateway (for example, switching between a shared space and a private space, or changing to a > different gateway). Attempting to do so fails with a Runtime Manager error. To deploy to a > different target or gateway, first manually delete the existing Runtime Manager application, then > redeploy. ## See Also - [Creating Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-create-agent-network) [Agent Network Use Cases](https://docs.mulesoft.com/agent-network/latest/af-use-case-orchestration) [Creating Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-create-agent-network)