Airtop · Rate Limits

Airtop Rate Limits

Airtop's primary constraint is plan-based concurrency - the maximum number of simultaneous cloud browser sessions - rather than a published per-minute request quota. Each plan caps concurrent sessions (Free 3, Starter 3, Professional 30, Enterprise 100, Custom negotiated). Throughput is further governed by a monthly credit balance consumed per browser operation, and individual AI operations accept costThresholdCredits / timeThresholdSeconds guards to bound a single call. Specific HTTP request-per-minute limits are not published and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring concurrent_sessions, credits, and seconds.

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

Tagged areas include Browser Automation, AI Agents, Cloud Browser, Web Scraping, and Rate Limiting.

4 Limits Throttle: 429
Browser AutomationAI AgentsCloud BrowserWeb ScrapingRate LimitingQuotasThrottling

Limits

Simultaneous Sessions account
concurrent_sessions
plan-based (Free 3, Starter 3, Professional 30, Enterprise 100)
Maximum cloud browser sessions running at once; raises with plan tier.
Monthly Credits account
credits
plan-based credit pool
Credits consumed per page load, interaction, scrape, and AI query/extraction; complex actions (e.g. captcha) cost more.
Per-Operation Cost Threshold request
credits
caller-defined (costThresholdCredits)
Optional per-call guard that cancels an AI operation if it would exceed the credit budget.
Per-Operation Time Threshold request
seconds
caller-defined (timeThresholdSeconds)
Optional per-call guard that cancels an AI operation after the time limit.

Policies

Concurrency-Based Limiting
Throughput is governed mainly by simultaneous-session caps per plan rather than a fixed RPM quota.
Credit Exhaustion
When the monthly credit pool is depleted, further operations are blocked until credits are replenished or the plan is upgraded.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources