Skip to main content
POST
Exa Search
Search the web and optionally extract content from returned results. This is a passthrough to Exa’s Search API, exposed through the Novita gateway with a platform route prefix. To authenticate with your Novita API key, get one from the Novita dashboard. Base URL: https://api.novita.ai.

Quickstart

Running the quickstart above returns the following at the time of publishing. The default request returns up to 10 results; two are shown here.

Request Headers

All endpoints require platform API authentication.
string
required
Use application/json.
string
default:"Bearer YOUR_API_KEY"
required
Platform API key, formatted as Bearer YOUR_API_KEY.

Request Body

string
required
Search query. Minimum length is 1.
string[]
Restrict results to these domains. Maximum 1200 entries.
string[]
Exclude results from these domains. Maximum 1200 entries.
string
Include links published after this ISO 8601 date-time.
string
Include links published before this ISO 8601 date-time.
integer
Number of results to return. Default is 10; supported public range is 1 to 100.
boolean
Enable content moderation to filter unsafe content from search results. Default is false.
object
Content extraction options for search results.
string[]
Additional query variants for deep-search modes. Range is 1 to 10 entries.
string
Search mode. One of instant, fast, auto, deep-lite, deep, or deep-reasoning.
string
Data category hint. Known values include company, research paper, news, personal site, financial report, publication, and people.Some values restrict which filters can be used:
  • company does not support startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, or excludeDomains.
  • people does not support startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, or excludeDomains, and includeDomains is limited to supported profile domains.
string
Two-letter ISO country code, such as US.
string
Enterprise compliance mode. Only hipaa is supported.
object
JSON Schema object for structured synthesized output. Supported root types include text and object; object schemas should describe the expected JSON object returned by Exa.
string
Extra instructions that guide synthesized output.

Examples

Search with highlights

Restrict to trusted domains

Use includeDomains to keep results within sources you trust.

Recent results only

Combine the news category with a published-date floor to filter out stale pages.
Use type: deep with an outputSchema to get a synthesized, schema-shaped result.

Response

string
Unique request identifier.
object[]
Search results.
object
Structured or synthesized output when requested.
number
Time taken to search in milliseconds.

Errors

Errors are returned as a JSON envelope with code, reason, message, and metadata. The platform validates and authenticates the request before forwarding it to Exa, so some errors originate at the platform and others are surfaced from upstream. For validation failures, message is a JSON-encoded string carrying the detailed error and tag. The examples below show that inner detail decoded for readability.

Notes

  • All request bodies are JSON.
  • Extra Exa parameters not listed here may be passed through.
  • Response shapes can vary depending on request options.
  • This document intentionally omits billing-related fields.

References

For more details, see the Exa Search API reference.
Last modified on July 30, 2026