Docs menu · Plans and limits

Plans and limits

The 14-day Shadow trial, what Developer and Team include, how agents and decisions are counted, and API rate limits.

Updated

The 14-day trial

Every workspace starts with a free Shadow Mode trial — no card. The 14 days start with your agents’ first real decision, not at sign-up, so a slow integration doesn’t cost you days. The trial includes up to 5,000 purpose evaluations and the Developer quotas.

When it ends, nothing breaks: agents keep being decided against your rules, and every spend is still recorded. Purpose is no longer assessed, and the report says so. Enforce needs a plan.

Plans

TrialDeveloperTeam
Pricefree, 14 days$49 / month$199 / month
Agents3325
Decisions / month5,0005,00050,000
Shadow Mode✓✓✓
Enforce—✓✓
Purpose-aware authority, MCP + SDK, human review, audit trail✓✓✓
Webhooks, priority support✓

How usage is counted

  • Agents: every agent that isn’t revoked. Paused agents count; revoked ones don’t.
  • Decisions: per calendar month (UTC). Idempotent retries return the original decision and aren’t counted twice. Console test decisions aren’t counted.
  • Console → Plan & usage shows both, with the trial’s days and purpose evaluations left.

Going over

  • Agents are a hard limit: creating one more answers 409 agent_limit. Revoke an agent or move to a larger plan.
  • Decisions are never refused. A limit that stopped decisions would either break your agents or let spends through unchecked, so going over is shown in the console, not enforced — and we’ll talk about the right plan.

Upgrading and billing

Console → Plan & usage → Upgrade. Payments are handled by Polar, our merchant of record, which also sends your invoices. The plan applies as soon as the payment confirms. Manage billing opens the customer portal: change plan or card, download invoices, or cancel — a cancelled plan runs to the end of the period, then the workspace returns to Shadow.

Rate limits

600 requests a minute per key, on every plan. Over it, 429 rate_limited with Retry-After; the SDK retries and never treats a 429 as permission to spend. See the API reference.