Limits

At a glance

• Plan quotas (runs / AI actions / tool limits) vary by plan.
• Daily quota window resets at 00:00 UTC.
• Rate limiting returns HTTP 429 with error "rate_limited".
• Public runs consume the tool owner's quotas.
• LLM tools require BYOK (owner AI key). If missing, "byok_required" must be side-effect-free.

Quotas (runs / AI actions / tool caps)

Quotas are enforced per owner and plan. Exact numbers depend on your plan.

# Key concepts (high-level)
- Runs: counted when /run succeeds.
- AI actions: only relevant for LLM-required tools.
- LIVE tools cap: limits how many tools can be LIVE/production.
- Public runs: use owner's quotas.

Rate limiting

Rate limits protect the platform from bursts. When hit, the API returns HTTP 429 with a structured rate_limited error.

# Rate limiting (example)
- Too many runs in a short window => HTTP 429
- Response includes error: "rate_limited"
- Best practice: exponential backoff (e.g. 250ms, 500ms, 1s, 2s ...)

Quota windows & reset times

Daily windows reset at 00:00 UTC. Other windows follow your plan/billing period.

# Quota windows
- Daily window resets at 00:00 UTC.
- Other quota windows depend on plan/billing period.

BYOK for LLM tools

If a tool requires an LLM step, the owner must configure an AI key. Otherwise runs must be blocked with byok_required.

# BYOK (LLM tools)
If a tool requires an LLM step but the owner has no active AI key:
- Error: "byok_required"
- Must be side-effect-free:
  - no tool_runs log
  - no quota charge
  - no embed token touch

TRIAL notes

The TRIAL plan is intentionally restricted to keep abuse low and encourage a quick upgrade when needed.

# Trial notes
- TRIAL plan has restricted features.
- Example: Data tables are not available on TRIAL.