Scrapfly Rate Limits
Scrapfly does not advertise per-second request limits. Throttling is enforced primarily through account-level concurrency caps (set by subscription tier) and credit-pool exhaustion. Per-domain throttling may also engage. The API surfaces concurrency and credit state in response headers, and returns 429 when concurrency, free quota, or domain throttling is hit.
Scrapfly Rate Limits is the machine-readable rate-limit profile for Scrapfly on the APIs.io network, in the API Commons Rate Limits shape.
It captures 7 rate-limit definitions, measuring concurrent_requests and varies.
Limit state is signalled in the accountConcurrentUsage, accountRemainingConcurrentUsage, projectConcurrentUsage, and projectRemainingConcurrentUsage response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.
Tagged areas include Web Scraping, Data Extraction, and Rate Limiting.
accountConcurrentUsageaccountRemainingConcurrentUsageprojectConcurrentUsageprojectRemainingConcurrentUsage
generated, dated 2026-05-05.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.