Getting started Community Training Tutorials Documentation APIs, AI & Tools
Any of these permissions:
-
Exchange: Exchange Viewer
-
Exchange: Exchange Contributor
-
Exchange: Exchange Administrator
Sign in to Agent Fabric, confirm you have the permissions your work requires, and learn where to find catalogs, policies, monitoring, and cost tools. Then choose your first job, such as registering assets, exposing an API as an MCP server, or applying a policy to live traffic.
Complete these checks with your administrator before you rely on Agent Fabric in production. Requirements vary by entry point and by which jobs you do.
Confirm that you have an Anypoint Platform user account and valid credentials for your organization’s entry path.
Confirm that you can reach Agent Fabric and integrated services, such as Anypoint Platform or a connected coding assistant, from the networks and locations you use.
Confirm these platform settings with your administrator:
Confirm that your organization has the required product access for Agent Fabric and that an administrator turned it on for your Anypoint Platform business group or organization. If Agent Fabric isn’t available, contact your Anypoint Platform organization administrator or MuleSoft account team.
Confirm that generative AI is turned on for your organization when you use AI-assisted features. See Enabling or Disabling Generative AI for Anypoint Platform.
Confirm that any connected Salesforce orgs are linked. See Connecting a Trusted Salesforce Organization to Anypoint Platform.
Confirm that required integrations with Anypoint Platform or your development environment work end to end.
If Agent Fabric connects to other services, work with your administrator to configure authentication, such as API keys or OAuth tokens.
Confirm that your administrator approved and configured required external connections, such as cloud providers under Platform > Providers.
Confirm that your administrator assigned the permissions for the jobs you do. See Agent Fabric Permissions.
|
These apply to more than one job:
|
Your organization determines how you reach Agent Fabric. Common entry points include these environments.
Anypoint Platform
Look for the enhanced experience banner or shortcut and choose Go to the new experience. Your administrator can also add a direct link in the main navigation.
Direct URL
Your organization can share a standalone URL, such as omni.mulesoft.com, that signs you in outside other apps. Use the address your administrator or internal documentation provides.
Coding assistants
If your organization connects Agent Fabric to a supported assistant, such as Claude Code, follow your internal instructions to open Agent Fabric features from that development environment.
Custom integrations
Your organization can build access through another tool. Follow the internal access instructions for custom integrations.
| Available access points depend on how your administrators configured the experience’s integrations with other platforms. |
Agent Fabric uses Anypoint Platform access management. Your administrator maps jobs to roles and permissions in Access Management. Exact permission names differ by organization. Use this table with your internal access guide.
| Required Permissions | Grants the Ability to | Notes |
|---|---|---|
Any of these permissions:
|
View services |
View services in the portfolio and open the catalog overview in Anypoint Exchange. |
One of these Exchange permissions:
|
Create services |
Register MCP servers, agents, LLMs, or APIs. To create an MCP server, you also need the API Manager: Manage APIs Configuration permission on at least one environment. To create an A2A bridge, you also need the API Manager: Manage APIs Configuration permission on the target environment. |
API Manager: API Creator |
Create instances |
Create or add instances. |
API Manager: API Creator |
Create model proxies |
Create model proxies on Omni Gateway. |
One of these Exchange permissions:
|
Configure semantic routing and semantic caching |
Configure the semantic routing service and the semantic caching service for model proxies. |
Any of these permissions:
|
Set model costs |
Set input and output token costs for each model so that cost reports show spend in dollars. |
These permissions:
|
Manage model wallets |
Create and edit model wallets and their budgets. The Manage Policies permission is required to apply, disable, reorder, and edit policies. |
API Manager: View APIs Configuration |
View instances |
View instances for services and open the Instances tab. |
API Manager: Manage APIs Configuration |
Edit instances |
Edit instances for services. |
Exchange: Exchange Administrator |
Create scanners |
Create scanners from Providers using Add MCP Server, Add Agent, or Add API if your organization enables matching scanner capabilities. To view the Providers section, you need these permissions or the required scanner entitlements for API, MCP, or agent scanners. |
Exchange: Exchange Administrator |
Set up Akamai risk correlation |
Create the Akamai API Security scanner in the target business group to correlate Akamai findings to services already in the portfolio. You also need access to apply the Akamai correlation policy in the environments you scan. |
Any of these permissions:
|
View vaults |
List and view external vaults under Platform > Providers, including sync activity and health checks. |
These permissions:
|
Manage vaults |
Register, edit, delete, test, and sync external vaults under Platform > Providers. |
Any of these permissions:
|
View monitoring |
Open the Monitoring tab at the service and instance levels, and view Monitoring in the navigation bar. |
API Manager: View Policies |
View policies |
View and apply policies on instances, and access policies from the Governance tab. |
API Manager: Manage Policies |
Apply policies |
Edit policy configurations and add policies. To apply, enable, disable, or remove policies on a third-party gateway, such as Azure API Management, Google Apigee, or Kong Gateway, the provider’s scanner connection credentials also need the provider’s write scope. |
These permissions:
|
Detect and contain rogue agents |
Apply the Rogue Agent Detection and Agent Kill Switch policies to model proxies, and review and quarantine flagged agents. |
These permissions:
|
Use the Cost Management experience |
Apply optimization strategies using policies, view policies, view Exchange assets, and query metrics. The Mule Developer Generative AI User permission is required to enable AI features. |
Anypoint Code Builder: Mule Developer Generative AI User |
Use AI features in Anypoint Code Builder |
Use AI-powered features in Anypoint Code Builder, including MuleSoft Vibes and Diagnostics Agent. |
Any of these permissions:
|
Create governance strategies |
Create governance strategies. To view and create governance strategies, you need the Governance Administrator permission for Control types, or the Manage Policies permission for Automated Policy types. |
Any of these permissions:
|
View governance reports |
View governance reports at the service and governance strategy levels. To see the conformance badge and whether rulesets passed or failed, you need the Exchange Viewer permission. To view or export detailed governance reports, including violations, warnings, and rule breakdowns, you need the Governance Viewer permission. |
Any of these permissions:
|
View alerts |
View API alerts in API Manager and read alerts in Runtime Manager. |
Any of these permissions:
|
Manage alerts |
Manage API alerts in API Manager and alerts in Runtime Manager. |
These permissions:
|
Use Agent Visualizer |
View monitoring data for agentic assets (Monitoring Viewer), view agentic assets (Exchange Viewer), view API nodes and relationships (View APIs Configuration), and view policies for assets (View Policies). |
These permissions:
|
Create and deploy agent networks |
Define brokers and agent networks in Anypoint Code Builder, publish agent network assets to Exchange, deploy them, and view usage. The Anypoint Code Builder Developer permission applies only to the cloud IDE. To deploy to CloudHub 2.0 or Runtime Fabric, you also need the CloudHub 2.0 permissions or the Runtime Fabric permissions. |
MuleSoft Agent AI User |
Use MuleSoft Agent functionality |
Access MuleSoft Agent functionality in the enhanced experience. |
If you can’t complete an action or a page shows an authorization error, ask your Anypoint Platform organization administrator for the matching permission or role.
After you sign in, you land on Home. The main navigation has four areas:
| Area | Use it to |
|---|---|
Portfolio |
Find and register services. Portfolio is the registry. Each asset type has its own catalog: Agents, MCP Servers, Model Proxies, APIs, and Gateways. See View Your Portfolio. |
Governance |
Work with organization governance strategies, gateway-wide policies, and Cost Management. |
Observability |
View organization-wide dashboards, reports, and notifications, if your administrator turned on those views for your team. |
Platform |
Manage connected providers for scanners and external vaults under Platform > Providers. |
The MuleSoft Agent is available on every page. Ask it to help you navigate, search, and manage your registry in natural language. It suggests next steps based on your current task and performs actions only after you confirm them. See Use the MuleSoft Agent.
Most day-to-day work on a registered service happens on its detail page. In Portfolio, open a service. The tabs you see depend on the catalog. See View Service Details in the Portfolio.
Instances
Create managed instances on Omni Gateway for stronger governance and monitoring, or unmanaged instances when you don’t need Omni Gateway in the request path. Available for agents, MCP servers, model proxies, and APIs. Gateways and Model Proxiesdon’t include an Instances tab.
Policies
Apply policies to the service or to one of its instances.
Conformance Report
Review scores, violations, and warnings. Available for agents, APIs, and MCP servers. For gateways, use Governance.
Monitoring
Review live metrics such as latency, error rates, and request volume for managed instances on Omni Gateway. Available for agents, APIs, MCP servers, and model proxies.
Versions
Review configuration history before you change instances or policies.
You can’t govern, secure, or control the cost of agents you don’t know about, so start by adding your agents, MCP servers, and APIs to the registry. After that, the jobs are independent. Choose the one that matches your next goal, in any order.
Catalog agents, MCP servers, and APIs so teams can find and reuse them: Add Services to Your Portfolio, Register Services Manually, and Enable Automated Service Discovery
Expose existing APIs as MCP servers so agents can call them as tools: Create MCP Servers with MCP Bridge
Present non-A2A agents as A2A-compliant so Agent Fabric can orchestrate them: Make an Agent A2A-Compliant
Coordinate work across specialized agents when one agent isn’t enough: Get Started with Agent Networks
Enforce the same policies on live traffic through Omni Gateway: Create and Manage Instances of Services, Apply and Manage Policies, and Work with Governance Strategies
See LLM spend, cap it, and reduce token use: Create Model Proxies, Set Model Costs for Spend Tracking, Cap Spend for Callers of Model Proxies, and Manage Costs and Token Usage
Detect and contain rogue agents: Detect and Contain Rogue Agents
Keep credentials in an external vault: Use Credentials Stored in External Vaults
Correlate Akamai risk to services you already discovered: Correlate Risk Using Akamai API Security
Monitor latency, errors, and volume: Monitor Services in Your Portfolio and Configure Notifications for Alerts