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. ## Web Search Your subscription tier sets the Web Search QPS (Queries Per Second) limit: | Subscription | QPS Limit | | :- | :- | | Free | 10 | | Base | 20 | | Builder | 50 | | Pro | 200 | | Max | 500 | ## Other Search APIs & Answer Broad Search, News Search, Business Search, Image Search, Video Search, and Answer share one QPS limit: 10 on the Free plan, 20 on every other tier. Answer is also subject to the Model Gateway RPM and TPM limits. ## 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. ## Embedding & VL Embedding The **Embedding** and **VL Embedding** APIs are limited by tokens per minute (TPM), applied per account by subscription tier: | Subscription | Embedding TPM | VL Embedding TPM | | :- | :- | :- | | Free / Base | 1,000,000 | 200,000 | | Builder | 2,500,000 | 500,000 | | Pro | 10,000,000 | 2,000,000 | | Max | 25,000,000 | 5,000,000 | ## Extract The **Extract API** is limited by URLs per minute, based on the mode in the request: | Mode | URLs / min | | :- | :- | | `standard` | 2,000 | | `auto` | 500 | | `advanced` | 200 | ## Model Gateway The **Model Gateway API** is rate limited by requests per minute (RPM) and tokens per minute (TPM). Each model's usage is counted separately: | Metric | Limit | | :- | :- | | RPM | 300 | | TPM | 2,000,000 | ## Deep Research Only a single concurrent request is supported. ## Grounded Generation Up to 3 concurrent requests are 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` ## Recommended Retry Behavior 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](mailto:support@octen.ai) ***Last modified on October 14, 2026
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.