Rate limits & plans

• Per-minute rate limit — sliding window, counted per API key
• Monthly request cap — counted per org, resets on the 1st of each calendar month (UTC)

​

Plan matrix

​

When you hit the limit

{
  "detail": {
    "error": "rate_limit_exceeded",
    "limit_per_minute": 60,
    "plan": "starter"
  }
}

{
  "detail": {
    "error": "monthly_cap_reached",
    "used": 500,
    "cap": 500,
    "plan": "starter",
    "upgrade_url": "https://medlistiq.com/dashboard/billing"
  }
}

​

How enforcement works

• Rate limit is enforced per container (we run on Cloud Run). The effective global limit is your plan limit × number of concurrent containers. For stricter guarantees reach out — we can move to a Redis-backed limiter.
• Monthly cap is enforced per org and cached 60s. You may slightly overshoot during that cache window, but only by a handful of requests. We honor the cap strictly once the cache refreshes.
• Only 2xx responses count against your cap. Failed auth, rate-limit rejects, and validation errors don’t consume quota.
• Demo/anonymous requests don’t count (when key auth is disabled in dev — not applicable to production).

​

Monitoring your usage

• Portal dashboard — real-time “X of Y used this month” progress bar at Dashboard → Usage
• Programmatic — drop us a note if you need an API for usage reporting; not built yet, prioritized by demand.

​

Monthly reset