Allowances and usage
Your plan sets two kinds of limit. Monthly allowances count what you use in a calendar month. Caps count what you have at one time. Plans lists the numbers for Free and Pro.
| Kind | Covers | Resets |
|---|---|---|
| Monthly allowance | Runs, notification emails, AI on the platform’s key | The 1st of each month, in UTC |
| Cap at one time | Projects, agents, databases, active app subscriptions | Never. Deleting one frees room |
What counts
Section titled “What counts”Every run counts once, when it starts: a manual run, Run draft in the builder, a scheduled run, an app event run and an API run. The outcome does not matter, so a run that fails still counts. A run with agent steps counts as one run, and its AI is counted separately.
When Super Flows retries a scheduled run or an app event delivery on its own, the retry finds the run it already started and is not counted again.
Notification emails
Section titled “Notification emails”Each recipient of a Notification step’s email counts as one email. If sending to an address fails, that address is handed back to your allowance. Webhook notifications do not count, and neither do account emails such as invitations and approval requests.
AI on the platform’s key
Section titled “AI on the platform’s key”This is the estimated dollar cost, at list price, of model calls made on the platform’s Vercel AI Gateway key: agent steps, agent chats and the assistant’s turns. Calls made on your organization’s own key count against nothing.
Agents on Workers AI run on the platform’s account. Their usage is not counted here, but they run only while there is allowance or credit left, so they are refused on Free and once the month’s AI is spent on Pro.
Super Flows may grant a paid organization AI credit on top of its allowance. Credit is spent once the month’s allowance is used, and what is left carries over to later months until it is spent.
Active app subscriptions
Section titled “Active app subscriptions”An App event trigger in a published, unpaused workflow listens through an app subscription. Triggers with the same connection, event and filter share one subscription, which counts once. Pausing the workflow, or setting the trigger to Disabled and publishing again, frees its subscription.
What happens at a limit
Section titled “What happens at a limit”Nothing you have is deleted. What stops is the next thing that would go over.
| Limit reached | What happens |
|---|---|
| Runs, started by a member or the API | The run does not start. The API answers 402 plan_limit_reached |
| Runs, on a schedule | That occurrence is skipped. The schedule stays on and tries again at its next time |
| Runs, from an app event | No run starts. Run history lists the event with the outcome “limit reached” |
| Notification emails | The Notification step fails, and the run stops there |
| AI on the platform’s key | The agent step fails or the chat turn is refused, with a message pointing to Settings. Workers AI agents stop too |
| Projects, agents, databases | Creating another one is refused |
| Active app subscriptions | Publishing or resuming a workflow that would add one is refused, before anything is subscribed |
The message names the limit. For example, at the runs limit on Free it reads “The Free plan includes 500 runs a month. Upgrade to add more.”
To get past a monthly allowance, wait for the 1st or upgrade. For AI on Pro, you can also add your organization’s own key in Settings, which agents then use instead. To get past a cap, delete something you no longer need or upgrade.
Where to see usage
Section titled “Where to see usage”- Billing. The This month card shows runs, notification emails and AI on our key against your plan, and the credit left when you have any. The Active app subscriptions card shows how many your live triggers use.
- Dashboard. The This month section shows how much of each allowance is left.
- The API.
GET /api/v1/billingreturns your plan, its limits and this month’s usage. See the API reference.
A meter turns red when its allowance is used up.