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-limit_name-limit for the total and x-ratelimit-limit_name-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-limit_name-limit and x-ratelimit-limit_name-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.