Crawler API taxonomy
Choose the right web access path.
AnyCrawler crawler APIs split into three practical jobs: discover sources with search, extract known pages with fetch or render, and capture screenshots when the workflow needs visual evidence.
API families
Route by the input you have and the output you need
The hub pages below keep direct endpoint pages easy to find while explaining how each capability fits into a production crawler workflow.
Routing guide
Start with the crawler job, then pick the endpoint
Search is for discovery, page crawl is for machine-readable extraction, and screenshots are for visual records. Most agent workflows use these in sequence rather than treating them as isolated tools.
| Starting point | Use | Next step |
|---|---|---|
| Known URL | Page crawl | Fetch static HTML pages or render JavaScript-heavy pages. |
| Unknown source | Search | Find candidate pages, news, images, videos, or papers before crawling. |
| Visual record needed | Screenshot | Capture a stored PNG after opening the page in the browser path. |
Common workflow
Discovery, extraction, evidence
A crawler pipeline can stay simple: find sources only when needed, extract text from selected pages, and capture screenshots for records that need review.