Settings

Usage data

Use Usage to review Flow executions, AI token usage, and Runtype-billed costs.

View usage data

To review usage analytics, follow these steps:

  1. In the sidebar, click Settings > Usage. The page opens with Billing month selected.
  2. To change the reporting period, select 7d, 30d, or 90d in Period.
  3. To request updated aggregate data, click Refresh usage analytics.
  4. To download the report, click Export CSV. The CSV file contains data for the selected period.

The page refreshes automatically every 60 seconds. The Usage page includes only activity billed by Runtype. Charges from your own API keys do not appear in this report.

Understand usage metrics

When the selected period contains usage, the Usage page starts with summary tiles. It shows Runtype-billed usage, Executions, and Average cost per execution. When cache activity exists, it also shows Estimated cache savings and cache hit rate. If no usage data exists, the page shows an empty state.

When usage data exists, the page shows the following charts and tables:

  • Usage cost over time: Shows daily Runtype-billed cost.
  • Executions over time: Shows execution volume by day.
  • Usage cost by category: Splits cost between AI models and built-in tools.
  • Cost by AI model: Lists models from highest cost to lowest with request count, token count, cost, and cost per request. It also shows cached input share when available.
  • Cost by built-in tool: Lists requests and cost for each built-in tool.
  • Prompt cache: Shows cache read and write token totals. The page displays this card only when the selected period contains cache activity. For more information, see Prompt caching.

The totals, charts, breakdowns, and CSV export use the selected period.

For this report, an execution is one Flow run, batch record run, Eval run, or scheduled trigger. One execution can make multiple model or tool requests.

When data loads, the page displays when the report was last updated. If the selected period starts before the available history, the page warns that earlier dates might be unavailable. Treat missing coverage as unknown, not as zero usage.

Use Settings > Billing to review the amount toward your monthly cap. Billing can be ahead of Usage while recent activity is still appearing on the Usage page. Reaching the cap pauses new executions. Your issued invoice shows the amount charged to your card.

Investigate contributing executions

Click Runtype-billed usage, Executions, or a model or tool name to open the executions behind that selection. In end-user reporting, click a user’s spend or execution count. The investigation keeps the selected dates and filters.

Choose an execution to open its exact trace. Select a trace event to inspect its details and use Add to eval to turn a useful example into a regression case.

The execution list uses unsampled recorded usage retained for 93 days. Its coverage summary shows when collection began and how much usage has no execution ID. Earlier history cannot be reconstructed; an empty list does not mean there was no usage. The sampled overview can differ from the retained event list. Runtype spend also includes pricing adjustments, so it is not the same measure as trace model-cost estimates. Native traces with missing completion metrics show partial totals rather than adding overlapping model, turn, and execution events together.

Reduce usage costs

Use lower-cost models

For routine tasks, choose a lower-cost model such as gpt-5.4-nano instead of gpt-5.4.

Set a lower output limit

Set a lower maxTokens limit when a shorter response is enough. This caps the output-token budget.

Store reusable API results

Store reusable API results in Records so later runs can avoid duplicate API calls.

Process records in batches

Process multiple records in a batch to reuse shared setup and reduce repeated overhead.

Optimize prompts

Remove unnecessary prompt content to reduce input tokens and input cost.

Understand bring your own key (BYOK) charges

With BYOK, follow these billing guidelines:

  • The Usage page excludes charges from your own API keys.
  • Your providers bill you directly for model costs.
  • Check each provider’s billing dashboard for exact charges.
  • Treat Runtype cost estimates as planning data, not invoices.

Next steps