> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt. # Manage your team's Postman Flows credit usage Postman provides tools to help you manage your team's usage of credits in Postman Flows. Flows pricing is based on consumption, with each Postman plan including a monthly allocation of credits. Eligible plans can enable pay-as-you-go to continue usage beyond their included credits. You can use the [Resource usage dashboard](http://go.postman.co/billing/add-ons/overview) to track credit consumption and manage billing settings. ## Flows access and included credits All plans include a baseline number of Flows credits each month so you can explore and use Flows. | Feature | Free | Solo | Team | Enterprise | | --------------------------- | ---- | --------- | --------- | ---------- | | Flows complimentary credits | 25 | 50 | 100 | 500 | | Pay-as-you-go Flows credits | No | Yes | Yes | Yes | | Pay-as-you-go AI credits | No | Yes | Yes | Yes | | RBAC | No | No | Yes | Yes | | Private Flow runner | No | No | No | Yes | | Snapshots per flow | 10 | Unlimited | Unlimited | Unlimited | Credits are allocated monthly per team and don't roll over. ## View flows usage To check your team’s current credit usage, click your avatar on the top right and select **Billing & resource usage**, then click **Resource usage** to open the [Resource usage dashboard](http://go.postman.co/billing/add-ons/overview). When your team reaches its monthly credit limit: * Flows that are currently running complete. * New runs that require credits are paused. * You can enable pay-as-you-go (if available on your plan) to continue usage. ## How Flows consume credits Credits are deducted when Flows run, based on the blocks used and where they execute. Only blocks listed in the following pricing table consume credits. There are two types of runs: * **Manual runs** (clicking **Run** in the app) only consume credits for blocks that run in the cloud, such as AI and connector blocks. However, if you have **Cloud Run** enabled when you test a flow on your local canvas, it runs in the cloud and consumes credits. Local canvas * **Automated runs** (triggered using API or MCP) consume credits for HTTP requests and logic blocks, in addition to AI and connector blocks. This usage-based model supports everything from basic API calls to complex AI-powered workflows. ## Premium block pricing ### Post-March 1, 2026 | Block type | Local canvas | Cloud / cloud canvas | | ----------------------- | ------------ | -------------------- | | HTTP Request | 0 | 1 | | AI Request | 0 + BYOK | 1 + BYOK | | Evaluate | 0 | 1 | | Evaluate with Packages | 0 | 2 | | If | 0 | 1 | | Condition | 0 | 1 | | Validate | 0 | 1 | | Integration (Connector) | 2 | 2 | Premium blocks are blocks that execute code or perform external operations. ## AI Agent models and tools The **AI Agent** block consumes credits based on the models and tools used during a block run. **AI Agent** credits are consumed for both local and cloud runs. | AI Agent models + tools | Credits per run (all run types) | | ----------------------------------- | ------------------------------- | | External MCP tool (per unique tool) | 2 | | Internal (Flows-hosted) MCP servers | Free | | GPT-5 | 10 | | GPT-5 mini | 2 | | GPT-5 nano | 1 | | GPT-4 | 25 | | GPT-4o | 15 | | GPT-4o mini | 2 | | Sonnet 4.5 | 10 | | Haiku 4.5 | 2 | | Sonnet 4 | 5 | External MCP tool charges are per unique tool invoked during a block run, not per tool call or per tool attached. For example, calling the same tool 100 times costs two credits, while calling three different tools once each costs six credits. The number of credits consumed by AI models is subject to change. ## AI media models AI media generation is billed based on the model used. AI media model usage is passed through at cost. | Model | Quality | Credits per run | | ---------------- | ------- | --------------- | | GPT-image-1.5 | Medium | 50 | | GPT-image-1 | Medium | 65 | | GPT-image-1-mini | Medium | 15 | ## Pay-as-you-go credits If your plan supports it, you can enable pay-as-you-go to continue using Flows after your included credits are exhausted. * Additional credits are billed at **\$1 per 1,000 credits** * Credits are billed based on actual usage * Monthly included credits don't roll over. Enterprise teams can purchase additional credits or discuss custom usage with their account team. Enterprise teams who purchase additional credits can also enable pay-as-you-go (PAYG) to run beyond those additional credits. PAYG credits stack on top of the extra purchased credits rather than replacing them, so usage isn't hard-capped at the extra purchased amount. The overage rate follows the Enterprise PAYG rate (\$10 per 10,000 credits). Enterprise teams can coordinate with their account teams on sizing. Pay-as-you-go is turned off by default. To activate it, click your avatar on the top right and select **Billing & resource usage**. Click **Resource usage** to open the [Resource usage dashboard](http://go.postman.co/billing/add-ons/overview) and turn on **Pay-as-you-go** under **Flows Credits**. ## Private Flow runner Private Flow runner is available only on Enterprise plans. | Team type | Access | | ----------------------- | ------ | | Free | No | | Solo | No | | Team | No | | Self-serve Enterprise | Yes | | Sales-served Enterprise | Yes |