--- schema_version: "1" id: d142ee47cc1f195c5f52498494a450855a2437f0631728c5ab6bd8a8b8260061 title: Enhanced MuleSoft Experience Overview collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/general/exp-overview.md canonical_url: https://docs.mulesoft.com/general/exp-overview source_site: docs.mulesoft.com content_type: documentation content_hash: 0a01580c9264446a77ecb877c71d277cb889a38c92c651a603e113e111831bea description: MuleSoft Documentation Site latest: true --- --- product: Getting Started keywords: enhanced mulesoft experience, enhanced experience, capabilities, workflow, mulesoft overview, experience features --- # Enhanced MuleSoft Experience Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To grow and tune your AI portfolio, register and monitor 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. Review live performance metrics, manage security policies, and track rule-level compliance through automated conformance reports. Your AI services stay audit-ready with clear visibility into cost and runtime health across your org. ## Enhanced Experience Capabilities The enhanced MuleSoft experience supports the full lifecycle of AI-connected integration services: Entity Management Register and manage agents, REST and GraphQL APIs, MCP servers, Model proxies, and gateways, including Anypoint Omni Gateway, external gateways, and unmanaged gateways. Each type has a dedicated catalog under **Portfolio**. Governance and Compliance Define and apply policies across domains such as access and security, performance and cost, data privacy and integrity, and compliance and observability. For connected third-party API gateways (Azure API Management, Google Apigee, and Kong Gateway), apply, enable, disable, and remove policies directly from Anypoint through policy write, with no Omni Gateway in the request path. Conformance reporting summarizes rule violations and severity so you can close gaps systematically. Cost and Performance Optimization Monitor token usage, per-instance signals, and daily cost where the product exposes them. Apply governance strategies and related controls, such as tool mapping and tool sanitization, to reduce spend and risk where the experience supports them. Instance Management Create and review instances for supported asset types. Choose managed paths through Omni Gateway when you need deeper monitoring and policy enforcement, or choose lighter models when that matches your operating model. Credential and Secrets Management Connect an external vault (AWS Secrets Manager, Microsoft Azure Key Vault, or HashiCorp Vault) under **Platform** > **Providers** so credentials stay in your existing secrets manager. MuleSoft stores only secret metadata and resolves values from the vault when needed, and a model proxy can reference a vault secret instead of storing a key. See [Using Credentials Stored in External Vaults](https://docs.mulesoft.com/general/exp-vaults-manage). MuleSoft Agent (AI assistant) Get help navigating, searching, and managing your portfolio through natural language conversations. The AI assistant provides context-aware guidance, performs actions with your confirmation, and suggests next steps based on your current task. Available from every page in the enhanced experience. ## Enhanced Experience High-Level Workflow To manage and tune your AI portfolio, register services, apply security policies, and monitor runtime health, access centralized catalogs to track agents and gateways while verifying compliance through conformance reports and cost management tools. These integrated features help you optimize performance and maintain audit readiness across your environment. 1. Complete onboarding and access the enhanced experience. Confirm your credentials and the permissions that your administrator assigned, as described in [Enhanced Experience Permissions](https://docs.mulesoft.com/general/exp-home-start#permissions). Finish integration setup for supporting systems, such as connected providers under **Platform** > **Providers**, before you rely on the experience in production. For onboarding details, see [Get Started with the Enhanced Experience](https://docs.mulesoft.com/general/exp-home-start). 2. Learn the layout of the enhanced experience. Sign in through your entry path and land on **Home**. Scan **Portfolio** catalogs, **Governance**, **Observability**, and **Platform** so that you know where to register services, apply policies, read health signals, and manage providers. For more information about portfolio views, see [View Your Portfolio Overview](https://docs.mulesoft.com/general/exp-portfolio-overview). For AI assistant usage, see [Using the MuleSoft Agent](https://docs.mulesoft.com/general/exp-ai-assistant-use). 3. Register services in **Portfolio**. Under **Portfolio**, open **Agents**, **MCP Servers**, **Model Proxies**, **APIs**, or **Gateways**. Add services to work with. Register them manually or use connected providers under **Platform** > **Providers** if your organization enables discovery flows. For registration methods, see [Adding Services to Your Portfolio](https://docs.mulesoft.com/general/exp-services-add-to-portfolio). 4. Create and manage instances. In **Portfolio**, open a service detail page from **Agents**, **MCP Servers**, **Model Proxies**, or **APIs**, then open the **Instances** tab to create managed or unmanaged deployments that match your needs. Managed instances on Omni Gateway give stronger governance and monitoring when the new experience exposes them. **Gateways** don’t include an **Instances** tab on their detail page. For instance workflows, see [Creating and Managing Instances of Services](https://docs.mulesoft.com/general/exp-instances-add). 5. Configure policies. On a service detail page in **Portfolio**, open the **Policies** tab for the service or one of its instances to apply governance policies that match access control, data privacy, performance, and compliance goals. For APIs discovered from third-party gateways, applying policies requires a scanner connection whose credentials carry the provider’s write scope; see [Policy Write Prerequisites](https://docs.mulesoft.com/general/exp-scanners-prerequisites-reference#_policy_write_prerequisites). Use top-level **Governance** for gateway-wide policy work, organization strategies, and cost tools. For governance policy workflows, see [Working with Governance Strategies](https://docs.mulesoft.com/general/exp-governance-work-with-strategies). 6. Review compliance. In **Portfolio**, open a service detail page from **Agents**, **APIs**, or **MCP Servers**, then open the **Conformance Report** tab to review scores, violations, and warnings and address the findings your governance team prioritizes. For gateways, use top-level **Governance** for the same compliance story at the scope the experience supports. For service-level tabs and conformance context, see [Viewing Service Details in the Portfolio](https://docs.mulesoft.com/general/exp-services-view-details). 7. Monitor runtime health. On a service detail page in **Portfolio** (**Agents**, **APIs**, **MCP Servers**, or **Model Proxies**), open the **Monitoring** tab to review live metrics such as latency, error rates, and request volume when the new experience surfaces Omni Gateway data for managed paths. Compare those service-level metrics with dashboards, reports, or notifications under top-level **Observability** when your administrator enabled those views for your team. For monitoring workflows, see [Monitoring Services in Your Portfolio](https://docs.mulesoft.com/general/exp-services-monitoring). 8. Manage costs. Under **Governance**, open **Cost Management** to study token usage and related spend signals. Apply the cost reduction strategies your organization adopted, such as tool mapping or tool sanitization, where the new experience supports them. For cost and token usage details, see [Managing Costs and Token Usage](https://docs.mulesoft.com/general/exp-governance-view-cost-and-token-usage). 9. Operate and tune the portfolio. Coordinate agents, APIs, gateways, MCP servers, and Model proxies so traffic, policies, and integrations stay aligned. Open **Versions** when you need configuration history before you change instances or policies. Adjust policies, instances, or registrations when monitoring and governance insights show drift or new risk. For service detail workflows, see [Viewing Service Details in the Portfolio](https://docs.mulesoft.com/general/exp-services-view-details). 10. Improve on each cycle. Feed findings from monitoring and governance back into planning for the next change window. For strategy refinement workflows, see [Working with Governance Strategies](https://docs.mulesoft.com/general/exp-governance-work-with-strategies). ## See Also - [Get Started with the Enhanced Experience](https://docs.mulesoft.com/general/exp-home-start) - [Enhanced MuleSoft Experience and Anypoint Platform Comparison](https://docs.mulesoft.com/general/exp-compare) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/general/learning-map-exp)