Daily executions

Each Flow or Agent run counts as one daily execution. Start a Flow or Agent with /api/dispatch, batch processing, the Product API, Schedules, or an SDK. The daily count resets at midnight UTC.

Execution counts are a measure, not a quota

No plan limits how many executions you can run, and your billing state does not limit the count. Runtype bills AI model calls and built-in tools used by your executions from prepaid credit. Auto-topup replenishes credit according to your billing settings.

There is no daily execution ceiling on any account, with or without a payment method on file. Execution count does not cause a 429 response. A per-second rate limit, your spend cap, or exhausted credit can pause executions.

Monitoring usage

Dashboard home shows root runs over the selected 7, 30, or 90 day window. Its Activity chart uses 24-hour intervals anchored to the start of that rolling window; these differ from the midnight UTC daily usage count. Total includes agents, flows, and historical runs whose type is unknown. Nested work is counted once with its parent. The counts include unfinished runs, while success rate uses finished runs only.

Select Total, Agents, or Flows to change the chart. Select a chart point or a date under View daily counts to open logs for that interval. Explore runs preserves the selected window and run type.

Use the Usage page for detailed usage analytics. Use the Logs page to review execution details.

Next steps

Continue with these pages:

• Usage data: Review spend by model and tool.
• Billing and plans: Manage credit, auto-topup, and your spend cap.
• Rate limits and usage: Find the causes of 429 and 402 responses.
• Working with Logs: Inspect individual executions.