Agent Fabric Release Notes

You can now deploy your agent network locally and test each broker through an Agent-to-Agent (A2A) chat interface directly from Anypoint Code Builder. Use local deployments to iterate on your agent network without publishing or deploying it.

You can now configure OAuth 2.0 client credentials authentication for LLMs in agent networks. For more information, see Agent Network YAML Reference.

You can now reuse existing MCP assets from Exchange that use SSE transport.

Agent networks now support Agent Script dialect version 1.4.

You can now configure authentication for agent cards that use dual egress upstreams. For more information, see Agent Network YAML Reference.

This release fixes an issue in which deployments failed when an agent network reused an existing asset from Exchange.

You can now deploy agent networks to Anypoint Runtime Fabric (RTF) targets. Your RTF deployment must be on version 3.0.277 or later.

You can now deploy agent networks that do not include a registry.

Agent networks now support the Extended Agent Card from the Agent2Agent (A2A) Protocol specification, enabling richer agent metadata and discovery capabilities.

You can now connect the enhanced experience to AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault so API keys and other credentials stay in your secrets manager. MuleSoft stores only metadata, such as secret names and paths, not the secret values. It reads the secret from your vault when a model proxy or other service needs it.

You can now contain a rogue AI agent before it leaks data, takes unauthorized actions, or runs up costs. Stop that agent’s requests from reaching your models, then restore access if the containment was a false positive.

Cost Management now includes budget management. Set spending budgets for your model wallets, track spend against each budget, and manage budgets across providers and models from the Budgets tab.

The Cost Management Optimizations page now includes an Agents tab, so you can review token usage and optimization opportunities for your agents alongside model proxies and MCP servers.

You can now create, edit, delete, and list model wallets, which allocate token budgets that are granted only when a request’s claims match the wallet’s required claims. Manage model wallets from the UI or through the MuleSoft Agent.

You can now edit instances for model proxies, APIs, agents, and MCP servers from the service detail page or the instance detail page, without switching to Anypoint Platform.

Model Proxy now supports semantic caching, TLS security for provider connections, external vault–based provider authentication, and the Model Proxy Request Compression policy.

MCP Bridge now exposes tool output schemas as part of the MCP specification, so you can connect servers built with MCP Bridge to Agentforce.

These SaaS connectors are now available in the Trusted MCP catalog: Wix, WordPress.com, Hootsuite, Descript, Intercom, Front, and LiveChat.

You can now create an A2A bridge to make a non-A2A agent A2A-compliant so that Agent Fabric can discover, govern, and orchestrate it alongside native A2A agents.

You can now use OAuth 2.0 Authorization Code for Microsoft Copilot Studio scanners to create, authorize, and test the provider connection before you continue scanner setup.

You can now apply universal policies to your API instances and manage the resulting native policies. A universal policy is defined once and applied as the correct native policy on each supported gateway.

API scanners now write policies from these provider platforms: Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in Portfolio > APIs > Policies.

You can now track remediation and scan status in the Akamai Security Findings table on the Conformance tab.

Improved performance for agent network operations.

Fixed issues with LLM connectivity and Gemini 3 model integration.

Use MuleSoft Vibes, Anypoint Code Builder, or the Anypoint CLI to undeploy agent networks and unpublish Exchange assets associated with those networks.

Previously in agent network 2.0, connection and broker IDs were restricted to lowercase letters, numeric characters, and non-trailing underscores. You can now use standard naming conventions, such as upper case letters, dashes, and periods for these IDs.

To resolve common deployment errors, see Resolve Agent Network Deployment Errors in Anypoint Code Builder.

Define broker orchestration as a graph of nodes, edges, and triggers in Agent Script (.agent) files. Each node performs a discrete step — either an LLM-powered action like classification or a deterministic action like routing — giving you full visibility and control over execution order.

Use probabilistic nodes for complex, open-ended decisions that require nuanced judgment, such as ticket severity classification or intent recognition.

Use deterministic nodes to enforce fixed execution paths once a key decision has been made, ensuring reliable, rule-based behavior across operational flows.

View a graph-based visual canvas alongside Agent Script code.

Organize projects with a dedicated /brokers directory containing .agent files alongside your agent-network.yaml registry and context definitions.

Communicate across agents using version 1.0 of the Agent2Agent (A2A) Protocol specification.

Create and configure agent networks using natural-language prompts in MuleSoft Vibes, including broker graph design, node configuration, and Exchange asset integration.

Build, publish, and deploy agent networks in CI/CD environments using the Anypoint CLI plugin.

Exchange now supports GoDaddy ANS agents. You can now add a scanner to automatically discover and register GoDaddy ANS agents. GoDaddy ANS agents are verified by GoDaddy to be safe and secure. Govern and consume the agents in other applications.

Agent Visualizer now includes search and filtering capabilities and MCP server and tool insights.

This release includes agent network project updates.

In Anypoint Exchange, you can now add agent scanners to automatically discover and register AI agents across agent ecosystems on external platforms, which include Amazon Bedrock, Google Vertex AI, and Microsoft Azure Copilot. After the agents are registered, govern and consume them in other applications.

Anypoint Exchange now includes an option to publish MCPs via URLs instead of uploading a schema file.

You can now create and manage instances for publicly available MCP servers in API Manager.

This release includes agent network project updates and fixed issues.

This release includes agent network project updates and fixed issues.

This release includes updates to agent network projects.

Discover agents and MCP servers with Anypoint Exchange.

Orchestrate agents across ecosystems with agent brokers, a context-aware routing service for agents and assets. For more information, see Anypoint Code Builder Release Notes.

Secure Omni Gateway Instances with Policies.

Observe and visualize your agentic assets.

Learn About Agent Fabric

Known Issues