I hit a rate limit
Common limits: 1 audit/hour per brand, per-user concurrency on scans.
Last updated: 2026-05-05
Where rate limits apply
Rate limits exist to keep the platform fast and fair for everyone. The most common ones:
| Action | Limit | Why |
|---|---|---|
| AI Search Audit | 1 run per brand per hour | Crawls + AI analysis are heavy; this prevents accidental loops |
| AI Scans | Per-user concurrency cap (rolling) | Protects edge function timeouts and provider quotas |
| Email verification | 5 sends per hour per user | Anti-abuse |
| Password reset | A few per hour per email | Anti-abuse |
| Copilot tools | Same limits as the underlying tool | Tools route through the queue |
The UI always shows the next allowed time when you hit a limit, so you don't have to guess.
"AI Search Audit limit reached"
The Audit fetches dozens of pages, runs them through multiple AI passes, and computes scores across three pillars. We cap it at 1 per brand per hour so a single user can't burn through credits or saturate the crawler.
- Wait the time shown on the button.
- Or audit a different brand in the meantime.
"Too many concurrent scans"
We throttle how many scans a single user can run in parallel to prevent edge timeouts. Queued scans are not lost — they execute as soon as a slot frees up. Just leave the Results page open or check back in a minute.
"Verification email rate limit"
You can request a maximum of 5 verification emails per hour. If you hit the limit, sign in with Google instead, or wait an hour.
Provider rate limits
Occasionally a specific AI provider rate-limits us. When that happens:
- The affected model is auto-disabled for a short window.
- Other models in your scan keep working.
- Once health checks pass, the model auto-re-enables — no action needed.
If you frequently hit limits and need higher caps for a legitimate use case, email contact@pranas.co.