Scrapybara · Rate Limits

Scrapybara Rate Limits

Scrapybara constrains usage primarily through concurrency and consumption quotas rather than published per-second request rates. Each plan caps the number of concurrent instances (Free 5, Basic 25, Pro 100) and meters monthly compute hours and agent credits; instances also carry a per-instance timeout_hours (0.01 to 24) after which they auto-terminate. Specific per-endpoint request-per-second limits are not published and are not reconciled in this artifact.

Scrapybara Rate Limits is the machine-readable rate-limit profile for Scrapybara on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring instances, hours, and credits.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI Agents, Virtual Desktops, Computer Use, Browser Automation, and Rate Limiting.

4 Limits Throttle: 429
AI AgentsVirtual DesktopsComputer UseBrowser AutomationRate LimitingQuotasConcurrency

Limits

Concurrent Instances account
instances
5 (Free) / 25 (Basic) / 100 (Pro)
Maximum number of instances that can run simultaneously, set by plan tier.
Compute Hours account
hours
10 (Free) / 100 (Basic) / 500 (Pro) per month
Monthly running-time allotment; overage billed per hour or blocked per plan.
Agent Credits account
credits
100 (Free) / 500 (Basic) / 2500 (Pro) per month
One credit per agent step; top-ups available at $0.04 per credit on paid plans.
Instance Timeout instance
hours
0.01 to 24
Each instance auto-terminates after its configured timeout_hours.

Policies

Concurrency-Based Limiting
Usage is gated primarily by concurrent-instance caps per plan rather than request-per-second throttling.
Auto-Termination
Instances stop automatically at timeout_hours to prevent runaway compute-hour consumption.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources