--- schema_version: "1" id: 5d46d2645f9f50e66f73ee85268571e041e2caedeff3de918be15bf71308ddd4 title: Publishing Agent Networks collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/agent-network/latest/af-publish-agent-network-assets.md canonical_url: https://docs.mulesoft.com/agent-network/latest/af-publish-agent-network-assets source_site: docs.mulesoft.com content_type: documentation content_hash: 04f7769e086dc9f8fe7b10497a7a78850c6b448a5910a82f8349b26f5e7d90ff description: MuleSoft Documentation Site release: "2.0" latest: true --- --- product: Building Agent Networks version: 2.0 is-latest-version: true --- # Publishing Agent Networks > 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, Exchange creates an asset for each broker, agent, and MCP server 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 named `badging-agent` in `agent-network.yaml`. After you publish, the Exchange `assetId` is `badging-agent`. > [!IMPORTANT] Asset names must be unique across all projects in your organization. If another > project already uses an asset name, the publish command fails. Use unique, descriptive names for > each asset in `agent-network.yaml`. For more information, see > [Troubleshoot Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-troubleshoot-agent-networks#asset-belongs-to-another-project-error-2006). ## Before You Begin Make sure you review the [prerequisites](https://docs.mulesoft.com/agent-network/latest/af-get-started#before-you-begin). To publish your project assets to a different business group, update the relevant `groupId` in `exchange.json`. ## Version Assets Don’t specify a semantic version (for example, `1.0.1`) each time you publish your project. Instead, enter a version group (for example, `V1` or `V2`) that represents the high-level version of your agent network project. Exchange handles the semantic versioning and automatically increments the version when there are changes. For existing projects, specify the same version group you were previously using. If you specify a different version group, then Exchange triggers a major semantic version upgrade (for example, `1.x.x` to `2.x.x`) for all associated assets. The `apiVersion` field in `exchange.json` is the version group shown when you publish an agent network to Exchange. The `apiVersion` field has these behaviors: - The version group name only changes when you explicitly rename `apiVersion`. Changing `apiVersion` automatically increments the major version (`x.0.0`). - The version group name doesn’t need to follow a `v#` pattern. You can can use any string. - Any other change unrelated to `apiVersion` automatically increments only the patch version. - You can’t manually increment the minor version. Exchange handles minor version increments. ## Publish Your Network Using MuleSoft Vibes Details Use MuleSoft Vibes to 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/latest/_images/af-acb-dev-agent-icon.png). 2. Tell MuleSoft Vibes 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 \[project-name\] project to Exchange. - Publish agent network project at /path/to/project with version 2.1.0. ## Publish Your Network Using Anypoint Code Builder Details Use Anypoint Code Builder to publish your agent network assets directly from your project to Anypoint Exchange. 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 group 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. Anypoint Code Builder publishes your agents, MCP servers, and LLM provider definitions to Exchange and creates an asset 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. ## Unpublish Your Network Using MuleSoft Vibes Details Use MuleSoft Vibes to unpublish your agent network assets from 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/latest/_images/af-acb-dev-agent-icon.png). 2. Tell MuleSoft Vibes to unpublish your agent network. MuleSoft Vibes does the rest. To get started, try one of these suggested messages. - Unpublish my Employee Onboarding project from Exchange. - Unpublish my agent network project. - Unpublish the \[project-name\] project from Exchange. ## Unpublish Your Network Using Anypoint Code Builder Details Unpublish your agent network assets from Anypoint Exchange directly from Anypoint Code Builder. When you unpublish, the asset versions are removed from Exchange. To prevent orphaned runtime references, undeploy your agent network before unpublishing. 1. If you’re not logged in already, log in to your Anypoint Platform account. 2. In Anypoint Code Builder, choose one of the following: 3. In the Explorer view, right-click a project file and select **Unpublish Agent Network**. 4. From the Command Palette, run this command: **MuleSoft: Unpublish Agent Network**. 5. In the confirmation dialog, select **Unpublish**. 6. Anypoint Code Builder removes the asset versions from Exchange. For details, check the Agent Fabric CLI output logs. ## Unpublish Behavior in Exchange When you unpublish an asset, Exchange performs a soft delete of the asset by default. Exchange waits 7 days before it permanently removes (hard deletes) the asset. If you republish an asset before the hard delete, Exchange uses the next available patch version (for example, `1.0.x`). ## Publish or Unpublish a Network Using the Anypoint CLI To set up, create, build, publish, unpublish, deploy, and undeploy agent networks in a CI/CD environment, use the Anypoint CLI plugin. For more information, see [Build Agent Networks in a CI/CD Environment](https://docs.mulesoft.com/agent-network/latest/af-build-agent-networks-in-a-ci-cd-environment). ## See Also - [Deploying Agent Network Instances](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets) [Defining Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-define-your-agent-network-specification) [Deploy and Test Agent Networks Locally (BETA)](https://docs.mulesoft.com/agent-network/latest/af-local-deploy-and-test)