Skip to main content
Mirobody counts requests per account × path × minute. On overflow you get HTTP 429 with a Retry-After header (seconds). 
HTTP/1.1 429 Too Many Requests
Retry-After: 47
PathSuggested RPMNotes
POST /v1/chat/completions≤ 60Streaming calls count too; wait for one to finish before the next
POST /v1/files≤ 30Batch where possible; OCR is compute-heavy
POST /v1/data≤ 120Batch records into one request (up to 1000/batch)
GET reads (/v1/data, /v1/files, /v1/models)≤ 120—
Exact thresholds are injected per deployment. Email Mirobody Support to confirm the limits for your account before going live.

​
Client backoff

  • On 429, respect Retry-After — never retry immediately.
  • Double the backoff after two consecutive 429s, up to 5 minutes.
  • Don’t fire chat calls in parallel; let each stream complete first.