API Overview
Choose the API for the web data you need.
Start with a search query or a page URL. Compare the available APIs, see what each returns, and choose the next step for your application.
Choose by input and output
What do you have, and what do you need back?
Search discovers links from a query. Fetch and Render turn a chosen URL into Markdown. Screenshot makes a separate PNG request when you need a visual record.
| I have | I need | Use |
|---|---|---|
| A question or keyword | Relevant source links | Search |
| A URL with content in its HTML | Readable Markdown | Fetch |
| A URL with JavaScript-loaded content | Rendered page Markdown | Render |
| A URL you need to see | A PNG image | Screenshot |
Two ways to begin
Combine APIs only when your task needs it
A query can lead to selected pages. If you already know the URL, you can extract it directly. A screenshot is an optional separate request.
Scope
Single-page requests and crawl orchestration
The documented public API provides source search, single-page extraction, and single-page screenshots. Your application chooses which URLs to process and handles a multi-page queue, deduplication, scheduling, and crawl depth when it needs them.
Can I start from a known URL?
Yes. Go straight to page extraction. Search is useful when you still need to find the source. Check the returned content before relying on it; a successful request alone does not establish completeness.