From 338aef5ee020711ade230a737586ee566c900ee8 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Wed, 13 May 2026 12:05:44 +0530 Subject: [PATCH 01/12] W-22448266-mule-credits-usage-and-rates-KS --- modules/ROOT/nav.adoc | 1 + .../pages/mule-credits-usage-and-rates.adoc | 98 +++++++++++++++++++ 2 files changed, 99 insertions(+) create mode 100644 modules/ROOT/pages/mule-credits-usage-and-rates.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 7435a0d69..99a3964c1 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -16,6 +16,7 @@ ** xref:usage-reports-release-notes.adoc[Release Notes] ** xref:usage-metrics.adoc[Usage and Pricing Metrics Reference] ** 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[] diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc new file mode 100644 index 000000000..40df83255 --- /dev/null +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -0,0 +1,98 @@ += Mule Credits Usage and Rates + +Mule Credits are a universal currency that you can freely use across usage types. You buy and draw down from your purchased capacity pool as you use the MuleSoft platform. Unlike the previous per-product metering model (Universal Base Pricing), a single pool of credits replaces individual product meters. This gives you the flexibility to consume credits across the entire MuleSoft platform based on your usage. Credits are shared across your entire Anypoint Platform organization. You can't manage them per business group. + +Available in Salesforce Digital Wallet, use Mule Credits before the Order End Date on your Order Form — rollovers aren't permitted. To see which usage types are included in your subscription, refer to the Usage Details table on your Order Form, Subscription Plan, or Features and Entitlement Document. + +== Mule Credits by Subscription Plan + +The usage types available to you depend on your subscription plan. + +[%header%autowidth.spread] +|=== +| Subscription Plan | Available Usage Types + +| *MuleSoft Integration* +| MuleSoft Flows, MuleSoft Messages, Private Spaces, Network Connections, Load Balancers + +| *MuleSoft Automation* +| IDP Pages, Flow Integration Tasks + +| *MuleSoft AI & API Management* +| Managed Assets, Gateway Requests, Private Spaces, Network Connections + +| *MuleSoft Agent Fabric* +| MuleSoft Flows, MuleSoft Messages, Managed Assets, Gateway Requests, Private Spaces, Network Connections + +| *MuleSoft All-Access* +| All usage types: MuleSoft Flows, MuleSoft Messages, Managed Assets, Gateway Requests, IDP Pages, Flow Integration Tasks, Private Spaces, Network Connections, Load Balancers + +| *MuleSoft All-Access License* +| All usage types: MuleSoft Flows, MuleSoft Messages, Managed Assets, Gateway Requests, IDP Pages, Flow Integration Tasks, Private Spaces, Network Connections, Load Balancers +|=== + +NOTE: MuleSoft All-Access License supports pre-commit and unlimited usage models. + +== Usage Types + +Each usage type (also referred to as a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the https://www.salesforce.com/mulesoft/mule-credits/rates/[Mule Credits Rate Card^]. + +[%header%autowidth.spread] +|=== +| Usage Type | Description | Unit + +| *MuleSoft Flows* +| A flow is a sequence of logical operations within a deployed Mule application that contains a Mule event source or APIkit route. Anypoint Platform tracks the number of flows across all business groups, environments, and applications. Usage is calculated by identifying the peak-hour flow count for each day and aggregating those daily peaks over the month. This is a sum-based meter — unlike the previous high-watermark model, all daily flow counts contribute to monthly usage. Subflows used for error handling or modular processing are included in the count. +| Per 1 Mule Flow + +| *MuleSoft Messages* +| The total volume of data containers processed by the runtime. The platform counts a message each time an event source triggers it, and aggregates message counts daily and monthly. Changes to a message as it moves through application flows are not tracked — only the initial trigger is counted. +| Per 1 million Mule Messages + +| *Managed Assets* +| An API, Agent, Model Context Protocol (MCP) Server, or Large Language Model (LLM) with at least one active instance in API Manager deployed to a Mule or Omni Gateway. Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group do not incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. +| Per 1 Managed Asset + +| *Gateway Requests* +| The number of calls made to all assets through the Omni Gateway. Usage is the sum of all requests processed, regardless of response status. +| Per 1 million Gateway Requests + +| *IDP Pages* +| The number of individual document pages processed by Intelligent Document Processing (IDP) in Anypoint IDP or MuleSoft for Flow: IDP. Each page is counted as a separate unit. +| Per 1 IDP Page + +| *Flow Integration Tasks* +| Individual units of work or actions (reading, creating, or updating a record) executed within a flow for MuleSoft for Flow: Integration. +| Per 1 Flow Integration Task + +| *Private Spaces* +| Dedicated, isolated logical instances within CloudHub 2.0. Anypoint Platform consumes credits based on provisioning of secure network instances, measured per day. +| Per 1 Private Space + +| *Network Connections* +| Active connections between the MuleSoft environment and external virtual private clouds (VPCs), virtual private networks (VPNs), or on-premises data centers, tracked per active connection per day. +| Per 1 Network Connection + +| *Load Balancers* +| Dedicated Load Balancers (DLBs) used to route external traffic to Mule applications, tracked per provisioned load balancer per day. +| Per 1 Load Balancer +|=== + +== 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. + +To view your Mule Credits consumption: + +. From the *App Launcher*, click *Digital Wallet*. +. Click the *Consumption Cards* tab. +. Locate the *Mule Credits* consumption card. + +Digital Wallet is available in Lightning Experience in Enterprise and Unlimited editions, and requires the View Consumption user permission. + +== See Also + +* https://help.salesforce.com/s/articleView?id=xcloud.wallet_enabled_products_rate_cards.htm&type=5[Digital Wallet–Enabled Consumption-Based Products^] (Salesforce Help) +* https://www.salesforce.com/mulesoft/mule-credits/rates/[Mule Credits Rate Card^] +* xref:automation-credits-usage-and-rates.adoc[] +* xref:usage-reports.adoc[] From 0c2948b0c0f655233873386d0d7fad75c5dd26fd Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Mon, 18 May 2026 19:43:48 +0530 Subject: [PATCH 02/12] added-rate-card-links --- .../pages/mule-credits-usage-and-rates.adoc | 67 ++++++++++++------- 1 file changed, 42 insertions(+), 25 deletions(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 40df83255..191d17753 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -1,8 +1,8 @@ = Mule Credits Usage and Rates -Mule Credits are a universal currency that you can freely use across usage types. You buy and draw down from your purchased capacity pool as you use the MuleSoft platform. Unlike the previous per-product metering model (Universal Base Pricing), a single pool of credits replaces individual product meters. This gives you the flexibility to consume credits across the entire MuleSoft platform based on your usage. Credits are shared across your entire Anypoint Platform organization. You can't manage them per business group. +A Mule Credit is a fungible currency that allows you to draw down from a single capacity pool as you consume services across MuleSoft. Instead of managing different usage types for all products, you purchase a package of credits that can be used flexibly across the entire MuleSoft platform. As you use these capabilities, Anypoint Platform deducts the corresponding credit amounts from your available balance. -Available in Salesforce Digital Wallet, use Mule Credits before the Order End Date on your Order Form — rollovers aren't permitted. To see which usage types are included in your subscription, refer to the Usage Details table on your Order Form, Subscription Plan, or Features and Entitlement Document. +Credits are shared across your entire Anypoint Platform organization and cannot be managed per business group. Use Mule Credits before the Order End Date set in the Usage Details table on your Order Form — rollovers are not permitted. To see which usage types are included in your subscription, refer to your Order Form, Subscription Plan, or Features and Entitlement Document. == Mule Credits by Subscription Plan @@ -35,49 +35,46 @@ NOTE: MuleSoft All-Access License supports pre-commit and unlimited usage models == Usage Types -Each usage type (also referred to as a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the https://www.salesforce.com/mulesoft/mule-credits/rates/[Mule Credits Rate Card^]. +Each usage type (also referred to as a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the <<_rate_cards,Rate Cards>> section. [%header%autowidth.spread] |=== -| Usage Type | Description | Unit +| Usage Type | Description | *MuleSoft Flows* -| A flow is a sequence of logical operations within a deployed Mule application that contains a Mule event source or APIkit route. Anypoint Platform tracks the number of flows across all business groups, environments, and applications. Usage is calculated by identifying the peak-hour flow count for each day and aggregating those daily peaks over the month. This is a sum-based meter — unlike the previous high-watermark model, all daily flow counts contribute to monthly usage. Subflows used for error handling or modular processing are included in the count. -| Per 1 Mule Flow +| A flow is a sequence of logical operations within a deployed Mule application that contains a Mule event source or APIkit route. Anypoint Platform tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24-hour period starting at 00:00 UTC, the hour with the highest flow count is identified as the daily peak. Based on your contract term, MuleSoft aggregates these daily peaks over the month or year to determine your final usage. This is a sum-based meter — unlike the previous high-watermark model, all daily flow counts contribute to your total usage. Subflows used for error handling or modular processing are included in the count. | *MuleSoft Messages* -| The total volume of data containers processed by the runtime. The platform counts a message each time an event source triggers it, and aggregates message counts daily and monthly. Changes to a message as it moves through application flows are not tracked — only the initial trigger is counted. -| Per 1 million Mule Messages +| The total volume of data containers processed by the runtime. The platform counts a message each time an event source triggers it, and aggregates message counts daily (UTC time) and monthly. Changes to a message as it moves through application flows are not tracked — only the initial trigger is counted. | *Managed Assets* -| An API, Agent, Model Context Protocol (MCP) Server, or Large Language Model (LLM) with at least one active instance in API Manager deployed to a Mule or Omni Gateway. Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group do not incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. -| Per 1 Managed Asset +| An asset is considered managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Managed assets include APIs, Agents, Model Context Protocol (MCP) Servers, and Large Language Models (LLMs). Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group do not incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. | *Gateway Requests* -| The number of calls made to all assets through the Omni Gateway. Usage is the sum of all requests processed, regardless of response status. -| Per 1 million Gateway Requests +| Any request received by https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Usage is measured as the sum of all processed requests, regardless of response status. | *IDP Pages* -| The number of individual document pages processed by Intelligent Document Processing (IDP) in Anypoint IDP or MuleSoft for Flow: IDP. Each page is counted as a separate unit. -| Per 1 IDP Page +| The number of individual document pages processed by Intelligent Document Processing (IDP) in https://docs.mulesoft.com/idp/[MuleSoft IDP^] or https://blogs.mulesoft.com/news/mulesoft-for-flow-intelligent-document-processing/[MuleSoft for Flow: IDP^]. Each page within a document is counted as a separate unit, and only successful LLM responses are charged. | *Flow Integration Tasks* -| Individual units of work or actions (reading, creating, or updating a record) executed within a flow for MuleSoft for Flow: Integration. -| Per 1 Flow Integration Task +| Individual units of work or actions (reading, creating, or updating a record) executed within https://www.mulesoft.com/platform/flow-integration[MuleSoft for Flow: Integration^]. | *Private Spaces* -| Dedicated, isolated logical instances within CloudHub 2.0. Anypoint Platform consumes credits based on provisioning of secure network instances, measured per day. -| Per 1 Private Space +| A https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about[Private Space^] is a dedicated, isolated environment in CloudHub 2.0 for running your apps. Credits are consumed based on the total number of provisioned Private Spaces per day. After you deprovision a Private Space, it stops consuming credits from the next calendar date onwards. | *Network Connections* -| Active connections between the MuleSoft environment and external virtual private clouds (VPCs), virtual private networks (VPNs), or on-premises data centers, tracked per active connection per day. -| Per 1 Network Connection +| Network connections allow you to securely connect corporate data centers and on-premises applications to CloudHub 1.0 and https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about#private-network[CloudHub 2.0^] using a VPN or AWS Transit Gateway. Credits are consumed based on the total number of active network connections per day. After you deprovision a network connection, it stops consuming credits from the next calendar date onwards. | *Load Balancers* -| Dedicated Load Balancers (DLBs) used to route external traffic to Mule applications, tracked per provisioned load balancer per day. -| Per 1 Load Balancer +| https://docs.mulesoft.com/cloudhub/cloudhub-dedicated-load-balancer[Dedicated Load Balancers^] used to distribute incoming traffic across multiple workers or instances. Credits are consumed based on the total number of provisioned load balancers per day. After you deprovision a load balancer, it stops consuming credits from the next calendar date onwards. |=== +== Rate Cards + +You consume Mule Credits at the applicable multiplier rate based on the usage type identified in the https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule_Credit_Rate_Card.pdf[Mule Credit Rate Card^]. + +Mule Credits must be used before the Order End Date set forth in the Usage Details table on the Order Form, and no rollover will be permitted. If your usage happens to exceed your contracted amount, MuleSoft automatically sends a monthly overage invoice to your primary billing contact at your standard contracted rate. Contact your account team with any questions about your contract or billing. + == 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. @@ -85,14 +82,34 @@ Mule Credits usage, monthly statements, and overage billing are centralized in S To view your Mule Credits consumption: . From the *App Launcher*, click *Digital Wallet*. -. Click the *Consumption Cards* tab. -. Locate the *Mule Credits* consumption card. +. Locate the *Mule Credits* consumption card in the *Consumption Cards* tab. Digital Wallet is available in Lightning Experience in Enterprise and Unlimited editions, and requires the View Consumption user permission. +=== Digital Wallet Features at a Glance + +[%header%autowidth.spread] +|=== +| Feature | For More Information + +| Monitor and analyze near-real-time usage for your consumption-based products. +| https://help.salesforce.com/s/articleView?id=xcloud.wallet_monitor_usage.htm&language=en_US&type=5[Monitor Usage for Consumption-Based Products in Digital Wallet^] + +| View the Consumption Analytics dashboard, which includes Tableau Next visualizations that leverage standard consumption tags. Visualizations are interactive, allowing you to instantly transform your view, drill down into details, and optimize business planning with consumption forecasting. +| https://help.salesforce.com/s/articleView?id=xcloud.wallet_consumption_analytics_dash.htm&language=en_US&type=5[Consumption Analytics Dashboard (Tableau Next)^] + +| Set customized threshold alerts to receive usage notifications when your org's usage exceeds specified thresholds. Also includes automated Monthly Account Summary emails that summarize usage from the previous month. +| https://help.salesforce.com/s/articleView?id=xcloud.wallet_get_notified.htm&type=5[Get Notifications about Your Usage^] +|=== + +To access Digital Wallet, see https://help.salesforce.com/s/articleView?id=xcloud.wallet_access.htm&type=5[Access Digital Wallet^]. + == See Also +* https://ptd.salesforce.com/#0[Salesforce Product Terms Dictionary^] * https://help.salesforce.com/s/articleView?id=xcloud.wallet_enabled_products_rate_cards.htm&type=5[Digital Wallet–Enabled Consumption-Based Products^] (Salesforce Help) -* https://www.salesforce.com/mulesoft/mule-credits/rates/[Mule Credits Rate Card^] +* https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule-Credit-Feature-Matrix-1.pdf[Feature Mapping^] +* https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule_Credit_Rate_Card.pdf[Mule Credit Rate Card^] +* https://www.salesforce.com/mulesoft/rates[MuleSoft Rates Landing Page^] * xref:automation-credits-usage-and-rates.adoc[] * xref:usage-reports.adoc[] From 7d9a38a67b54fb1df8554aa413d5c4ee2556c3c8 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 19 May 2026 11:27:22 +0530 Subject: [PATCH 03/12] fixed technical feedback --- .../ROOT/pages/mule-credits-usage-and-rates.adoc | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 191d17753..92f99c083 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -42,13 +42,19 @@ Each usage type (also referred to as a meter) tracks a specific dimension of pla | Usage Type | Description | *MuleSoft Flows* -| A flow is a sequence of logical operations within a deployed Mule application that contains a Mule event source or APIkit route. Anypoint Platform tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24-hour period starting at 00:00 UTC, the hour with the highest flow count is identified as the daily peak. Based on your contract term, MuleSoft aggregates these daily peaks over the month or year to determine your final usage. This is a sum-based meter — unlike the previous high-watermark model, all daily flow counts contribute to your total usage. Subflows used for error handling or modular processing are included in the count. +| A flow is a sequence of logical operations configured within the XML `` element of a Mule application. The runtime report tracks the flows within a deployed and running Mule application that contains a Mule event source or APIkit route requests. + +Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow might receive a record and transform data into a given format that another flow processes. + +To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24 hour period starting at 00:00 UTC, a single hour with the highest flow count is identified as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine your final usage. | *MuleSoft Messages* -| The total volume of data containers processed by the runtime. The platform counts a message each time an event source triggers it, and aggregates message counts daily (UTC time) and monthly. Changes to a message as it moves through application flows are not tracked — only the initial trigger is counted. +| The total volume of data containers processed by the runtime. To track message usage, the runtime report counts the number of times a Mule event source triggers a message. To calculate usage, MuleSoft aggregates the number of messages daily (UTC time) and monthly. After a message is triggered, the report doesn’t track changes to the message because the message is processed within the application’s flows. | *Managed Assets* -| An asset is considered managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Managed assets include APIs, Agents, Model Context Protocol (MCP) Servers, and Large Language Models (LLMs). Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group do not incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. +| An asset (API, Agent, MCP Server, or LLM) is considered managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. + +Multiple instances within the same business group don't incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. | *Gateway Requests* | Any request received by https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Usage is measured as the sum of all processed requests, regardless of response status. @@ -102,13 +108,11 @@ Digital Wallet is available in Lightning Experience in Enterprise and Unlimited | https://help.salesforce.com/s/articleView?id=xcloud.wallet_get_notified.htm&type=5[Get Notifications about Your Usage^] |=== -To access Digital Wallet, see https://help.salesforce.com/s/articleView?id=xcloud.wallet_access.htm&type=5[Access Digital Wallet^]. +For more information about Digital Wallet access, see https://help.salesforce.com/s/articleView?id=xcloud.wallet_access.htm&type=5[Access Digital Wallet^]. == See Also -* https://ptd.salesforce.com/#0[Salesforce Product Terms Dictionary^] * https://help.salesforce.com/s/articleView?id=xcloud.wallet_enabled_products_rate_cards.htm&type=5[Digital Wallet–Enabled Consumption-Based Products^] (Salesforce Help) -* https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule-Credit-Feature-Matrix-1.pdf[Feature Mapping^] * https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule_Credit_Rate_Card.pdf[Mule Credit Rate Card^] * https://www.salesforce.com/mulesoft/rates[MuleSoft Rates Landing Page^] * xref:automation-credits-usage-and-rates.adoc[] From 25dcfd4f99d8daca6216fada958c48b98df8c080 Mon Sep 17 00:00:00 2001 From: Kabilan Sarathi Date: Tue, 19 May 2026 13:39:15 +0530 Subject: [PATCH 04/12] fixed-review-comments --- .../pages/mule-credits-usage-and-rates.adoc | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc index 92f99c083..a2ac4c21a 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -1,8 +1,8 @@ = Mule Credits Usage and Rates -A Mule Credit is a fungible currency that allows you to draw down from a single capacity pool as you consume services across MuleSoft. Instead of managing different usage types for all products, you purchase a package of credits that can be used flexibly across the entire MuleSoft platform. As you use these capabilities, Anypoint Platform deducts the corresponding credit amounts from your available balance. +A Mule Credit is a fungible currency that allows you to draw down from a single capacity pool as you consume services across MuleSoft. Instead of managing different usage types for all products, you purchase a package of credits to use flexibly across the entire MuleSoft platform. As you use these capabilities, Anypoint Platform deducts the corresponding credit amounts from your available balance. -Credits are shared across your entire Anypoint Platform organization and cannot be managed per business group. Use Mule Credits before the Order End Date set in the Usage Details table on your Order Form — rollovers are not permitted. To see which usage types are included in your subscription, refer to your Order Form, Subscription Plan, or Features and Entitlement Document. +Mule Credits apply to your entire Anypoint Platform organization and you can't manage them per business group. Use Mule Credits before the Order End Date set in the Usage Details table on your Order Form — rollovers aren't permitted. To see which usage types your subscription includes, refer to your Order Form, Subscription Plan, or Features and Entitlement Document. == Mule Credits by Subscription Plan @@ -35,7 +35,7 @@ NOTE: MuleSoft All-Access License supports pre-commit and unlimited usage models == Usage Types -Each usage type (also referred to as a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the <<_rate_cards,Rate Cards>> section. +Each usage type (also called a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the <<_rate_cards,Rate Cards>> section. [%header%autowidth.spread] |=== @@ -46,40 +46,40 @@ Each usage type (also referred to as a meter) tracks a specific dimension of pla Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow might receive a record and transform data into a given format that another flow processes. -To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24 hour period starting at 00:00 UTC, a single hour with the highest flow count is identified as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine your final usage. +To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24 hour period starting at 00:00 UTC, MuleSoft identifies a single hour with the highest flow count as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine your final usage. | *MuleSoft Messages* -| The total volume of data containers processed by the runtime. To track message usage, the runtime report counts the number of times a Mule event source triggers a message. To calculate usage, MuleSoft aggregates the number of messages daily (UTC time) and monthly. After a message is triggered, the report doesn’t track changes to the message because the message is processed within the application’s flows. +| The total volume of data containers processed by the runtime. To track message usage, the runtime report counts the number of times a Mule event source triggers a message. To calculate usage, MuleSoft aggregates the number of messages daily (UTC time) and monthly. After a Mule event source triggers a message, the report doesn't track changes to the message because the application's flows process it internally. | *Managed Assets* -| An asset (API, Agent, MCP Server, or LLM) is considered managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Usage is counted per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. +| An asset (API, Agent, MCP Server, or LLM) counts as managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Anypoint Platform counts usage per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group don't incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. | *Gateway Requests* -| Any request received by https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Usage is measured as the sum of all processed requests, regardless of response status. +| Any request that https://docs.mulesoft.com/gateway/latest/[Omni Gateway^] receives. MuleSoft measures usage as the sum of all processed requests, regardless of response status. | *IDP Pages* -| The number of individual document pages processed by Intelligent Document Processing (IDP) in https://docs.mulesoft.com/idp/[MuleSoft IDP^] or https://blogs.mulesoft.com/news/mulesoft-for-flow-intelligent-document-processing/[MuleSoft for Flow: IDP^]. Each page within a document is counted as a separate unit, and only successful LLM responses are charged. +| The number of individual document pages that Intelligent Document Processing (IDP) processes in https://docs.mulesoft.com/idp/[MuleSoft IDP^] or https://blogs.mulesoft.com/news/mulesoft-for-flow-intelligent-document-processing/[MuleSoft for Flow: IDP^]. MuleSoft counts each page within a document as a separate unit, and charges only for successful LLM responses. | *Flow Integration Tasks* -| Individual units of work or actions (reading, creating, or updating a record) executed within https://www.mulesoft.com/platform/flow-integration[MuleSoft for Flow: Integration^]. +| Individual units of work or actions (reading, creating, or updating a record) executed within https://help.salesforce.com/s/articleView?id=platform.automate_flow_get_started_mfi.htm&type=5[MuleSoft for Flow: Integration^]. | *Private Spaces* -| A https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about[Private Space^] is a dedicated, isolated environment in CloudHub 2.0 for running your apps. Credits are consumed based on the total number of provisioned Private Spaces per day. After you deprovision a Private Space, it stops consuming credits from the next calendar date onwards. +| A https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about[Private Space^] is a dedicated, isolated environment in CloudHub 2.0 for running your apps. You consume credits based on the total number of provisioned Private Spaces per day. After you deprovision a Private Space, it stops consuming credits from the next calendar date onwards. | *Network Connections* -| Network connections allow you to securely connect corporate data centers and on-premises applications to CloudHub 1.0 and https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about#private-network[CloudHub 2.0^] using a VPN or AWS Transit Gateway. Credits are consumed based on the total number of active network connections per day. After you deprovision a network connection, it stops consuming credits from the next calendar date onwards. +| Network connections allow you to securely connect corporate data centers and on-premises applications to CloudHub 1.0 and https://docs.mulesoft.com/cloudhub-2/ch2-private-space-about#private-network[CloudHub 2.0^] using a VPN or AWS Transit Gateway. You consume credits based on the total number of active network connections per day. After you deprovision a network connection, it stops consuming credits from the next calendar date onwards. | *Load Balancers* -| https://docs.mulesoft.com/cloudhub/cloudhub-dedicated-load-balancer[Dedicated Load Balancers^] used to distribute incoming traffic across multiple workers or instances. Credits are consumed based on the total number of provisioned load balancers per day. After you deprovision a load balancer, it stops consuming credits from the next calendar date onwards. +| https://docs.mulesoft.com/cloudhub/cloudhub-dedicated-load-balancer[Dedicated Load Balancers^] used to distribute incoming traffic across multiple workers or instances. You consume credits based on the total number of provisioned load balancers per day. After you deprovision a load balancer, it stops consuming credits from the next calendar date onwards. |=== == Rate Cards You consume Mule Credits at the applicable multiplier rate based on the usage type identified in the https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule_Credit_Rate_Card.pdf[Mule Credit Rate Card^]. -Mule Credits must be used before the Order End Date set forth in the Usage Details table on the Order Form, and no rollover will be permitted. If your usage happens to exceed your contracted amount, MuleSoft automatically sends a monthly overage invoice to your primary billing contact at your standard contracted rate. Contact your account team with any questions about your contract or billing. +Use Mule Credits before the Order End Date set forth in the Usage Details table on the Order Form — MuleSoft doesn't permit rollovers. If your usage happens to exceed your contracted amount, MuleSoft automatically sends a monthly overage invoice to your primary billing contact at your standard contracted rate. Contact your account team with any questions about your contract or billing. == Viewing Usage and Billing From b92cc8dca9916a5a0d1e545e6379e88046150611 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:31:28 +0530 Subject: [PATCH 05/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 a2ac4c21a..3fc3d2514 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -1,4 +1,4 @@ -= Mule Credits Usage and Rates += Understand Mule Credits Usage and Rates A Mule Credit is a fungible currency that allows you to draw down from a single capacity pool as you consume services across MuleSoft. Instead of managing different usage types for all products, you purchase a package of credits to use flexibly across the entire MuleSoft platform. As you use these capabilities, Anypoint Platform deducts the corresponding credit amounts from your available balance. From bb9b8bfcea1bf183b98624cbdea43fcb8bd23030 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:32:22 +0530 Subject: [PATCH 06/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 3fc3d2514..6db2ac626 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -35,7 +35,7 @@ NOTE: MuleSoft All-Access License supports pre-commit and unlimited usage models == Usage Types -Each usage type (also called a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see the <<_rate_cards,Rate Cards>> section. +Each usage type (also called a meter) tracks a specific dimension of platform consumption. Credit rates vary by monthly consumption volume and reset on the first day of each calendar month. You consume credits at the same rate across all environments, including production, pre-production, sandbox, and design. For the full tiered rate table, see <<_rate_cards,Rate Cards>>. [%header%autowidth.spread] |=== From 889abd2b8074e8d608021f2f3dba00fa873c9d09 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:32:44 +0530 Subject: [PATCH 07/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 6db2ac626..6901aab5e 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -2,7 +2,7 @@ A Mule Credit is a fungible currency that allows you to draw down from a single capacity pool as you consume services across MuleSoft. Instead of managing different usage types for all products, you purchase a package of credits to use flexibly across the entire MuleSoft platform. As you use these capabilities, Anypoint Platform deducts the corresponding credit amounts from your available balance. -Mule Credits apply to your entire Anypoint Platform organization and you can't manage them per business group. Use Mule Credits before the Order End Date set in the Usage Details table on your Order Form — rollovers aren't permitted. To see which usage types your subscription includes, refer to your Order Form, Subscription Plan, or Features and Entitlement Document. +Mule Credits apply to your entire Anypoint Platform organization and you can't manage them per business group. Use Mule Credits before the `Order End Date` set in the *Usage Details* table on your *Order Form* because rollovers are not permitted. To see which usage types your subscription includes, refer to your *Order Form*, *Subscription Plan*, or *Features and Entitlement Document*. == Mule Credits by Subscription Plan From 10b35f20c80b278b93b9fb041d95f0be0c3474c4 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:33:02 +0530 Subject: [PATCH 08/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 6901aab5e..ce4d816f8 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -42,7 +42,7 @@ Each usage type (also called a meter) tracks a specific dimension of platform co | Usage Type | Description | *MuleSoft Flows* -| A flow is a sequence of logical operations configured within the XML `` element of a Mule application. The runtime report tracks the flows within a deployed and running Mule application that contains a Mule event source or APIkit route requests. +| A flow is a sequence of logical operations configured within the XML `` element of a Mule application. The runtime report tracks flows in deployed and running Mule applications that contain a Mule event source or APIkit route requests. Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow might receive a record and transform data into a given format that another flow processes. From 1157577ff580b6984be74dc8139f5b2a6ddb74e6 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:34:08 +0530 Subject: [PATCH 09/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 ce4d816f8..6f57b871f 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -44,7 +44,7 @@ Each usage type (also called a meter) tracks a specific dimension of platform co | *MuleSoft Flows* | A flow is a sequence of logical operations configured within the XML `` element of a Mule application. The runtime report tracks flows in deployed and running Mule applications that contain a Mule event source or APIkit route requests. -Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow might receive a record and transform data into a given format that another flow processes. +Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow can receive a record and transform data into a given format that another flow processes. To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24 hour period starting at 00:00 UTC, MuleSoft identifies a single hour with the highest flow count as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine your final usage. From 74a54e085b02a84978f88edd48768214dc3e92a4 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:36:15 +0530 Subject: [PATCH 10/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 6f57b871f..56f655713 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -46,7 +46,7 @@ Each usage type (also called a meter) tracks a specific dimension of platform co Mule apps in production environments typically use multiple flows and subflows to divide the app into functional modules or for error-handling purposes. For example, one flow can receive a record and transform data into a given format that another flow processes. -To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24 hour period starting at 00:00 UTC, MuleSoft identifies a single hour with the highest flow count as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine your final usage. +To calculate usage, MuleSoft tracks the number of flows across all business groups, environments, and applications on an hourly basis. For every 24-hour period starting at 00:00 UTC, MuleSoft identifies the hour with the highest flow count as the daily max flow. Based on your contract term, MuleSoft then aggregates these daily maximums over the month or year to determine final usage. | *MuleSoft Messages* | The total volume of data containers processed by the runtime. To track message usage, the runtime report counts the number of times a Mule event source triggers a message. To calculate usage, MuleSoft aggregates the number of messages daily (UTC time) and monthly. After a Mule event source triggers a message, the report doesn't track changes to the message because the application's flows process it internally. From 519d21b0aef42801c948056806ae56ab365178c8 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:36:26 +0530 Subject: [PATCH 11/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 56f655713..e828e075f 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -52,7 +52,7 @@ To calculate usage, MuleSoft tracks the number of flows across all business grou | The total volume of data containers processed by the runtime. To track message usage, the runtime report counts the number of times a Mule event source triggers a message. To calculate usage, MuleSoft aggregates the number of messages daily (UTC time) and monthly. After a Mule event source triggers a message, the report doesn't track changes to the message because the application's flows process it internally. | *Managed Assets* -| An asset (API, Agent, MCP Server, or LLM) counts as managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager^] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Anypoint Platform counts usage per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. +| An asset (API, Agent, MCP Server, or LLM) counts as managed if it has at least one active instance in https://docs.mulesoft.com/api-manager/latest/latest-overview-concept[API Manager] deployed to a https://docs.mulesoft.com/mule-gateway/mule-gateway-capabilities-mule4[Mule Gateway^] or https://docs.mulesoft.com/gateway/latest/[Omni Gateway^]. Anypoint Platform counts usage per business group per day; if an asset has active instances across multiple business groups, it counts as one asset per group. Multiple instances within the same business group don't incur extra charges. Anypoint Platform deducts credits as long as the asset status is Active in API Manager, even if there are no calls to the asset. From f117fa406a982f6127ec70a5b57f454d61e7d702 Mon Sep 17 00:00:00 2001 From: Kabilan-s-cx Date: Tue, 19 May 2026 18:36:45 +0530 Subject: [PATCH 12/12] Apply suggestion from @Crispy-Salesforce Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- 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 e828e075f..bdf6d6578 100644 --- a/modules/ROOT/pages/mule-credits-usage-and-rates.adoc +++ b/modules/ROOT/pages/mule-credits-usage-and-rates.adoc @@ -79,7 +79,7 @@ Multiple instances within the same business group don't incur extra charges. Any You consume Mule Credits at the applicable multiplier rate based on the usage type identified in the https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/mulesoft/Mule_Credit_Rate_Card.pdf[Mule Credit Rate Card^]. -Use Mule Credits before the Order End Date set forth in the Usage Details table on the Order Form — MuleSoft doesn't permit rollovers. If your usage happens to exceed your contracted amount, MuleSoft automatically sends a monthly overage invoice to your primary billing contact at your standard contracted rate. Contact your account team with any questions about your contract or billing. +If your usage exceeds your contracted amount, MuleSoft sends a monthly overage invoice to your primary billing contact at your standard contracted rate. Contact your account team with any questions about your contract or billing. == Viewing Usage and Billing