---
schema_version: "1"
id: 8cfbc19e5a7417d37599c43146810502732df98e59742174c0afafb87a80a17e
title: Publish Agent Network Assets
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/agent-network/1.0/af-publish-agent-network-assets.md
canonical_url: https://docs.mulesoft.com/agent-network/1.0/af-publish-agent-network-assets
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b9dc5679fbd18ceb32a4a52c550f3fe7fc68db14ea268a4472c7f8db013d1fa5
description: MuleSoft Documentation Site
release: "1.0"
latest: false
---
---
product: Building Agent Networks
version: 1.0
---

# Publish Agent Network Assets

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Build and publish your agent network project as Anypoint Exchange assets. When you publish, an asset
is created for each broker, agent, and MCP server that’s in your agent network. The asset ID is the
value of the `name` key in `agent-network.yaml`.

For example, suppose you have an agent name of `badging-agent` in `agent-network.yaml`. After it’s
published, the Exchange `assetId` is `badging-agent`.

## Before You Begin

Make sure you review the [prerequisites](https://docs.mulesoft.com/agent-network/1.0/af-get-started#before-you-begin).

If you want to publish your project assets to a different business group, update the relevant
`groupId` in `exchange.json`.

> [!IMPORTANT] Agent networks use an automatic versioning system for Anypoint Exchange assets. If
> you make changes to your existing agent network project assets and re-publish them, Exchange
> triggers a major semantic version upgrade (for example, 1.x.x to 2.x.x).

## Publish Your Network Using MuleSoft Vibes

MuleSoft Vibes can help you publish your agent network specification to Anypoint Exchange. For more
information, see
[Creating API Specs with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-api-ai-create-spec).

1.  In the Anypoint Code Builder activity bar, click the agent icon
    ![](/mulesoft/current/en-us/agent-network/1.0/_images/af-acb-dev-agent-icon.png).

2.  Tell the agent that you want to publish your agent network. MuleSoft Vibes does the rest.

To get started, try one of these suggested messages.

- Publish my Employee Onboarding project.

- Publish my agent network project version 1.0.0.

- Publish the hello-world-network project to Exchange.

- Publish agent network project at /path/to/project with version 2.1.0.

## Publish Your Network Using Anypoint Code Builder

1.  If you’re not logged in already, log in to your Anypoint Platform account.

2.  In your Anypoint Code Builder project, choose one of the following:

3.  In Explorer, right-click a project file and select **Publish Agent Network Assets**.

4.  In the Command Palette, run this command: **MuleSoft: Publish Agent Network Assets**.

5.  In **Publish Agent Network Project Assets**, enter a version for the project and review the
    project metadata. If you want to publish project assets to a different business group, update
    the `groupId` in `exchange.json`.

6.  Select **Publish**.

7.  Your agents, MCP servers, and LLM provider definitions are published to Exchange. An Exchange
    asset is created for each element in your agent network.

Next, discover your agent network assets in **Agents & Tools** in Exchange to get a comprehensive
view of your integration, including agent and MCP server assets. Exchange automatically tags brokers
for easy identification.

## Publish a Network Using the Anypoint CLI

If you run operations within a CI/CD environment, you can use Anypoint CLI’s plugin to set up,
create, build, publish, and deploy agent networks. For more information, see
[Build Agent Networks in a CI/CD Environment](https://docs.mulesoft.com/agent-network/1.0/af-build-agent-networks-in-a-ci-cd-environment).

## See Also

- [Deploy Agent Network Instances](https://docs.mulesoft.com/agent-network/1.0/af-deploy-agent-network-targets)