Skip to main content

For AI agents: docs.octen.ai/resources/rate-limits.md

Octen enforces rate limits to ensure platform stability and fair usage across all customers. Rate limits define how frequently you can call the API within a given time window. Requests that exceed these limits will be temporarily rejected.

​
Broad Search, Web Search, Embedding & VL Embedding

The following QPS (Queries Per Second) limits are shared across the Broad Search, Web Search, Embedding & VL Embedding:

​
How rate limits are applied

Rate limits are determined by your account plan and optional per-key caps:
  • Each account has a default rate limit based on its subscription tier.
  • When creating an API key, you may configure an additional rate limit for that key.
  • If both are configured, requests are throttled by whichever limit is lower.

​
Extract

The Extract API uses a rate limiting model based on requests per minute (RPM):

​
Model

The Model APIs are rate limited by requests per minute (RPM) and tokens per minute (TPM). Each model’s usage is counted separately:

​
Deep Research

Only a single concurrent request is supported.

​
What happens when you exceed a limit

If a request exceeds the allowed rate:
  • The request is rejected with a rate limit error.
  • HTTP status: 429
When receiving a rate limit error:
  • Check the msg for detail.
  • Avoid immediate retries in a tight loop.
  • Resume requests after the rate limit window resets.
  • For high-throughput or bursty workloads, batching requests where supported can help reduce pressure on rate limits.

​
Increasing rate limits

If your application requires higher throughput or sustained traffic:
  • Custom limits or enterprise plans may be available.
  • Contact the Octen team to discuss your use case.
  • Support: support@octen.ai