Contact Us 1-800-596-4880
  1. Homepage
  2. Building Agent Networks (2.0)

  3. Get Started with Agent Networks

Get Started with Agent Networks

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 Component Required 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

CloudHub 2.0 permissions

See Permissions by Product in Anypoint Platform for a list of all Anypoint Platform permissions.

Additional Requirements

To complete these tasks, you also need:

MuleSoft Vibes Requirements (Optional)

If you plan to use MuleSoft Vibes to create agent network projects, make sure you meet the requirements.

CLI Requirements (Optional)

If you’re using the Anypoint CLI to create agent network projects, ensure you meet these requirements.

Task Overview

Step 1: Set Up Your Agent Network

  1. Use Anypoint Runtime Manager to set up a space in CloudHub 2.0.

    See Set Up the Target Space for Your Environment.

  2. Set up Omni Gateways for the space.

Step 2: Create a Project

Now you’re ready to create an agent network project. Choose one of these methods.

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.

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.

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 or a CloudHub 2.0 private space.

Set Up the Target Space for Your Environment

To deploy an agent network, you need a space on CloudHub 2.0. 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. We recommend naming the private space agent-network-space.

    2. Associate the new or existing private space with the business groups and environments 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.

Set Up Agent Network Gateways for the Target Space

After you set up a target space, use the MuleSoft: Set Up Agent Network Gateways command to create the gateways required for deployment in CloudHub 2.0.

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. You can also use separate gateways for ingress and egress traffic in a private space.

For more information about gateways, see Omni Gateway Deployment Models.

  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.

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