Plans & limits

Your plan sets three things: how many searches you can run per hour, how many watch rules you can keep, and how many webhook deliveries you get per day. The numbers below are CT Watch’s defaults — a deployment can tune them.

The quotas

| | Anonymous | Free | Pro | |---|---|---|---| | Searches / hour | 5 (per IP) | 20 | 100 | | Watch rules | — | 10 | 1,000 | | Webhook deliveries / day | — | 100 | 10,000 |

Anonymous is search-only — no account, capped per source IP. Sign in (free) to raise the search rate and unlock watch rules and webhooks. See live numbers for your account on the dashboard’s Usage tab, and the plan comparison on pricing.

403 — you hit a cap

A 403 Forbidden on a mutation means you’ve hit a count limit — most often the watch-rule cap for your plan. Remove a rule or upgrade. Caps are checked at create time, so existing data is never affected.

429 — you hit a rate

A 429 Too Many Requests means you’ve exceeded your searches / hour — counted per account when you’re signed in, or per source IP when you’re not. Back off and retry; the limit is a fixed window, so it clears on its own shortly.

Signing in raises the search rate (5 → 20 / hour, or 100 on Pro) and attributes usage to your account instead of your IP, which is the main reason to authenticate even for read-only search.

Deliveries

Webhook deliveries count against your daily quota as they’re sent. Retries of a single match don’t multiply the count — a match is one delivery to each target. When you’re over the daily cap, new matches stop delivering until the counter resets; the matches themselves are still archived and searchable.

Raising limits

Pro raises the rule and delivery caps. Self-serve checkout isn’t wired yet, so Pro access is arranged by hand for now — see pricing.