Skip to main content
/search runs a web search (Google results) and returns the results best first: each one’s url, title and description (the snippet the search engine shows). Set type=news for recent articles with their publisher and date. Ask for page content, and every result page is scraped in the same request, exactly as /scrape would scrape it, and returned in scrape on its result. One call answers “find pages about X and give me their text”. Use /search to find pages. For a researched answer with sources, use /answers. When you already know the page, use /scrape.

Example requests

Example response

Search operators work in query the way they do on Google: "exact phrase", -word, filetype:pdf and site:example.com. Results on your account’s blocklist are dropped, and the rest renumbered.

Scraping the results

Ask for content with formats on GET (for example formats=markdown,links, plus only_main_content and max_age), or a scrape_options object on POST with any option /scrape takes. Up to 10 results can be scraped in one request. Result pages are fetched in parallel within one deadline: 45 seconds by default, and timeout can shorten it. A page that can’t be fetched (blocked, too slow, not a page) gets a scrape_error with an error code instead of scrape, and isn’t charged. The search itself still succeeds.

Credits

A 10-result search costs 2 credits. With every page as markdown, it costs 12.

Next

Answers

A researched, sourced answer instead of a list of links.

API reference

Every parameter, and a playground to try it.