Skip to main content
POST
Search the web
Search the open web and get back a lean result list. ⚠️ Despite being a POST, parameters go in the query stringquery (required), max_num_results (default 10, max 100), and as_ylo/as_yhi for a year range. A JSON body is not accepted. Returns a search id and results[] carrying only title, link and snippet. Measured at about 4 seconds for a roughly 600-byte response. Its virtue is how little it returns, which suits an agent that only needs to know what exists. It gives you no page text — if you need the content, post_tavily_search returns it in the same call. Keep the id: it is what post_scholar_search_explain needs.
Scholar search endpoints use POST with parameters in the query string. Do not send query or max_num_results as a JSON or form body.

Example

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

query
string
required

Search query for scholarly materials

Example:

"machine learning"

max_num_results
integer
default:10

Maximum number of search results to return, up to 100

Required range: 1 <= x <= 100
as_ylo
integer | null

Year of publication lower bound

Required range: 1900 <= x <= 2030
as_yhi
integer | null

Year of publication upper bound

Required range: 1900 <= x <= 2030

Response

Successful search response

id
string
required

Unique identifier for the search request

results
object[]
required

List of web search results