Give your agents the whole web, as data.
Crawl, scrape and search the web with one API. Get clean markdown or JSON back for your agents.
Sign up and run requests before you buy. Or copy the setup prompt into your coding agent.
{
"url": "https://doc.rust-lang.org/book/",
"return_format": "markdown"
}# The Rust Programming Language
*by Steve Klabnik, Carol Nichols, and Chris Krycho, with contributions from the Rust Community* This version of the text assumes you’re using Rust 1.90.0 (released 2025-09-18) or later with `edition = "2024"` in the *Cargo.toml* file of all projects to configure them to use Rust 2024 Edition idioms.Three products. One key.
Start with the API. The browser and the proxy network also work on their own. The trace below is one crawl through all three.
- api.spider.cloud
Step one of an example trace, captured 2026-09-05. The API receives POST /crawl for doc.rust-lang.org/book with a limit of 30, hands the job to the browser, waits, and returns 30 pages of markdown totalling 331 kilobytes with status 200. Every page came back 200. demo-01 is an illustrative correlation id, not an API field.
- browser.spider.cloud
Step two. The browser opens a session, accepts the request from the API, routes it through an ISP exit in Germany, loads each of the 30 pages from doc.rust-lang.org/book, and hands the markdown back to the API before closing the session. demo-01 is an illustrative correlation id, not an API field.
- proxy.spider.cloud
Step three. The network accepts the browser's request and routes it through an ISP exit in Germany, rotating the exit per request, then fetches the 30 pages from doc.rust-lang.org/book and returns them to the browser. The pool is 215M+ exits in 199 countries. demo-01 is an illustrative correlation id, not an API field.
Crawl, scrape, search
Whole sites or single pages, returned as markdown, JSON, links or screenshots. Search the web from the same key.
See the APIA browser we wrote
Headless, written from scratch in Rust. Stealth and CAPTCHA solving are on by default, up to 100 sessions at once.
See the browserThe network underneath
215M+ residential and ISP exits in 199 countries, rotated per request. Works with our browser or yours.
See proxy locationsUse the whole web like a dataset.
Most websites have no API. Spider renders their pages and extracts the content for your RAG pipeline or agent.
Two figures, each with its source.
Drawing of a hatched source sheet projected into a rendered browser viewport, with the scroll spine marked where the page ends.
Renders like a user
Scripts run, lazy images load, and infinite scroll reaches the end. You get the page a person sees, not the one the server sends.
See the browserDrawing of a hatched wall with one gate. Two paths from a browser and the network meet at the gate and one path leaves it, ending at a page marked 200.
Passes the checkpoint
The request handles bot walls, CAPTCHAs and geo checks on its own. What comes back is the page, with a 200.
See the unblockerDrawing of a web page with its navigation, sidebar and footer hatched out, and the article lifting off as a clean sheet of markdown.
Extracts the content
Navigation, ads and footers drop away. What is left is markdown or JSON that reads the way the page was written.
See the formatsDrawing of thirty numbered pages on a conveyor rail, the first ones already lifted off and delivered, the last one still in flight.
Streams in order
Each page in a crawl arrives as one JSONL line the moment it is done, in order. Nothing waits for the last URL.
See streaming
Pay for usage, or for concurrency.
pay as you go
no minimumPlus $0.001 per CPU minute.
- Bandwidth
- $1 per GB
- CPU time
- $0.001 per minute
- Blocked, timed out, failed
- $0
unlimited
flat ratePriced by concurrency units. View unit pricing
- Requests
- unlimited
- Starting allocation
- 2 concurrency units
- Per concurrency unit
- $20 down to $13
Make your first request.
01Get a key
Create API keySign up and copy the key. New accounts start with a free balance.
export SPIDER_API_KEY="sk-..."
SDKs, the MCP server and every command read it.
02 Connect Claude Code Client configs in the docs
claude mcp add spider --transport http \ https://mcp.spider.cloud/mcp \ -H "Authorization: Bearer $SPIDER_API_KEY"
Read and follow https://spider.cloud/agent-skill/SKILL.md
Or skip MCP and let the agent onboard itself
03Read the data
example output example data after a scrape[{
"url": "https://example.com",
"status": 200,
"content": "# Example Domain\n\n..."
}]The connection comes first. Data like this arrives once the client makes a request.
Markdown or JSON, streamed. Drop it into your RAG store, agent context or database.
Start with one URL.
Create a key. Make your first request.