---
schema_version: "1"
id: b0d4964ffd306882e99f7a4d54a27544bd329f3ba3146fb0dab68c197aaf796c
title: Track the Number of Billable Flows in Anypoint Studio
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/flow-counting-studio.md
canonical_url: https://docs.mulesoft.com/studio/flow-counting-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 203e61ac07c66e0adf313e4cef338850d0e88bad7789dfff7c16d74bfd392cf3
description: MuleSoft Documentation Site
latest: true
---
---
product: Studio
---

# Track the Number of Billable Flows in Anypoint Studio

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

In Anypoint Studio 7.20 and later, you can track the number of billable flows in your project.

Flow Counting improves transparency in usage-based pricing by providing visibility into the number
of billable flows when developing your project. With this new feature, you better understand your
consumption patterns from design to deployment, preventing unexpected billing issues.

Your Anypoint Platform organization pays for billable flows, such as Trigger Flows or
APIkit-generated flows, in deployed Mule applications in your runtime plane. A flow is billable when
it contains a Mule event source or routes APIkit requests. To reduce these costs, consider using
subflows or private flows, which aren’t billable. Additionally, to bypass charges for unused flows,
avoid deploying unnecessary flows from accelerators or assets. See
[Anypoint Platform Pricing](https://docs.mulesoft.com/general/pricing) for information about managing and reducing billable
flows.

<table><colgroup><col> <col></colgroup><thead><tr><th>Type of Flow</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>Trigger Flows</p></div></div></td><td><div><div><p>Begins the execution of a process based on certain events or conditions. These flows are the starting point of any integration application. A trigger flow usually starts with a message source, like a listener or a scheduler. The message source reacts to external events (like HTTP requests, time schedules, or file updates) and starts the next process.</p></div></div></td></tr><tr><td><div><div><p>APIkit-generated Flows</p></div></div></td><td><div><div><p>Flow automatically created by the APIkit module if you import or design an API spec. These flows map incoming API requests to the appropriate logic and responses. Each action in the API spec results in a flow.</p></div></div></td></tr></tbody></table>

## Count the Flows in Your Project Using Studio

1.  Select your project.

2.  Click **Flow Count** (![2%](/mulesoft/current/en-us/studio/_images/flow-count-icon.png)) in the taskbar.

    Studio displays the number of billable flows your Anypoint Platform organization is charged for
    in deployed Mule applications.

    ![A table showing the billable flow names and type](/mulesoft/current/en-us/studio/_images/flow-count.png)

3.  Click **OK** to close the window.

## See Also

- [Usage-Based Pricing: Usage and Rates](https://docs.mulesoft.com/general/usage-metrics)
Type of Flow	Description
Trigger Flows	Begins the execution of a process based on certain events or conditions. These flows are the starting point of any integration application. A trigger flow usually starts with a message source, like a listener or a scheduler. The message source reacts to external events (like HTTP requests, time schedules, or file updates) and starts the next process.
APIkit-generated Flows	Flow automatically created by the APIkit module if you import or design an API spec. These flows map incoming API requests to the appropriate logic and responses. Each action in the API spec results in a flow.