For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a product
    • Setting up a chat surface
    • Setting up an API surface
    • Setting up an MCP surface
    • Setting up an A2A surface
    • Setting up a Slack surface
    • Setting up a webhook surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to MCP clients
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and editing flows
    • Flow step types overview
    • Agent and flow templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
    • Braintrust (tracing)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Managing secrets
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate limits and usage
    • Managing Runtype with Claude
    • Agent skills
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Tier Limits
  • How It Works
  • Monitoring Usage
Dashboard

Daily Executions

Was this page helpful?
Previous

What is the Playground?

Next
Built with

A Daily Execution is a single Flow run that counts against your usage quota. Every time you trigger a Flow or Agent—via /api/dispatch, batch, Product API, scheduled run, or the SDK—it counts as one execution.

Tier Limits

TierPoolWhat Happens at Limit
Build/Trial50/dayEnters “slow mode” (10s delay, max 10/hr)
Startup15k/monthSoft cap — continues but tracks overage for billing
Growth60k/monthSoft cap — continues but tracks overage for billing
Team300k/monthSoft cap — continues but tracks overage for billing
EnterpriseUnlimitedNo limits

How It Works

Build tier gets 50 free executions per day, resetting at midnight UTC. After 50, requests continue with a 10-second delay and a cap of 10 per hour (“slow mode”). Exceeding the hourly cap returns HTTP 429.

Paid tiers use a monthly pool. Executions are never blocked — overages are tracked and billed (e.g., 5/1kforStartup,5/1k for Startup, 5/1kforStartup,4/1k for Growth, $3/1k for Team). See billing and plans for details.

Monitoring Usage

The header badge shows your current usage (e.g., “5/50 today”). Click it to see:

  • Progress bar showing usage percentage
  • Used vs. limit counts
  • Countdown to next reset
  • Upgrade button

Badge colors change as you approach limits: gray when normal, amber at 90%+, orange in slow mode, and purple when in overage on paid plans.

For detailed usage analytics, see usage data. To review execution details, check execution logs.

Executions reset daily at midnight UTC for Build tier, and monthly for paid tiers.