J
Julien
Hi there,
I’m on the You.com Pro plan and sometimes hit “quota exceeded” errors without any way to know which limit I supposedly crossed. Maybe am i wrong but it seems that there is no public documentation of:
• the exact number of requests allowed per minute / hour / day;
• how these quotas differ by model or by agent;
• what the UI does when a threshold is reached (soft warning vs. hard block).
Because of this opacity it’s impossible to tell whether an error is legitimate, a bug, or an accidental abuse, and it prevents us from integrating You.com reliably into production workflows.
Impact
• Production jobs can stop unexpectedly.
• We purposely under-use the service for fear of being blocked.
• Not in my case but: finance / IT of a company could not budget or approve the tool without hard numbers.
Here are some of my suggestions:
  1. Publish a table of soft & hard limits per plan, per model, per time window.
  2. Eventually return clear 429 errors with JSON details, e.g.
```json
{ "error": "quota_exceeded",
"quota": "requests_per_minute",
"limit": 120,
"retry_after": 47 }
```
  1. Add a real-time usage dashboard showing “XX / YY requests” and 70 % / 90 % warnings.
  2. Offer e-mail or webhook alerts when usage crosses configurable thresholds.
  3. Provide controlled over-quota “burst” credits or pay-as-you fallback to avoid hard stop.
  4. Expose downloadable error / usage logs for auditing and debugging.
  5. Not in my use case but eventually: allow sub-quotas per API key so a test project can’t drain the whole company allocation.
(Obvious) benefits:
• Predictable capacity and cost planning.
• Fewer support tickets about unexplained blocks.
• Easier enterprise adoption thanks to transparent metrics.
• Stronger trust in You.com as a professional platform.