Exa Search
Search
Exa Search
POST
Exa Search
This document describes the Exa passthrough endpoints exposed by the platform gateway. It is based on Exa’s Search, Get Contents, and Answer APIs, with platform route prefixes applied.
Base URL example:
https://api.novita.ai
Search the web and optionally extract content from returned results.
Request Headers
All endpoints require platform API authentication.Use
application/json.Platform API key, formatted as
Bearer <api_key>.Request Body
Search query. Minimum length is 1.
Restrict results to these domains. Maximum 1200 entries.
Exclude results from these domains. Maximum 1200 entries.
Include links crawled after this ISO 8601 date-time.
Include links crawled before this ISO 8601 date-time.
Include links published after this ISO 8601 date-time.
Include links published before this ISO 8601 date-time.
Number of results to return. Default is
10; supported public range is 1 to 100.Enable content moderation to filter unsafe content from search results. Default is
false.Content extraction options for search results. See Search Contents Object.
Additional query variants for deep-search modes. Range is
1 to 10 entries.Search mode. Common values include
instant, fast, auto, deep-lite, deep, and deep-reasoning.Data category hint. Known values include
company, research paper, news, personal site, financial report, and people. See Search Category Limits.Two-letter ISO country code, such as
US.Enterprise compliance mode, such as
hipaa.JSON schema for structured synthesized output. See Search Output Schema.
Extra instructions that guide synthesized output.
Search Contents Object
Thecontents object controls which content fields are extracted from search results.
Return page text or configure text extraction. See Search Text Options.
Return selected highlight snippets or configure highlight extraction. See Search Highlight Options.
Return generated summaries or configure summary generation. See Search Summary Options.
Return extra page data such as links, image links, rich links, or code blocks. See Search Extras Options.
Timeout for live crawling in milliseconds.
Maximum cache age in hours.
0 requests fresh content; -1 always uses cache.Number of subpages to crawl. Range is
0 to 100.Term or terms used to find targeted subpages.
Search Category Limits
Some category values restrict which filters can be used.Does not support
startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, or excludeDomains.Does not support
startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, or excludeDomains. includeDomains is limited to supported profile domains.Search Text Options
Maximum number of text characters to return. Range is
1 to 10000.Include lightweight HTML tags instead of plain text.
Requested text verbosity.
Semantic page sections to include.
Semantic page sections to exclude.
Search Highlight Options
Custom query used to select highlights.
Maximum characters to return for highlights. Range is
1 to 10000.Search Summary Options
Custom instruction for summary generation.
Optional JSON schema for structured summary output.
Search Extras Options
Number of links to return. Range is
0 to 1000.Number of image links to return. Range is
0 to 1000.Number of rich image links to return. Range is
0 to 1000.Number of rich links to return. Range is
0 to 1000.Number of code blocks to return. Range is
0 to 1000.Search Output Schema
outputSchema accepts a JSON Schema object for structured output generation. Supported root types include text and object; object schemas should describe the expected JSON object returned by Exa.
JSON Schema root type, commonly
text or object.Field definitions for the structured output.
Required property names.
Array item schema when a property is an array.
Whether undeclared fields are allowed, or a schema for additional fields.
Request Example
Response
Unique request identifier.
Search results.
Structured or synthesized output when requested. See Search Synthesis Output Object.
Search Synthesis Output Object
Generated content. It can be structured when
outputSchema is provided.Field-level grounding or citation metadata when returned.
Result Object
Result title.
Result URL.
Published date when available.
Author when available.
Exa document ID.
Associated image URL.
Site favicon URL.
Extracted page text when requested.
Highlight snippets when requested.
Scores for returned highlights.
Generated summary when requested.
Subpage results when requested. See Search Subpage Object.
Structured entity data when returned. See Search Entity Object.
Extra links, images, rich links, or code blocks when requested. See Search Response Extras Object.
Search Subpage Object
Subpage title.
Subpage URL.
Exa document ID when available.
Extracted text when requested.
Generated summary when requested.
Highlight snippets when requested.
Search Entity Object
Entity name.
Entity type when returned.
Associated URL when returned.
Entity description when returned.
Additional entity metadata.
Search Response Extras Object
Links found on the page.
Image links found on the page.
Image links with additional metadata.
Links with additional metadata.
Code blocks found on the page.
Errors
The platform may return standard HTTP errors before forwarding the request, and Exa may return upstream errors after forwarding.Invalid request body or unsupported parameter value.
Missing or invalid API key.
Access denied by platform or upstream provider.
Route or requested resource not found.
Rate limit exceeded.
Internal server error.
Upstream provider error.
Service unavailable.
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 June 12, 2026