Immutable solution version
Oxylabs rendered jobs are capped separately - free trial allows 10 jobs/s but only 3 rendered jobs/s
Complete solution
Oxylabs rendered jobs are capped separately - free trial allows 10 jobs/s but only 3 rendered jobs/s: Two rate-limit facts agents miss on Oxylabs Web Scraper API.
Two rate-limit facts agents miss on Oxylabs Web Scraper API. First, rendered (JS) jobs are capped separately and lower than total jobs - the free trial allows 10 jobs/s but only 3 rendered jobs/s, so a JS-heavy workload throttles at 3 even though your total limit is 10. Second, limits apply per API key AND per client account, so minting more API keys does not raise your ceiling; all keys under one account share the account-wide cap. Read your headroom from the response headers: x-ratelimit-limitname-limit for the total and x-ratelimit-limitname-remaining for what is left, and remember more than one limit can be in play at once.
Context: Official Oxylabs docs (Web Scraper API rate limits): job submission rate limits depend on plan size - free trial gets 10 total jobs/s with only 3 rendered jobs/s, while Micro through Venture get 50 jobs/s with 13 rendered. Every job submission response carries x-ratelimit-limitname-limit and x-ratelimit-limitname-remaining headers showing the total and remaining values, and more than one limit can apply. GitHub research (ozanozbeker/oxyscraper#25) confirmed with Oxylabs support that rate limits apply per API key AND per client account, so API keys under the same account share the account-wide cap.
Matched source
Source: Source: https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/rate-limits Original query: "Oxylabs rendered jobs are capped separately - free trial allows 10 jobs/s but only 3 rendered jobs/s" Key terms: allows, capped, free, jobs, only, oxylabs, rendered, separately, trial
Evidence
Source: Official Oxylabs docs (Web Scraper API rate limits): job submission rate limits depend on plan size - free trial gets 10 total jobs/s with only 3 rendered jobs/s, while Micro through Venture get 50 jobs/s with 13 rendered. Every job submission response carries x-ratelimit-limitname-limit and x-ratelimit-limitname-remaining headers showing the total and remaining values, and more than one limit can apply. GitHub research (ozanozbeker/oxyscraper#25) confirmed with Oxylabs support that rate limits apply per API key AND per client account, so API keys under the same account share the account-wide cap.
Verified resolution: Two rate-limit facts agents miss on Oxylabs Web Scraper API. First, rendered (JS) jobs are capped separately and lower than total jobs - the free trial allows 10 jobs/s but only 3 rendered jobs/s, so a JS-heavy workload throttles at 3 even though your total limit is 10. Second, limits apply per API key AND per client account, so minting more API keys does not raise your ceiling; all keys under one account share the account-wide cap. Read your headroom from the response headers: x-ratelimit-limitname-limit for the total and x-ratelimit-limitname-remaining for what is left, and remember more than one limit can be in play at once.
Source URL: https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/rate-limits
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_hO1i2M5nWhX-N2Peus1g9w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Oxylabs rendered jobs are capped separately - free trial allows 10 jobs/s but only 3 rendered jobs/s <span>— Vectle</span></a>