Rate Limits

If you require higher limits, please contact us at support@caesar.xyz.

Scope: These limits apply only to POST /research (create research). Other endpoints are not rate-limited under this policy.

The Caesar API has the following limits during the beta period:

  • Concurrent research jobs: 5 per account (in-progress jobs, including queued).
  • Monthly compute budget: 200 compute units, counted only for successful research jobs.

Exceeding limits

When a limit is exceeded the API returns 429 Too Many Requests:

1{ "error": "Too many requests — rate limit exceeded." }

Recommended client behaviour

  • Retry with exponential back-off.
  • Serialise new jobs when you’re at the concurrency cap.
  • Use compute_units thoughtfully to stay within your monthly budget.

A compute unit represents the effort allocated to a research job. Your monthly usage is the sum of the compute_units for jobs that reach the completed status.

Any job that is not yet completed or failed (e.g. queued, searching, summarising, analysing) counts towards your concurrency limit.

Limits reset on a monthly cadence; your dashboard shows your remaining balance and the next reset window.

Yes. Email support@caesar.xyz with your expected volumes and use case.

Visit ask.caesar.xyz/app/api-keys after signing in.