Spider · Rate Limits

Spider Cloud Rate Limits

Rate limit definitions for the Spider Cloud API. Every account is permitted up to 10,000 core API requests per minute by default. Spider's hosted MCP server inherits the same per-account API limit. Browser-automation sessions are constrained to five concurrent sessions and time out after five minutes of inactivity. Enterprise accounts can negotiate higher limits.

Spider Cloud Rate Limits is the machine-readable rate-limit profile for Spider on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, across the default and enterprise tiers, measuring requests_per_minute, concurrent_sessions, and idle_minutes.

Limit state is signalled in the limit, remaining, reset, and retryAfter 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 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Crawling, Scraping, Data Extraction, URLs, and AI.

4 Limits Exhausted: HTTP 429 Quota: 429 limitremainingresetretryAfter
Method: generated, dated 2026-05-25.
Written by API Evangelist on 2026-05-25 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
CrawlingScrapingData ExtractionURLsAIRate LimitingQuotasThrottling

Limits

Default Core API RPM account
requests_per_minute · minute
10000
Browser Session Concurrency account
concurrent_sessions · instant
5
Browser Session Idle Timeout session
idle_minutes · minute
5
Negotiated Enterprise Limit contract
requests_per_minute · minute
-1

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses, honoring the Retry-After header when present.
Failed Requests Are Free
Spider's billing model does not charge for failed responses — only successful responses that return data — which complements rate limit recovery.
Browser Session Lifecycle
Browser-automation sessions are limited to five concurrent sessions per account and are automatically closed after five minutes of inactivity.
Enterprise Negotiation
Accounts needing more than 10,000 RPM should contact sales for custom rate limit provisioning.
Robots.txt
Crawling honors robots.txt by default; clients can opt out but should respect target-site policies and fair-use norms.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/spider-cloud-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.