From eb61eb6c63cd676be085ac2a26c9897e4cb61acb Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Fri, 24 Jul 2026 18:11:49 +0530 Subject: [PATCH 01/15] W-23568435-mule-credits-granular-usage --- modules/ROOT/nav.adoc | 6 +++--- .../pages/mule-credits-usage-and-rates.adoc | 15 ++++++++++++++- modules/ROOT/pages/usage-metrics.adoc | 18 ++++++++++++++++-- modules/ROOT/pages/usage-reports.adoc | 11 +++++++++++ 4 files changed, 44 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 96f9abae4..a07ab9bfc 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -45,15 +45,15 @@ ** xref:api-led-operate.adoc[Step 6. Monitor and Manage] * xref:usage-reports.adoc[Usage Reports] ** xref:usage-reports-release-notes.adoc[Release Notes] - ** xref:usage-metrics.adoc[Usage and Pricing Metrics Reference] - ** xref:ai-features-and-data-usage.adoc[] - ** xref:pricing.adoc[Pricing] + ** xref:usage-metrics.adoc[Usage-Based Pricing: Usage and Rates] ** xref:mule-credits-usage-and-rates.adoc[] ** xref:automation-credits-usage-and-rates.adoc[] *** xref:mulesoft-automation-credits-3-0.adoc[] *** xref:mulesoft-automation-credits-2-0.adoc[] *** xref:mulesoft-automation-credits-1-0.adoc[] + ** xref:ai-features-and-data-usage.adoc[] ** xref:troubleshooting-usage-reports.adoc[] + ** xref:pricing.adoc[Pricing] * xref:java-support.adoc[] ** xref:partner-connector-upgrade.adoc[] ** xref:customer-connector-upgrade.adoc[] diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 1f71f1062..0d4c8f585 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -86,7 +86,20 @@ If your usage exceeds your contracted amount, MuleSoft sends a monthly overage i == Viewing Usage and Billing -Mule Credits usage, monthly statements, and overage billing are centralized in Salesforce Digital Wallet. If you have an Anypoint Platform organization, you can also view your usage and entitlement details in Anypoint Usage Reports for cross-platform transparency. +Mule Credits usage appears in both Anypoint Usage Reports and Salesforce Digital Wallet. Salesforce Digital Wallet is the source of truth for finalized Mule Credit totals, monthly statements, and overage billing. Anypoint Usage Reports provide granular usage visibility by usage type, business group, and application. + +Use Anypoint Usage Reports to investigate consumption spikes, understand which business groups and applications are driving usage, and support internal forecasting or cost allocation workflows. + +=== When to Use Each View + +* Use *Anypoint Usage Reports* to investigate what is driving consumption across usage types, business groups, and applications. +* Use *Salesforce Digital Wallet* to review finalized monthly consumption and billing outcomes. + +=== Granular Visibility Coverage + +Granular visibility is currently available for select usage types, with additional usage types planned. MuleSoft introduces coverage in phases, and coverage can vary over time. + +For usage report access and operational drill-down context, see xref:usage-reports.adoc[]. To view your Mule Credits consumption: diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index f711728cc..7ad237237 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -1,5 +1,5 @@ -= Usage and Pricing Metrics Reference -:keywords: usage metrics, pricing metrics, anypoint mq usage, api experience hub, api governance, api manager += Usage-Based Pricing: Usage and Rates +:keywords: usage metrics, pricing metrics, anypoint mq usage, api experience hub, api governance, api manager, mule credits, automation credits :page-aliases: pricing-metrics.adoc Anypoint Platform captures usage metrics across products, but not all metrics are billable or reflected in usage reports. @@ -78,6 +78,20 @@ Anypoint MQ API requests are available via API and aggregated on usage reports. | IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. |=== +== Anypoint Pricing Plans + +The available usage types depend on your Anypoint pricing plan. + +[%header%autowidth.spread] +|=== +| Available Usage Types | Subscription Plan + +.3+|Mule Flows, Mule Messages, Data Throughput, API Calls for Flex Gateway, API Manager Pre-Production, API Manager Production, and APIs Under Governance +|*MuleSoft Integration Starter* +|*MuleSoft Integration Advanced* +|*API Management Solution* +|=== + == Anypoint MQ Usage Anypoint MQ usage reports show this information in tables and cards: diff --git a/modules/ROOT/pages/usage-reports.adoc b/modules/ROOT/pages/usage-reports.adoc index a5d130149..83e4170e1 100644 --- a/modules/ROOT/pages/usage-reports.adoc +++ b/modules/ROOT/pages/usage-reports.adoc @@ -100,6 +100,17 @@ Use the Anypoint Usage API to programmatically access usage data. The API provid To use the API, see the API documentation for the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a/usage-api/[Anypoint Usage API] for access and implementation details. Users must have Usage Viewer permission to access the Usage API. +[[granular-mule-credits-visibility]] +== Granular Mule Credits Visibility + +Anypoint Usage Reports provide operational drill-down visibility for Mule Credits-related consumption. + +[NOTE] +==== +Use Salesforce Digital Wallet for finalized, billing-relevant Mule Credits totals and statements. +==== + +For detailed Mule Credits usage guidance, visibility coverage, and billing context, see xref:mule-credits-usage-and-rates.adoc[]. [[usage-reports-on-control-planes]] == Usage Reports on Control Planes From 24584334b4ef4457fdd77f2c40e04c7fe63db594 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Fri, 24 Jul 2026 18:24:00 +0530 Subject: [PATCH 02/15] fixed the note --- modules/ROOT/pages/usage-metrics.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 7ad237237..2d2993b56 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -29,7 +29,6 @@ The CPU limit configuration of each application is summarized at each environmen |API Manager |API instances: API instances in production, preproduction, and unclassified APIs (not associated with an environment) that are managed by API Manager after they are created using add, promote, or import options. a|API instances remain under management until they are deleted. Instances of API Manager are aggregated using a Max Concurrent model with three separate metrics for production, preproduction, and unclassified (APIs that aren't associated with an environment). -+ [NOTE] Data for API Manager is available starting in October 2024. From f9368046d3b39ec9eca8068ea946020ef5e61722 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Fri, 24 Jul 2026 21:38:28 +0530 Subject: [PATCH 03/15] Added Mulesoft visibility in usage reports --- .../pages/mule-credits-usage-and-rates.adoc | 2 ++ modules/ROOT/pages/usage-metrics.adoc | 21 ++++++++++++------- modules/ROOT/pages/usage-reports.adoc | 2 ++ 3 files changed, 17 insertions(+), 8 deletions(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 0d4c8f585..40ae079e5 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -101,6 +101,8 @@ Granular visibility is currently available for select usage types, with addition For usage report access and operational drill-down context, see xref:usage-reports.adoc[]. +For a summary of pricing models and where to review usage and billing context for each model, see xref:usage-metrics.adoc[]. + To view your Mule Credits consumption: . From the *App Launcher*, click *Digital Wallet*. diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 2d2993b56..3c91f6093 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -77,18 +77,23 @@ Anypoint MQ API requests are available via API and aggregated on usage reports. | IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. |=== -== Anypoint Pricing Plans - -The available usage types depend on your Anypoint pricing plan. +The following pricing models are available for Anypoint Platform. Use this summary to understand where to review usage and finalized billing information for each model. [%header%autowidth.spread] |=== -| Available Usage Types | Subscription Plan +| Pricing Model | Usage Visibility + +| *vCore* +| Review vCore usage in Anypoint Usage Reports. For detailed vCore metrics and behavior, see xref:usage-metrics.adoc#mule-runtime-usage[] and xref:usage-reports.adoc[]. + +| *Usage-Based Pricing (UBP)* +| Review UBP usage in Anypoint Usage Reports by product and metric. Use this page for product-specific metric definitions. + +| *Mule Credits* +| Review granular operational usage in Anypoint Usage Reports. Use Salesforce Digital Wallet for finalized Mule Credit totals, statements, and billing outcomes. For details, see xref:mule-credits-usage-and-rates.adoc[]. -.3+|Mule Flows, Mule Messages, Data Throughput, API Calls for Flex Gateway, API Manager Pre-Production, API Manager Production, and APIs Under Governance -|*MuleSoft Integration Starter* -|*MuleSoft Integration Advanced* -|*API Management Solution* +| *Automation* +| Review granular automation usage and rates in xref:automation-credits-usage-and-rates.adoc[]. Use monthly statements as the source of truth for finalized billing outcomes. |=== == Anypoint MQ Usage diff --git a/modules/ROOT/pages/usage-reports.adoc b/modules/ROOT/pages/usage-reports.adoc index 83e4170e1..a7fb39ca5 100644 --- a/modules/ROOT/pages/usage-reports.adoc +++ b/modules/ROOT/pages/usage-reports.adoc @@ -100,6 +100,8 @@ Use the Anypoint Usage API to programmatically access usage data. The API provid To use the API, see the API documentation for the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a/usage-api/[Anypoint Usage API] for access and implementation details. Users must have Usage Viewer permission to access the Usage API. +For a summary of pricing models and where to review usage and billing context for each model, see xref:usage-metrics.adoc[]. + [[granular-mule-credits-visibility]] == Granular Mule Credits Visibility From 35f4b24582f583c35a6f72238c12ac1473b6e14b Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Mon, 27 Jul 2026 19:59:25 +0530 Subject: [PATCH 04/15] Update Subscription plan and usage type --- .../automation-credits-usage-and-rates.adoc | 38 +++++++++++---- modules/ROOT/pages/usage-metrics.adoc | 46 +++++++------------ 2 files changed, 45 insertions(+), 39 deletions(-) diff --git a/modules/ROOT/pages/automation-credits-usage-and-rates.adoc b/modules/ROOT/pages/automation-credits-usage-and-rates.adoc index 4ffb36492..9550cc8b1 100644 --- a/modules/ROOT/pages/automation-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/automation-credits-usage-and-rates.adoc @@ -36,6 +36,34 @@ MuleSoft - Automation - Additional Credits (100) - (Gold, Platinum, Titanium) | xref:mulesoft-automation-credits-1-0.adoc[MuleSoft Automation Credits 1.0] |=== +== Usage Type Description + +The following table defines automation usage metrics by product and explains how each metric is calculated for reporting. + +[cols=3*] +|=== +|Product |Metric Description |Usage Details + +|Composer +|Composer task: Any discrete action executed on a Composer connector, including but not limited to read, create, update, and delete. +|Calculated on a per-action basis and aggregated as the total number of tasks completed within a billing cycle. + +.2+|RPA (Robotic Process Automation) +|RPA bot minutes: The total duration (in minutes) spent running process automations across all active bot sessions. +|Calculated by tracking active execution time. Parallel bot sessions, multi-bot processes, and test-phase runs each count toward total bot minutes. + +|RPA API Calls: Programmatic HTTP or REST requests used to trigger, monitor, or manage RPA bot workflows from external applications. +|Calculated on a per-request basis by summing all individual API calls made to the RPA Manager or RPA Bot API. + +|Intelligent Document Processing (IDP) +|IDP Document Pages: A single physical or digital document page processed by IDP document actions. +|Calculated per page processed (each page of multi-page documents counts separately). IDP actions executed by RPA consume document pages and corresponding RPA Bot Minutes. + +|MuleSoft for Flow: Integration +|Integration Tasks: A discrete execution of integration capabilities within Salesforce Flow. +|Calculated in real time per individual task execution, enabling immediate monitoring and aggregation of total consumption. +|=== + == MuleSoft Automation Credits A quantity of Automation Credits is included with certain MuleSoft Services, with the specific entitlement indicated on the Usage Details table on the Order Form for such Services. Automation Credits are consumed as you create and execute automations based on the rates in the following table. While MuleSoft Automation Credits 1.0 uses a conversion-based model, MuleSoft Automation Credits 2.0 and 3.0 use multiplier rates. Credit usage rates differ by subscription plan. Refer to the column that corresponds to your credit system. @@ -46,11 +74,6 @@ IMPORTANT: As of February 18, 2026, Flow Orchestration is included for customers |=== | Usage Type | MuleSoft Automation Credits 3.0 | MuleSoft Automation Credits 2.0 | MuleSoft Automation Credits 1.0 -| *Visibility and Reporting* -| *Digital Wallet:* Automation Credits 3.0 provides an instant visibility of credit consumption. -| *Anypoint Reports (Monthly):* Usage aggregated and reported via Sequoia on a monthly cycle. -| *Anypoint Reports (Monthly):* Legacy reporting via Sequoia based on monthly usage aggregates. - | *Flow Orchestration Runs* | *As of February 18, 2026, for Enterprise and Higher Editions*: Included + For customers on other editions, the https://help.salesforce.com/s/articleView?id=platform.flow_considerations_limit.htm&type=5[General Flow Limits^] apply. @@ -110,19 +133,16 @@ The method for viewing usage and handling billing varies based on the type of Au [%header%autowidth.spread] |=== -| Usage Type | Usage Visibility | Billing (monthly statements and overage) +| Usage Type | Usage Visibility | MuleSoft Automation Credits 3.0 | Digital Wallet (and optionally Anypoint Usage Reports if you have an Anypoint Platform org) -| Digital Wallet | MuleSoft Automation Credits 2.0 | Anypoint Usage Reports -| Sequoia | MuleSoft Automation Credits 1.0 | Anypoint Usage Reports -| Sequoia |=== == Monthly Account Summary Emails diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 3c91f6093..012cb923f 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -4,6 +4,22 @@ Anypoint Platform captures usage metrics across products, but not all metrics are billable or reflected in usage reports. +== Subscription Plan + +The available usage types depend on your Anypoint pricing plan. + +[%header%autowidth.spread] +|=== +| Subscription Plan | Available Usage Types + +| Integration Starter, Integration Advanced, API Management +| Mule Flows, Mule Messages, Data Throughput, API Calls for Omni/Flex Gateway, API Manager Pre-Production, API Manager Production, APIs Under Governance, Anypoint MQ API request, Object Store API request +|=== + +== Usage Type Description + +The following table defines usage metrics by product and explains how each metric is calculated for reporting. + [cols=3*] |=== |Product |Metric Description |Usage Details @@ -50,14 +66,6 @@ a|If an API is governed, all versions of that API are considered one governed AP | Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model | Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. -|Composer -|Composer task: Any action executed on a Composer connector, including but not limited to read, create, update, and delete -|Composer tasks are aggregated as a total of all actions during a month. - -|RPA -|Robotic Process Automation (“RPA”) bot minutes: The number of minutes running process automations across all bot sessions -|A single bot can run multiple parallel sessions, with RPA bot minutes counting for each parallel session. You can configure multiple bots to run the same process, with RPA bot minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA bot minutes. - |Anypoint MQ |Anypoint MQ API request: A request made to retrieve one or more messages from the Anypoint MQ APIs |Anypoint MQ uses API requests to calculate billing. @@ -72,28 +80,6 @@ Anypoint MQ API requests are available via API and aggregated on usage reports. |DataGraph orchestration: An API request made by Anypoint DataGraph to the source APIs to get data for the GraphQL API request made to Anypoint DataGraph |Orchestrations are not currently aggregated on usage reports. -| Intelligent Document Processing (IDP) -| Intelligent Document Processing (IDP) Document Pages: A single page processed by IDP -| IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. -|=== - -The following pricing models are available for Anypoint Platform. Use this summary to understand where to review usage and finalized billing information for each model. - -[%header%autowidth.spread] -|=== -| Pricing Model | Usage Visibility - -| *vCore* -| Review vCore usage in Anypoint Usage Reports. For detailed vCore metrics and behavior, see xref:usage-metrics.adoc#mule-runtime-usage[] and xref:usage-reports.adoc[]. - -| *Usage-Based Pricing (UBP)* -| Review UBP usage in Anypoint Usage Reports by product and metric. Use this page for product-specific metric definitions. - -| *Mule Credits* -| Review granular operational usage in Anypoint Usage Reports. Use Salesforce Digital Wallet for finalized Mule Credit totals, statements, and billing outcomes. For details, see xref:mule-credits-usage-and-rates.adoc[]. - -| *Automation* -| Review granular automation usage and rates in xref:automation-credits-usage-and-rates.adoc[]. Use monthly statements as the source of truth for finalized billing outcomes. |=== == Anypoint MQ Usage From ebe0cbe4060803b74cca6f96bd4fd80aff2d671e Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 28 Jul 2026 11:11:17 +0530 Subject: [PATCH 05/15] Update mule-credits-usage-and-rates.adoc --- modules/ROOT/pages/mule-credits-usage-and-rates.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 40ae079e5..55bd6b229 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -93,7 +93,7 @@ Use Anypoint Usage Reports to investigate consumption spikes, understand which b === When to Use Each View * Use *Anypoint Usage Reports* to investigate what is driving consumption across usage types, business groups, and applications. -* Use *Salesforce Digital Wallet* to review finalized monthly consumption and billing outcomes. +* Use *Salesforce Digital Wallet* to review finalized daily and monthly with usage type breakdown consumption and billing outcomes. === Granular Visibility Coverage From 5168b3f63f15f0a25f2a198d8c32109e48c91173 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 11:59:20 +0530 Subject: [PATCH 06/15] reverting automation credits doc --- .../automation-credits-usage-and-rates.adoc | 38 +++++-------------- 1 file changed, 9 insertions(+), 29 deletions(-) diff --git a/modules/ROOT/pages/automation-credits-usage-and-rates.adoc b/modules/ROOT/pages/automation-credits-usage-and-rates.adoc index 9550cc8b1..4ffb36492 100644 --- a/modules/ROOT/pages/automation-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/automation-credits-usage-and-rates.adoc @@ -36,34 +36,6 @@ MuleSoft - Automation - Additional Credits (100) - (Gold, Platinum, Titanium) | xref:mulesoft-automation-credits-1-0.adoc[MuleSoft Automation Credits 1.0] |=== -== Usage Type Description - -The following table defines automation usage metrics by product and explains how each metric is calculated for reporting. - -[cols=3*] -|=== -|Product |Metric Description |Usage Details - -|Composer -|Composer task: Any discrete action executed on a Composer connector, including but not limited to read, create, update, and delete. -|Calculated on a per-action basis and aggregated as the total number of tasks completed within a billing cycle. - -.2+|RPA (Robotic Process Automation) -|RPA bot minutes: The total duration (in minutes) spent running process automations across all active bot sessions. -|Calculated by tracking active execution time. Parallel bot sessions, multi-bot processes, and test-phase runs each count toward total bot minutes. - -|RPA API Calls: Programmatic HTTP or REST requests used to trigger, monitor, or manage RPA bot workflows from external applications. -|Calculated on a per-request basis by summing all individual API calls made to the RPA Manager or RPA Bot API. - -|Intelligent Document Processing (IDP) -|IDP Document Pages: A single physical or digital document page processed by IDP document actions. -|Calculated per page processed (each page of multi-page documents counts separately). IDP actions executed by RPA consume document pages and corresponding RPA Bot Minutes. - -|MuleSoft for Flow: Integration -|Integration Tasks: A discrete execution of integration capabilities within Salesforce Flow. -|Calculated in real time per individual task execution, enabling immediate monitoring and aggregation of total consumption. -|=== - == MuleSoft Automation Credits A quantity of Automation Credits is included with certain MuleSoft Services, with the specific entitlement indicated on the Usage Details table on the Order Form for such Services. Automation Credits are consumed as you create and execute automations based on the rates in the following table. While MuleSoft Automation Credits 1.0 uses a conversion-based model, MuleSoft Automation Credits 2.0 and 3.0 use multiplier rates. Credit usage rates differ by subscription plan. Refer to the column that corresponds to your credit system. @@ -74,6 +46,11 @@ IMPORTANT: As of February 18, 2026, Flow Orchestration is included for customers |=== | Usage Type | MuleSoft Automation Credits 3.0 | MuleSoft Automation Credits 2.0 | MuleSoft Automation Credits 1.0 +| *Visibility and Reporting* +| *Digital Wallet:* Automation Credits 3.0 provides an instant visibility of credit consumption. +| *Anypoint Reports (Monthly):* Usage aggregated and reported via Sequoia on a monthly cycle. +| *Anypoint Reports (Monthly):* Legacy reporting via Sequoia based on monthly usage aggregates. + | *Flow Orchestration Runs* | *As of February 18, 2026, for Enterprise and Higher Editions*: Included + For customers on other editions, the https://help.salesforce.com/s/articleView?id=platform.flow_considerations_limit.htm&type=5[General Flow Limits^] apply. @@ -133,16 +110,19 @@ The method for viewing usage and handling billing varies based on the type of Au [%header%autowidth.spread] |=== -| Usage Type | Usage Visibility +| Usage Type | Usage Visibility | Billing (monthly statements and overage) | MuleSoft Automation Credits 3.0 | Digital Wallet (and optionally Anypoint Usage Reports if you have an Anypoint Platform org) +| Digital Wallet | MuleSoft Automation Credits 2.0 | Anypoint Usage Reports +| Sequoia | MuleSoft Automation Credits 1.0 | Anypoint Usage Reports +| Sequoia |=== == Monthly Account Summary Emails From 61621e9a36b9341ba01a960657c2338c169d1bc5 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:01:57 +0530 Subject: [PATCH 07/15] reverted recent changes in nav and usage metrics --- modules/ROOT/nav.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index a07ab9bfc..96f9abae4 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -45,15 +45,15 @@ ** xref:api-led-operate.adoc[Step 6. Monitor and Manage] * xref:usage-reports.adoc[Usage Reports] ** xref:usage-reports-release-notes.adoc[Release Notes] - ** xref:usage-metrics.adoc[Usage-Based Pricing: Usage and Rates] + ** xref:usage-metrics.adoc[Usage and Pricing Metrics Reference] + ** xref:ai-features-and-data-usage.adoc[] + ** xref:pricing.adoc[Pricing] ** xref:mule-credits-usage-and-rates.adoc[] ** xref:automation-credits-usage-and-rates.adoc[] *** xref:mulesoft-automation-credits-3-0.adoc[] *** xref:mulesoft-automation-credits-2-0.adoc[] *** xref:mulesoft-automation-credits-1-0.adoc[] - ** xref:ai-features-and-data-usage.adoc[] ** xref:troubleshooting-usage-reports.adoc[] - ** xref:pricing.adoc[Pricing] * xref:java-support.adoc[] ** xref:partner-connector-upgrade.adoc[] ** xref:customer-connector-upgrade.adoc[] From f5d6f9af7a8c5c690930398eb26a150a47aa17f8 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:02:08 +0530 Subject: [PATCH 08/15] reverted changes --- modules/ROOT/pages/usage-metrics.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 012cb923f..e89e6822a 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -1,5 +1,5 @@ -= Usage-Based Pricing: Usage and Rates -:keywords: usage metrics, pricing metrics, anypoint mq usage, api experience hub, api governance, api manager, mule credits, automation credits += Usage and Pricing Metrics Reference +:keywords: usage metrics, pricing metrics, anypoint mq usage, api experience hub, api governance, api manager :page-aliases: pricing-metrics.adoc Anypoint Platform captures usage metrics across products, but not all metrics are billable or reflected in usage reports. From 79b44ce6a8d4145f15f76cc5c441fa1a0ae4cfab Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:06:06 +0530 Subject: [PATCH 09/15] reverted usage metrics changes --- modules/ROOT/pages/usage-metrics.adoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index e89e6822a..391bd3bf1 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -66,6 +66,14 @@ a|If an API is governed, all versions of that API are considered one governed AP | Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model | Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. +|Composer +|Composer task: Any action executed on a Composer connector, including but not limited to read, create, update, and delete +|Composer tasks are aggregated as a total of all actions during a month. + +|RPA +|Robotic Process Automation ("RPA") bot minutes: The number of minutes running process automations across all bot sessions +|A single bot can run multiple parallel sessions, with RPA bot minutes counting for each parallel session. You can configure multiple bots to run the same process, with RPA bot minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA bot minutes. + |Anypoint MQ |Anypoint MQ API request: A request made to retrieve one or more messages from the Anypoint MQ APIs |Anypoint MQ uses API requests to calculate billing. @@ -80,6 +88,9 @@ Anypoint MQ API requests are available via API and aggregated on usage reports. |DataGraph orchestration: An API request made by Anypoint DataGraph to the source APIs to get data for the GraphQL API request made to Anypoint DataGraph |Orchestrations are not currently aggregated on usage reports. +|Intelligent Document Processing (IDP) +|Intelligent Document Processing (IDP) Document Pages: A single page processed by IDP +|IDP document actions might process documents that have more than one page, with each page counting separately. When RPA executes document actions, it also counts towards document pages and additionally consumes the corresponding RPA Bot Minutes, accounting for the time the RPA process runs. |=== == Anypoint MQ Usage From 600a1ed54bc8bcecff34902bf1a1dc08ee313e10 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:12:09 +0530 Subject: [PATCH 10/15] updating vCore content --- modules/ROOT/pages/usage-metrics.adoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 391bd3bf1..96b458e8a 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -24,7 +24,7 @@ The following table defines usage metrics by product and explains how each metri |=== |Product |Metric Description |Usage Details -.6+|Mule Runtime +.8+|Mule Runtime |Mule flow: Flow within a deployed and running Mule app that contains a Mule event source or route APIKit request |Flows are aggregated using a Max Concurrent model. The usage for a month is the highest number of flows that exist in a single given hour during a month. @@ -32,6 +32,10 @@ The following table defines usage metrics by product and explains how each metri |A Mule message counts as a single unit when an event source triggers it. Messages are aggregated using a total of all messages sent during a month. |Data throughput: Total amount of data transferred in and out of the infrastructure that runs Mule where the Mule app is deployed |Data throughput counts when the deployed application transfers data to execute its business logic, including but not limited to internal operational network traffic for monitoring, logs, and health checks. Data throughput is aggregated as a sum of all bytes during a month. +|vCore Usage in Production: Virtual processing capacity allocated to run Mule applications and APIs in production environments +|Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in production environments. +|vCore Usage in Preproduction: Virtual processing capacity allocated to run Mule applications and APIs in non-production environments, such as sandbox, QA, staging, and development +|Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in non-production environments. | Cluster capacity: A set of workers or nodes that act as a single deployment target for a given Runtime Fabric instance | Allocatable CPU capacity of each node within the Runtime Fabric instance. | CPU Limit (Millicores): Maximum amount of CPU resources a worker node in Runtime Fabric can use From ad775b7c490e2e6ab6ff66bfc82aeab35a7055d0 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:13:02 +0530 Subject: [PATCH 11/15] removing extra spaces --- modules/ROOT/pages/usage-metrics.adoc | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 96b458e8a..d3796fd2e 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -36,15 +36,15 @@ The following table defines usage metrics by product and explains how each metri |Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in production environments. |vCore Usage in Preproduction: Virtual processing capacity allocated to run Mule applications and APIs in non-production environments, such as sandbox, QA, staging, and development |Calculated based on the peak allocated virtual cores assigned to active CloudHub (CH1) and CloudHub 2.0 (CH2) application workers in non-production environments. -| Cluster capacity: A set of workers or nodes that act as a single deployment target for a given Runtime Fabric instance -| Allocatable CPU capacity of each node within the Runtime Fabric instance. -| CPU Limit (Millicores): Maximum amount of CPU resources a worker node in Runtime Fabric can use +|Cluster capacity: A set of workers or nodes that act as a single deployment target for a given Runtime Fabric instance +|Allocatable CPU capacity of each node within the Runtime Fabric instance. +|CPU Limit (Millicores): Maximum amount of CPU resources a worker node in Runtime Fabric can use a| The amount of CPU usage is aggregated over a specific period of time, such as an hour or a day. The CPU limit configuration of each application is summarized at each environment ID, then at each business group, and then at the root organization ID for preproduction (sandbox) and production environment types separately. -| CPU Reserve (Millicores): A guaranteed minimum amount of CPU resources allocated to a worker node in the Runtime Fabric instance -| CPU reserve is aggregated by calculating the total amount of CPU resources allocated by the user to reserve for applications within the cluster or Runtime Fabric instance. +|CPU Reserve (Millicores): A guaranteed minimum amount of CPU resources allocated to a worker node in the Runtime Fabric instance +|CPU reserve is aggregated by calculating the total amount of CPU resources allocated by the user to reserve for applications within the cluster or Runtime Fabric instance. |API Manager |API instances: API instances in production, preproduction, and unclassified APIs (not associated with an environment) that are managed by API Manager after they are created using add, promote, or import options. @@ -61,14 +61,14 @@ a|If an API is governed, all versions of that API are considered one governed AP |Omni Gateway requests are aggregated as a total of all requests during a month. .3+|LLM Proxy -| Prompt tokens: Number of tokens an LLM Proxy in the prompts an LLM Proxy sends to a specific LLM Model -| These tokens are the sum of all prompt tokens a specific LLM Proxy sends to a specific LLM Model during a month. A prompt sent to an LLM Proxy are considered an Omni Gateway API call and count towards the Omni Gateway API call metric. +|Prompt tokens: Number of tokens an LLM Proxy in the prompts an LLM Proxy sends to a specific LLM Model +|These tokens are the sum of all prompt tokens a specific LLM Proxy sends to a specific LLM Model during a month. A prompt sent to an LLM Proxy are considered an Omni Gateway API call and count towards the Omni Gateway API call metric. -| Completion tokens: Number of tokens in the responses that an LLM Proxy receives from a specific LLM Model +|Completion tokens: Number of tokens in the responses that an LLM Proxy receives from a specific LLM Model |These tokens are the sum of all response tokens a specific LLM Proxy receives from a specific LLM Model during a month. -| Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model -| Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. +|Total tokens: Total number of tokens used in interactions between an LLM Proxy and a specific LLM Model +|Some LLM Providers, such as Gemini, use thinking tokens. Total tokens are the sum of prompt tokens, completion tokens, and thinking tokens if applicable. |Composer |Composer task: Any action executed on a Composer connector, including but not limited to read, create, update, and delete From 66880a8fa72ef1cdaeb2f7ff3b149ee31577829c Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 12:15:47 +0530 Subject: [PATCH 12/15] reverting subscription plan table --- modules/ROOT/pages/usage-metrics.adoc | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index d3796fd2e..e420bc665 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -4,18 +4,6 @@ Anypoint Platform captures usage metrics across products, but not all metrics are billable or reflected in usage reports. -== Subscription Plan - -The available usage types depend on your Anypoint pricing plan. - -[%header%autowidth.spread] -|=== -| Subscription Plan | Available Usage Types - -| Integration Starter, Integration Advanced, API Management -| Mule Flows, Mule Messages, Data Throughput, API Calls for Omni/Flex Gateway, API Manager Pre-Production, API Manager Production, APIs Under Governance, Anypoint MQ API request, Object Store API request -|=== - == Usage Type Description The following table defines usage metrics by product and explains how each metric is calculated for reporting. From 88a22fbb37ca6c63da96e95aa5608d148462437d Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 28 Jul 2026 16:28:32 +0530 Subject: [PATCH 13/15] fixed PM comments --- .../pages/mule-credits-usage-and-rates.adoc | 25 +++++-------------- modules/ROOT/pages/usage-reports.adoc | 2 +- 2 files changed, 7 insertions(+), 20 deletions(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 55bd6b229..5d0f18bcc 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -86,29 +86,16 @@ If your usage exceeds your contracted amount, MuleSoft sends a monthly overage i == Viewing Usage and Billing -Mule Credits usage appears in both Anypoint Usage Reports and Salesforce Digital Wallet. Salesforce Digital Wallet is the source of truth for finalized Mule Credit totals, monthly statements, and overage billing. Anypoint Usage Reports provide granular usage visibility by usage type, business group, and application. +Mule Credits usage is available in both Anypoint Usage Reports and Salesforce Digital Wallet. Salesforce Digital Wallet remains the billing source of truth for finalized Mule Credits totals, statements, and overage outcomes. Anypoint Usage Reports provide granular visibility into consumption by usage type, business group, and application. -Use Anypoint Usage Reports to investigate consumption spikes, understand which business groups and applications are driving usage, and support internal forecasting or cost allocation workflows. +Use both views together for a complete view of Mule Credits consumption. Digital Wallet shows finalized totals and trends. Anypoint Usage Reports show consumption details by usage type, business group, and application. Values can differ between these views. -=== When to Use Each View - -* Use *Anypoint Usage Reports* to investigate what is driving consumption across usage types, business groups, and applications. -* Use *Salesforce Digital Wallet* to review finalized daily and monthly with usage type breakdown consumption and billing outcomes. - -=== Granular Visibility Coverage - -Granular visibility is currently available for select usage types, with additional usage types planned. MuleSoft introduces coverage in phases, and coverage can vary over time. +Use Anypoint Usage Reports to investigate consumption spikes, identify which business groups and applications are driving usage, and support internal forecasting or cost allocation workflows. -For usage report access and operational drill-down context, see xref:usage-reports.adoc[]. - -For a summary of pricing models and where to review usage and billing context for each model, see xref:usage-metrics.adoc[]. - -To view your Mule Credits consumption: - -. From the *App Launcher*, click *Digital Wallet*. -. Locate the *Mule Credits* consumption card in the *Consumption Cards* tab. +=== When to Use Each View -Digital Wallet is available in Lightning Experience in Enterprise and Unlimited editions, and requires the View Consumption user permission. +* Use *Anypoint Usage Reports* to analyze what is driving consumption across usage types, business groups, and applications. +* Use *Salesforce Digital Wallet* to review finalized daily and monthly consumption and billing outcomes. === Digital Wallet Features at a Glance diff --git a/modules/ROOT/pages/usage-reports.adoc b/modules/ROOT/pages/usage-reports.adoc index a7fb39ca5..81c4c1fae 100644 --- a/modules/ROOT/pages/usage-reports.adoc +++ b/modules/ROOT/pages/usage-reports.adoc @@ -112,7 +112,7 @@ Anypoint Usage Reports provide operational drill-down visibility for Mule Credit Use Salesforce Digital Wallet for finalized, billing-relevant Mule Credits totals and statements. ==== -For detailed Mule Credits usage guidance, visibility coverage, and billing context, see xref:mule-credits-usage-and-rates.adoc[]. +For detailed Mule Credits usage guidance and billing context, see xref:mule-credits-usage-and-rates.adoc[]. [[usage-reports-on-control-planes]] == Usage Reports on Control Planes From 1174c1596d823614b8748de5579041f07db4fad1 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 28 Jul 2026 21:53:02 +0530 Subject: [PATCH 14/15] Apply suggestion from @JennyHajee Co-authored-by: Jenny Hajee <94015849+JennyHajee@users.noreply.github.com> --- modules/ROOT/pages/usage-metrics.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index e420bc665..91e4fcc41 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -6,7 +6,7 @@ Anypoint Platform captures usage metrics across products, but not all metrics ar == Usage Type Description -The following table defines usage metrics by product and explains how each metric is calculated for reporting. +These table defines usage metrics by product and explains how each metric is calculated for reporting. [cols=3*] |=== From a55e1ccd01ec49c54639173cfe34672e1b4aeff4 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 28 Jul 2026 21:53:18 +0530 Subject: [PATCH 15/15] Apply suggestion from @JennyHajee Co-authored-by: Jenny Hajee <94015849+JennyHajee@users.noreply.github.com> --- modules/ROOT/pages/usage-metrics.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/usage-metrics.adoc b/modules/ROOT/pages/usage-metrics.adoc index 91e4fcc41..3ed23aea8 100644 --- a/modules/ROOT/pages/usage-metrics.adoc +++ b/modules/ROOT/pages/usage-metrics.adoc @@ -63,7 +63,7 @@ a|If an API is governed, all versions of that API are considered one governed AP |Composer tasks are aggregated as a total of all actions during a month. |RPA -|Robotic Process Automation ("RPA") bot minutes: The number of minutes running process automations across all bot sessions +|Robotic Process Automation (RPA) bot minutes: The number of minutes running process automations across all bot sessions |A single bot can run multiple parallel sessions, with RPA bot minutes counting for each parallel session. You can configure multiple bots to run the same process, with RPA bot minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA bot minutes. |Anypoint MQ