Get Started with the Enhanced Experience
Grow and tune your AI portfolio by registering and monitoring agents, APIs, and gateways in centralized catalogs. Sign in through the entry point your organization provides, such as Anypoint Platform, or a direct URL, to access dashboards and governance strategies based on your assigned permissions. You can review live performance metrics, manage security policies, and track rule-level compliance through automated conformance reports.
These tools ensure your AI assets remain audit-ready while providing clear visibility into cost and runtime health across your organization.
Watch this video to see how to get started with the enhanced MuleSoft experience:
Access the Enhanced Experience
Your organization determines how you access the new experience. Common options include these environments.
-
Anypoint Platform
In Anypoint Platform, look for the new experience banner or shortcut and choose Go to the new experience. Your administrator can also add a direct link in the main navigation or workspace.
-
Coding assistants
If your organization connects the new experience to a supported assistant, such as Claude Code, follow your internal instructions to open the new experience features from that development environment.
-
Direct URL
Your organization can share a standalone URL that signs you in to the new experience outside other apps. Use the address your administrator or internal documentation provides.
-
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 new experience’s integrations with other platforms. |
Before You Begin
Before you rely on the new experience in production, complete these checks with your administrator. Requirements vary by entry point and how your administrator integrates the new experience with other systems.
- Access and Credentials
-
-
Confirm that you have a user account for your organization’s entry path, such as Anypoint Platform, and valid credentials to log in.
-
Confirm that you can reach the new experience and integrated services, such as Anypoint Platform, or a connected coding assistant, from the networks and locations you use.
-
- Platform and Product Access
-
-
Confirm that your organization has the required product access for the new experience and that an administrator enabled it for your Anypoint Platform business group or organization.
If the experience isn’t available, contact your Anypoint Platform organization administrator or MuleSoft account team.
-
Confirm that required integrations with Anypoint Platform or your development environment work end to end.
-
If the new experience connects to other services, work with your administrator to configure authentication, such as API keys or OAuth tokens, to ensure successful connections.
-
Confirm that your administrator approved and configured required external connections, such as cloud providers under Providers.
-
Enhanced Experience Permissions
The new experience 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. |
To apply open policies, or to apply, edit, enable, disable, or remove native policies on external gateways, you also need the Organization Administrator role. Without it, you can’t load an open policy catalog, open a policy configuration form, apply an open policy, or apply, edit, enable, disable, or remove native policies on an external gateway. Listing native policy templates on an external gateway still uses the View Policies permission. Viewing policies already applied on Omni or Mule gateways still uses the View Policies or Manage Policies permission.
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.