> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.runtype.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.runtype.com/_mcp/server.

# Daily executions

Each Flow or Agent run counts as one execution. You can start runs in several ways, for example with the [dispatch endpoint](/api-reference/runtype-api/dispatch/execute-a-flow-or-agent) (`POST /v1/dispatch`), [batch processing](/user-guide/flows/running-flows-in-batch), the [Product API](/user-guide/products-surfaces/calling-your-api-endpoints), [Schedules](/user-guide/schedules/what-are-schedules), or an SDK.

## Execution counts are a measure, not a quota

Runtype doesn't limit how many executions your account runs per day, with or without a payment method on file. Runtype bills the AI model calls and built-in tools that your executions use from prepaid credit. Auto-topup replenishes credit according to your billing settings.

These limits can still stop or refuse a run:

* A burst rate on some plans, which limits how many executions start in a 10-second window and returns `429`.
* The hourly batch limit of 250,000 records per user, which returns `429` when a batch submission exceeds it.
* Your spend cap or exhausted credit.
* A cap on a test credential. A [Test API key](/user-guide/settings/managing-api-keys) (`rt_test_`) allows 200 executions in total. Its daily cap of 20 counts every execution your account runs that day, from any source, so a Test key returns `429` after your account reaches 20 executions that day, even if the Test key started none of them. A [surface test API key](/user-guide/products-surfaces/setting-up-an-api-surface) allows 50 executions per day. Daily caps reset at midnight UTC.
* The per-minute and per-hour rate limits on a [client token](/user-guide/products-surfaces/client-tokens-and-domain-restrictions).

## Monitoring usage

The **Activity** chart on Dashboard home shows how many runs started in each 24-hour interval. To change the period, choose **Last 7 days**, **Last 30 days**, or **Last 90 days** next to **Across your workspace** on Dashboard home. Select the refresh button beside the period to update the counts. The **Updated** time shows when the numbers were taken, and **Showing saved data** appears when a refresh fails.

The chart counts top-level runs. Work that a run starts is counted once with that run, and runs that are still in progress are included. Each point covers 24 hours, counted from the start of the selected period, and the tooltip shows its start time in UTC.

Use the controls on the **Activity** card:

* Select **Total**, **Agents**, or **Flows** to change which runs the chart counts.
* Select a chart point to open the logs for that interval.
* Expand **View daily counts** to see a table of the intervals. Select a date to open its logs.
* Select **Explore runs** to open the logs for the whole period and the selected run type.

**Total** can include older runs that aren't labeled as an agent or a flow. When it does, the card footer shows how many of these runs are included in **Total** only, so **Agents** plus **Flows** can be lower than **Total**.

For spend by model and tool, click **Settings > Usage**. For more information, see [Usage data](/user-guide/settings/usage-data). To review individual runs, use the **Logs** page.

## Next steps

Continue with these pages:

* [What is the Dashboard?](/user-guide/dashboard/what-is-the-dashboard): Read the production health metrics that share the same time range.
* [Usage data](/user-guide/settings/usage-data): Review spend by model and tool.
* [Billing and plans](/user-guide/settings/billing-and-plans): Manage credit, auto-topup, and your spend cap.
* [Rate limits and usage](/user-guide/troubleshooting-faq/rate-limits-and-usage): Find the causes of `429` and `402` responses.
* [Working with Logs](/user-guide/logs/working-with-logs): Inspect individual executions.