From be68a68d0de0affdd48e037f37fba5177a9dcf81 Mon Sep 17 00:00:00 2001 From: Hanna Nelson Date: Mon, 18 May 2026 18:06:19 -0700 Subject: [PATCH] Add access tier documentation for Enhanced Experience - Add new topic: Understanding Your Access to the Enhanced Experience Explains API Portfolio Access vs Agent + API Portfolio Access tiers - Add new topic: Get Started with API Portfolio Management Focused workflow for users with API-only access - Add new topic: Get Started with Agent Portfolio Management Comprehensive workflow for users with agent + API access - Update exp-overview.adoc to reference access tiers - Update exp-glossary.adoc to define access tier terms - Update exp-start-home.adoc to reference subscription tiers - Add prerequisites to exp-create-mcp-server.adoc for agent access - Add prerequisites to exp-add-semantic-services.adoc for agent access - Update nav.adoc to include new access tier topics All changes follow SKU-agnostic approach, focusing on user capabilities rather than product SKU numbers. --- modules/ROOT/nav.adoc | 3 + .../ROOT/pages/exp-add-semantic-services.adoc | 5 + modules/ROOT/pages/exp-create-mcp-server.adoc | 5 + .../exp-get-started-agent-portfolio.adoc | 288 ++++++++++++++++++ .../pages/exp-get-started-api-portfolio.adoc | 195 ++++++++++++ modules/ROOT/pages/exp-glossary.adoc | 10 + modules/ROOT/pages/exp-overview.adoc | 7 +- modules/ROOT/pages/exp-start-home.adoc | 4 + .../pages/exp-understand-access-tiers.adoc | 150 +++++++++ 9 files changed, 666 insertions(+), 1 deletion(-) create mode 100644 modules/ROOT/pages/exp-get-started-agent-portfolio.adoc create mode 100644 modules/ROOT/pages/exp-get-started-api-portfolio.adoc create mode 100644 modules/ROOT/pages/exp-understand-access-tiers.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index cedb261a..e5a6fb9d 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -6,7 +6,10 @@ *** xref:exp-glossary.adoc[Glossary] ** xref:exp-release-notes.adoc[Release Notes] ** xref:exp-start-home.adoc[] + *** xref:exp-understand-access-tiers.adoc[] *** xref:exp-view-portfolio-overview.adoc[] + *** xref:exp-get-started-api-portfolio.adoc[] + *** xref:exp-get-started-agent-portfolio.adoc[] ** xref:exp-add-services-to-portfolio.adoc[] *** xref:exp-connect-providers-to-add-services.adoc[] *** xref:exp-register-services-manually.adoc[] diff --git a/modules/ROOT/pages/exp-add-semantic-services.adoc b/modules/ROOT/pages/exp-add-semantic-services.adoc index f379ed93..3be3f252 100644 --- a/modules/ROOT/pages/exp-add-semantic-services.adoc +++ b/modules/ROOT/pages/exp-add-semantic-services.adoc @@ -1,5 +1,10 @@ = Adding Semantic Services +[NOTE] +==== +Semantic services require Agent + API Portfolio Access. If you don't see the Semantic Services option under LLM Proxies, contact your administrator to verify your subscription tier. See xref:exp-understand-access-tiers.adoc[] for more information. +==== + Semantic services improve how the system interprets and routes LLM-driven requests across your portfolio. They help teams apply context-aware behavior so the system directs requests to the most relevant tools, services, or pathways that your organization configured. Use this capability when your workflows need more than static routing. With semantic context in place, the system can support better request matching, more consistent response behavior, and stronger control as usage grows across agents, APIs, MCP servers, and related integrations. diff --git a/modules/ROOT/pages/exp-create-mcp-server.adoc b/modules/ROOT/pages/exp-create-mcp-server.adoc index 78b72fcd..b3849457 100644 --- a/modules/ROOT/pages/exp-create-mcp-server.adoc +++ b/modules/ROOT/pages/exp-create-mcp-server.adoc @@ -1,5 +1,10 @@ = Create an MCP Server +[NOTE] +==== +MCP server management requires Agent + API Portfolio Access. If you don't see the MCP Servers catalog, contact your administrator to verify your subscription tier. See xref:exp-understand-access-tiers.adoc[] for more information. +==== + Create MCP servers to define identity, runtime connectivity, and the tools and resources exposed to MCP clients. Creating an MCP server defines a new MCP implementation—for example, by transcoding an existing REST API or creating a runtime deployment—and establishes the server identity, runtime connectivity, and the MCP capabilities (tools and resources) exposed to clients. diff --git a/modules/ROOT/pages/exp-get-started-agent-portfolio.adoc b/modules/ROOT/pages/exp-get-started-agent-portfolio.adoc new file mode 100644 index 00000000..0fe4ee3e --- /dev/null +++ b/modules/ROOT/pages/exp-get-started-agent-portfolio.adoc @@ -0,0 +1,288 @@ += Get Started with Agent Portfolio Management + +[NOTE] +==== +Agent portfolio management requires Agent + API Portfolio Access. If you don't see the Agents, MCP Servers, or LLM Proxies catalogs, contact your administrator to verify your subscription tier. See xref:exp-understand-access-tiers.adoc[] for more information. +==== + +Use the enhanced experience to register, govern, monitor, and optimize your AI-powered services, including agents, MCP servers, and LLM proxies. The agent portfolio management features provide visibility and control over your AI service estate alongside traditional APIs. + +== Before You Begin + +Confirm these requirements with your administrator: + +Access:: +* You have Agent + API Portfolio Access. +* You can sign in to the enhanced experience through your organization's entry point. + +Permissions:: +* You have the necessary Access Management permissions to view and manage agents, MCP servers, and LLM proxies. +* See xref:exp-start-home.adoc#permissions[Enhanced Experience Permissions] for details. + +Integration:: +* Your organization has configured connections to Anypoint Platform. +* If using external AI providers, your administrator has configured the appropriate provider connections under *Platform* > *Providers*. + +== Agent Portfolio Workflow + +Follow these steps to start managing your agent portfolio: + +=== 1. Navigate to the Agent Catalogs + +. Sign in to the enhanced experience. +. In the main navigation, select *Portfolio*. +. Review the available catalogs: ++ +* *Agents*: AI-powered services that use the Agent-to-Agent (A2A) protocol +* *MCP Servers*: Services that expose tools and resources via the Model Context Protocol +* *LLM Proxies*: Gateway-backed proxies to large language models +* *APIs*: Traditional REST, GraphQL, and AsyncAPI services + +=== 2. Register Your Agent Services + +Add agents to the catalog using one of these methods: + +Manual Registration with A2A Endpoint:: +Use this method when your agent exposes an A2A endpoint: ++ +. On the Agents catalog page, select *Add Agent*. +. Enter the A2A endpoint URL. +. The system fetches the agent card automatically. +. Review the agent metadata and capabilities. +. Select *Save*. + +Manual Registration with Agent Card:: +Use this method when you have an agent card file: ++ +. On the Agents catalog page, select *Add Agent*. +. Choose to upload an agent card file. +. Complete the registration form with agent metadata. +. Select *Save*. + +Provider Discovery:: +Use scanners to automatically discover agents from connected AI platforms: ++ +. Configure a provider connection under *Platform* > *Providers*. +. Create a scanner for the provider. +. Run the scanner to discover agents automatically. +. Review and approve discovered agents. + +For detailed steps, see xref:exp-register-services-manually.adoc[] and xref:exp-connect-providers-to-add-services.adoc[]. + +=== 3. Register MCP Servers + +Add MCP servers to the catalog: + +Create from Existing API:: +. Navigate to an API detail page. +. Select *Actions* > *Create MCP Server*. +. Configure the MCP server endpoint and schema. +. Select *Create*. + +Manual Registration:: +. On the MCP Servers catalog page, select *Add MCP Server*. +. Enter the MCP URL or upload an MCP schema file. +. Complete the registration form. +. Select *Save*. + +For detailed steps, see xref:exp-create-mcp-server.adoc[]. + +=== 4. Register LLM Proxies + +Add LLM proxies to the catalog: + +. On the LLM Proxies catalog page, select *Add LLM Proxy*. +. Select the target LLM provider and model. +. Configure the proxy instance on a gateway. +. Set up authentication and rate limiting policies. +. Select *Create*. + +=== 5. View Service Details + +. From any catalog, select a service to open its detail page. +. Review the available tabs: ++ +* *Overview*: Basic metadata, description, status, and capabilities +* *Versions*: All registered versions (where applicable) +* *Instances*: Deployed instances on gateways +* *Policies*: Applied runtime policies +* *Conformance Report*: Governance compliance status +* *Monitoring*: Performance metrics, token usage, and health data + +For more information, see xref:exp-view-service-details.adoc[]. + +=== 6. Create Instances + +Deploy your agent services to gateways: + +. On the service detail page, select the *Instances* tab. +. Select *Add Instance*. +. Choose the gateway type: ++ +* *Managed instance*: Routes traffic through Anypoint Omni Gateway with full policy enforcement, authentication, and monitoring +* *Unmanaged instance*: Lighter deployment without Omni Gateway +. Configure the instance URL and target endpoint. +. Select *Create*. + +For detailed steps, see xref:exp-add-instances.adoc[]. + +=== 7. Apply Governance Policies + +Enforce runtime controls on your agent service instances: + +Instance-Level Policies:: +. On the service detail page, select the *Instances* tab. +. Select an instance. +. On the instance detail page, select the *Policies* tab. +. Select *Apply Policy*. +. Choose a policy template appropriate for agent services: ++ +* Authentication and authorization +* Rate limiting and throttling +* Tool mapping (control which tools an agent can invoke) +* Tool sanitization (filter or modify tool inputs/outputs) +* Cost controls +. Configure policy parameters. +. Select *Apply*. + +Organization-Wide Strategies:: +Create governance strategies that automatically apply policies to matching agent services: ++ +. Navigate to *Governance* > *Governance Strategies*. +. Create a new strategy with rules, scope, and automated policies. +. Select domains relevant to AI services (performance, cost, security, compliance). +. Activate the strategy. ++ +For detailed steps, see xref:exp-create-governance-strategies.adoc[]. + +=== 8. Monitor Agent Performance + +Track runtime health and usage: + +. On the service detail page, select the *Monitoring* tab. +. Review key metrics: ++ +* Request volume and throughput +* Response times and latency +* Token usage and consumption +* Error rates and failure modes +* Tool invocation patterns (for agents) +. Set up alerts for threshold violations under *Observability* > *Notifications*. + +For more information, see xref:exp-monitor-your-services.adoc[] and xref:exp-view-detailed-metrics-for-services.adoc[]. + +=== 9. Review Compliance + +Check governance conformance for agent services: + +. On the service detail page, select the *Conformance Report* tab. +. Review the compliance score and severity breakdown. +. Identify rule violations and warnings related to: ++ +* Agent card schema compliance +* Security and authentication requirements +* Tool exposure policies +* Cost and performance thresholds +. Address high-priority findings by updating agent configurations or applying policies. + +=== 10. Manage Costs + +Track token usage and optimize AI spending: + +. Navigate to *Governance* > *Cost Management*. +. Review token usage by service, instance, and time period. +. Identify cost optimization opportunities: ++ +* High-volume agents with potential for caching +* Inefficient tool usage patterns +* Opportunities for tool mapping to reduce unnecessary invocations +. Apply cost reduction policies: ++ +* Tool mapping to limit agent tool access +* Rate limiting to control request volume +* Caching policies to reduce redundant LLM calls + +For more information, see xref:exp-view-cost-and-token-usage.adoc[]. + +== Use Semantic Search + +Search across your agent portfolio using natural language: + +. Navigate to *Portfolio*. +. Use the search bar at the top of any catalog. +. Enter a natural language query describing what you're looking for. +. Review semantically matched results across agents, MCP servers, and APIs. + +Semantic search helps you find relevant services based on capabilities and descriptions, not just exact name matches. + +== Next Steps + +After establishing your agent portfolio: + +* Set up automated scanners for AI provider discovery +* Define agent-specific governance strategies +* Configure cost thresholds and alerts +* Integrate with Slack for agent notifications +* Connect the Platform MCP Server to Claude Desktop for agent development workflows +* Explore the Ask MuleSoft AI assistant for guided portfolio management + +== Common Tasks + +=== Update an Agent's Capabilities + +. Navigate to the agent detail page. +. Select *Actions* > *Update Agent Card*. +. Upload the updated agent card or point to the refreshed A2A endpoint. +. Review changes and save. + +=== Configure Tool Mapping for an Agent + +. Navigate to the agent instance detail page. +. Select the *Policies* tab. +. Select *Apply Policy* > *Tool Mapping*. +. Define which tools the agent is allowed to invoke. +. Save the policy configuration. + +=== Review Token Usage Trends + +. Navigate to *Governance* > *Cost Management*. +. Filter by agent or MCP server. +. Review the usage timeline chart. +. Export data for further analysis if needed. + +=== Create an MCP Server from an API + +. Navigate to an existing API detail page. +. Select *Actions* > *Create MCP Server*. +. Configure how API operations map to MCP tools. +. Save the MCP server configuration. +. The new MCP server appears in the MCP Servers catalog. + +For detailed steps, see xref:exp-create-mcp-server.adoc[]. + +== Troubleshooting + +*I can't see the Agents, MCP Servers, or LLM Proxies catalogs*:: +Verify that your subscription includes Agent + API Portfolio Access. Contact your administrator to confirm your subscription tier and Access Management permissions. See xref:exp-understand-access-tiers.adoc[]. + +*My agent registration fails*:: +Check that your A2A endpoint is accessible and returns a valid agent card. Review error messages for specific validation issues. Verify that your agent card conforms to the A2A protocol schema. + +*Token usage data is not appearing*:: +Confirm that your agent instance is deployed to a managed gateway and is receiving traffic. Token usage data may take a few minutes to appear after instance creation. Verify that the gateway is configured to report usage metrics. + +*Semantic search returns no results*:: +Semantic search requires indexed service descriptions. Newly registered services may take a few minutes to appear in semantic search results. Verify that your services have detailed descriptions in their metadata. + +*Tool mapping policies are not being enforced*:: +Verify that the agent instance is a managed instance on Anypoint Omni Gateway. Unmanaged instances do not support policy enforcement through the enhanced experience. Confirm that the tool mapping policy is applied and active. + +== See Also + +* xref:exp-understand-access-tiers.adoc[] +* xref:exp-overview.adoc[] +* xref:exp-register-services-manually.adoc[] +* xref:exp-create-mcp-server.adoc[] +* xref:exp-add-instances.adoc[] +* xref:exp-work-with-governance-strategies.adoc[] +* xref:exp-view-cost-and-token-usage.adoc[] diff --git a/modules/ROOT/pages/exp-get-started-api-portfolio.adoc b/modules/ROOT/pages/exp-get-started-api-portfolio.adoc new file mode 100644 index 00000000..bff61329 --- /dev/null +++ b/modules/ROOT/pages/exp-get-started-api-portfolio.adoc @@ -0,0 +1,195 @@ += Get Started with API Portfolio Management + +Use the enhanced experience to register, govern, monitor, and optimize your REST, GraphQL, and AsyncAPI services. The API portfolio management features help you maintain visibility and control over your API estate across multiple gateways and environments. + +== Before You Begin + +Confirm these requirements with your administrator: + +Access:: +* You have API Portfolio Access or Agent + API Portfolio Access. +* You can sign in to the enhanced experience through your organization's entry point. + +Permissions:: +* You have the necessary Access Management permissions to view and manage APIs. +* See xref:exp-start-home.adoc#permissions[Enhanced Experience Permissions] for details. + +Integration:: +* Your organization has configured connections to Anypoint Platform. +* If using external gateways (Apigee, Kong), your administrator has configured the appropriate provider connections. + +== API Portfolio Workflow + +Follow these steps to start managing your API portfolio: + +=== 1. Navigate to the APIs Catalog + +. Sign in to the enhanced experience. +. In the main navigation, select *Portfolio* > *APIs*. +. Review any existing APIs that were discovered or previously registered. + +=== 2. Register Your APIs + +Add APIs to the catalog using one of these methods: + +Manual Registration:: +Use this method when you have API specification files or endpoint details: ++ +. On the APIs catalog page, select *Add API*. +. Choose to upload a specification file (OAS, RAML, Proto, AsyncAPI) or enter API details manually. +. Complete the registration form with API metadata. +. Select *Save*. ++ +For detailed steps, see xref:exp-register-services-manually.adoc[]. + +Provider Discovery:: +Use this method to automatically discover APIs from connected cloud platforms: ++ +. Configure a provider connection under *Platform* > *Providers*. +. Create a scanner for the provider. +. Run the scanner to discover APIs automatically. +. Review and approve discovered APIs. ++ +For detailed steps, see xref:exp-connect-providers-to-add-services.adoc[] and xref:exp-add-scanners-from-providers.adoc[]. + +=== 3. View API Details + +. From the APIs catalog, select an API to open its detail page. +. Review the available tabs: ++ +* *Overview*: Basic metadata, description, and status +* *Versions*: All registered versions of the API +* *Instances*: Deployed instances on gateways +* *Policies*: Applied runtime policies +* *Conformance Report*: Governance compliance status +* *Monitoring*: Performance metrics and health data + +For more information, see xref:exp-view-service-details.adoc[]. + +=== 4. Create API Instances + +Deploy your API to a gateway by creating an instance: + +. On the API detail page, select the *Instances* tab. +. Select *Add Instance*. +. Choose the gateway type: ++ +* *Managed instance*: Routes traffic through Anypoint Omni Gateway with full policy enforcement and monitoring +* *Unmanaged instance*: Lighter deployment without Omni Gateway +. Configure the instance URL and target endpoint. +. Select *Create*. + +For detailed steps, see xref:exp-add-instances.adoc[]. + +=== 5. Apply Governance Policies + +Enforce runtime controls on your API instances: + +Instance-Level Policies:: +. On the API detail page, select the *Instances* tab. +. Select an instance. +. On the instance detail page, select the *Policies* tab. +. Select *Apply Policy*. +. Choose a policy template (rate limiting, authentication, security, etc.). +. Configure policy parameters. +. Select *Apply*. + +Organization-Wide Strategies:: +Create governance strategies that automatically apply policies to matching APIs: ++ +. Navigate to *Governance* > *Governance Strategies*. +. Create a new strategy with rules, scope, and automated policies. +. Activate the strategy. ++ +For detailed steps, see xref:exp-create-governance-strategies.adoc[]. + +=== 6. Monitor API Performance + +Track runtime health and usage: + +. On the API detail page, select the *Monitoring* tab. +. Review key metrics: ++ +* Request volume and throughput +* Response times and latency +* Error rates and status codes +* Availability and uptime +. Set up alerts for threshold violations under *Observability* > *Notifications*. + +For more information, see xref:exp-monitor-your-services.adoc[] and xref:exp-view-detailed-metrics-for-services.adoc[]. + +=== 7. Review Compliance + +Check governance conformance: + +. On the API detail page, select the *Conformance Report* tab. +. Review the compliance score and severity breakdown. +. Identify rule violations and warnings. +. Address high-priority findings by updating API specifications or configurations. + +=== 8. Manage Costs + +Track token usage and optimize spending (for APIs that integrate with LLM services): + +. Navigate to *Governance* > *Cost Management*. +. Review token usage by API and instance. +. Identify cost optimization opportunities. +. Apply tool mapping or rate limiting policies to reduce spend. + +For more information, see xref:exp-view-cost-and-token-usage.adoc[]. + +== Next Steps + +After establishing your API portfolio: + +* Set up automated scanners to keep your catalog current +* Define organization-wide governance strategies +* Configure observability dashboards for your team +* Integrate with Slack for notifications +* Connect the Platform MCP Server to Claude Desktop for development workflows + +== Common Tasks + +=== Update an API Version + +. Navigate to the API detail page. +. Select the *Versions* tab. +. Select *Add Version*. +. Upload the updated specification file. +. Review changes and save. + +=== Deactivate an API Instance + +. Navigate to the API detail page. +. Select the *Instances* tab. +. Select the instance to deactivate. +. Select *Actions* > *Deactivate*. +. Confirm the action. + +=== Review Gateway Connectivity + +. Navigate to *Portfolio* > *Gateways*. +. Review gateway status and health indicators. +. Investigate any connectivity issues or alerts. + +== Troubleshooting + +*I can't see the APIs catalog*:: +Verify that you have the required subscription tier and Access Management permissions. Contact your administrator if the catalog is not visible. + +*My API registration fails*:: +Check that your specification file is valid and in a supported format (OAS 2.0/3.0/3.1, RAML 0.8/1.0, Proto3, AsyncAPI 2.x/3.x). Review error messages for specific validation issues. + +*Monitoring data is not appearing*:: +Confirm that your API instance is deployed to a managed gateway and is receiving traffic. Monitoring data may take a few minutes to appear after instance creation. + +*Policies are not being enforced*:: +Verify that the instance is a managed instance on Anypoint Omni Gateway. Unmanaged instances do not support policy enforcement through the enhanced experience. + +== See Also + +* xref:exp-overview.adoc[] +* xref:exp-understand-access-tiers.adoc[] +* xref:exp-register-services-manually.adoc[] +* xref:exp-add-instances.adoc[] +* xref:exp-work-with-governance-strategies.adoc[] diff --git a/modules/ROOT/pages/exp-glossary.adoc b/modules/ROOT/pages/exp-glossary.adoc index 9f4dde2b..2d91d3bd 100644 --- a/modules/ROOT/pages/exp-glossary.adoc +++ b/modules/ROOT/pages/exp-glossary.adoc @@ -2,6 +2,16 @@ The enhanced MuleSoft experience uses a consistent set of terms across governance, portfolio, instance management, and agentic experiences. Clear definitions help you apply the right concepts when registering assets, configuring strategies, and managing instances. +== Access and Subscription Terms + +Agent + API Portfolio Access:: +A subscription tier that includes full access to all enhanced experience catalogs: Agents, APIs, MCP Servers, LLM Proxies, and Gateways. Provides agent-specific governance, monitoring, and cost management features in addition to all API portfolio capabilities. + +API Portfolio Access:: +A subscription tier that includes access to APIs and Gateways catalogs, along with API-focused governance, monitoring, and cost management features. Does not include access to Agents, MCP Servers, or LLM Proxies catalogs. + +== Entity and Service Terms + A2A endpoint:: An endpoint that exposes an agent's capabilities using the Agent-to-Agent (A2A) protocol. Point to an A2A endpoint during agent registration to fetch the agent card automatically. diff --git a/modules/ROOT/pages/exp-overview.adoc b/modules/ROOT/pages/exp-overview.adoc index 9dfe7e2e..1168b5cd 100644 --- a/modules/ROOT/pages/exp-overview.adoc +++ b/modules/ROOT/pages/exp-overview.adoc @@ -4,11 +4,16 @@ To grow and tune your AI portfolio, register and monitor agents, APIs, and gatew Your AI assets stay audit-ready with clear visibility into cost and runtime health across your org. +[NOTE] +==== +The catalogs and features available to you depend on your subscription tier. See xref:exp-understand-access-tiers.adoc[] to understand API Portfolio Access and Agent + API Portfolio Access. +==== + == Enhanced Experience Capabilities The enhanced MuleSoft experience supports the full lifecycle of AI-connected integration assets: -Entity Management:: Register and manage agents, REST and GraphQL APIs, MCP servers, LLMs, and gateways, including Anypoint Omni Gateway, external gateways, and unmanaged gateways. Each type has a dedicated catalog under *Portfolio*. +Entity Management:: Register and manage agents, REST and GraphQL APIs, MCP servers, LLMs, and gateways, including Anypoint Omni Gateway, external gateways, and unmanaged gateways. Each type has a dedicated catalog under *Portfolio*. The catalogs you can access depend on your subscription tier—API Portfolio Access provides APIs and Gateways catalogs, while Agent + API Portfolio Access adds Agents, MCP Servers, and LLM Proxies catalogs. 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. Conformance reporting summarizes rule violations and severity so you can close gaps systematically. diff --git a/modules/ROOT/pages/exp-start-home.adoc b/modules/ROOT/pages/exp-start-home.adoc index b36449c3..43a84921 100644 --- a/modules/ROOT/pages/exp-start-home.adoc +++ b/modules/ROOT/pages/exp-start-home.adoc @@ -37,6 +37,7 @@ 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, Slack, or a connected coding assistant, from the networks and locations you use. +* Verify your subscription tier (API Portfolio Access or Agent + API Portfolio Access) to understand which catalogs and features are available to you. See xref:exp-understand-access-tiers.adoc[] for details. Platform and Product Access:: + @@ -100,5 +101,8 @@ Feed findings from monitoring and governance back into planning for the next cha == See Also +* xref:exp-understand-access-tiers.adoc[] +* xref:exp-get-started-api-portfolio.adoc[] +* xref:exp-get-started-agent-portfolio.adoc[] * xref:exp-overview.adoc[] * xref:exp-compare.adoc[] diff --git a/modules/ROOT/pages/exp-understand-access-tiers.adoc b/modules/ROOT/pages/exp-understand-access-tiers.adoc new file mode 100644 index 00000000..0b8698d7 --- /dev/null +++ b/modules/ROOT/pages/exp-understand-access-tiers.adoc @@ -0,0 +1,150 @@ += Understanding Your Access to the Enhanced Experience + +Your MuleSoft subscription determines which portfolio catalogs and features you can access in the enhanced experience. Access levels range from API portfolio management to full agent and API portfolio management. + +== Access Tiers + +The enhanced experience provides different feature sets based on your subscription tier. + +API Portfolio Access:: +Includes access to the APIs catalog, gateway management, API-focused governance strategies, monitoring, cost management, and platform integration features. This tier focuses on managing and governing REST, GraphQL, and AsyncAPI services. + +Agent + API Portfolio Access:: +Includes everything in API Portfolio Access, plus the Agents catalog, MCP Servers catalog, LLM Proxies catalog, and agent-specific governance features. This tier provides full portfolio management for both traditional APIs and AI-powered services. + +[NOTE] +==== +Your organization's MuleSoft subscription determines which tier you have access to. If you need access to additional features, contact your Anypoint Platform organization administrator or your MuleSoft account team. +==== + +== Check Your Access Level + +To identify which features are available to you: + +. Sign in to the enhanced experience through your organization's entry point. +. Navigate to *Portfolio* in the main navigation. +. Review which catalogs appear in the Portfolio section: ++ +* If you see *APIs* and *Gateways*, you have API Portfolio Access. +* If you also see *Agents*, *MCP Servers*, and *LLM Proxies*, you have Agent + API Portfolio Access. + +The catalogs visible to you reflect your subscription tier and the permissions your administrator assigned. + +== Feature Availability by Tier + +The following table shows which features are available at each access tier: + +[%header,cols="3,1,1"] +|=== +|Feature |API Portfolio Access |Agent + API Portfolio Access + +|APIs catalog +|✓ +|✓ + +|Agents catalog +| +|✓ + +|MCP Servers catalog +| +|✓ + +|LLM Proxies catalog +| +|✓ + +|Gateways management +|✓ +|✓ + +|API governance strategies +|✓ +|✓ + +|Agent governance strategies +| +|✓ + +|API instances and monitoring +|✓ +|✓ + +|Agent instances and monitoring +| +|✓ + +|Cost management +|✓ +|✓ + +|Semantic search +| +|✓ + +|Ask MuleSoft (AI assistant) +|✓ +|✓ + +|Platform MCP Server +|✓ +|✓ + +|Slack integration +|✓ +|✓ + +|Claude Desktop integration +|✓ +|✓ + +|Provider discovery and scanners +|✓ +|✓ + +|Observability dashboards +|✓ +|✓ + +|Notifications and alerts +|✓ +|✓ +|=== + +== Permissions vs. Subscription Tiers + +Access to features requires both: + +Subscription Tier:: +Your organization's MuleSoft contract determines which catalogs and features are enabled. This is managed at the organization or business group level. + +Access Management Permissions:: +Your administrator assigns specific permissions that control what actions you can perform within the available features. Even if your organization has Agent + API Portfolio Access, you need the appropriate permissions to create, modify, or delete services. + +For information about permissions, see xref:exp-start-home.adoc#permissions[Enhanced Experience Permissions]. + +== Request Access + +If you need access to features that aren't currently available: + +. *For catalog access* (Agents, MCP Servers, LLMs): ++ +Contact your MuleSoft account team to discuss upgrading your subscription tier. + +. *For permissions* within available catalogs: ++ +Contact your Anypoint Platform organization administrator to request the appropriate role assignments. + +. *For technical issues* accessing the enhanced experience: ++ +Contact your internal IT support or Anypoint Platform administrator to verify: ++ +* Your user account has the correct entitlements +* The enhanced experience is enabled for your business group +* Required integrations are configured correctly + +== See Also + +* xref:exp-start-home.adoc[] +* xref:exp-overview.adoc[] +* xref:exp-compare.adoc[]