Key Benefits
- Token efficient: Use
highlightsto get key excerpts relevant to your query, reducing token usage by 10x compared to full text, without adding latency. - Specialized index coverage: State of the art search performance on people, company, and code using Exa’s in-house search indexes.
- Incredible speed: Providing the fastest search available without compromising on quality, allowing for search to be added to real-time workflows.
Request Fields
Thequery parameter is required for all search requests. The remaining fields are optional. See the API Reference for complete parameter details.
| Field | Type | Notes | Example |
|---|---|---|---|
| query | string | The search query. Supports long, semantically rich descriptions for finding niche content. | ”blog post about embeddings and vector search” |
| type | string | Search method: auto (highest quality search), fast (high quality and lower latency). | “auto” |
| numResults | int | Number of results to return (1-100). Defaults to 10. | 10 |
| text | bool/obj | Return full page text. Can specify maxCharacters and includeHtmlTags. | true or {"maxCharacters": 5000} |
| highlights | bool | Return token-efficient excerpts most relevant to your query. | true |
| maxAgeHours | int | Maximum age of indexed content in hours. If older, fetches with livecrawl. 0 = always livecrawl, -1 = never livecrawl (cache only). | 24 |
| includeDomains | string[] | Only return results from these domains. | [“arxiv.org”, “nature.com”] |
| excludeDomains | string[] | Exclude results from these domains. | [“reddit.com”, “quora.com”] |
| startPublishedDate | string | Filter to content published after this date (ISO 8601). | “2024-01-01T00:00:00.000Z” |
| category | string | Target specific content types: company, people, tweet, news | ”company” |
| summary | bool/obj | Return LLM-generated summaries. Can specify custom query and JSON schema for structured extraction. | {"query": "Key technical contributions"} |
Search Type: Auto vs Fast
Thetype parameter selects the search method:
-
auto(default): Exa’s highest quality search. -
fast: Streamlined, low-latency search. Best for real-time applications where speed is critical.
Token Efficiency
Choosing the right content mode can significantly reduce token usage while maintaining answer quality.| Mode | Best For |
|---|---|
| text | Deep analysis, when you need full context, comprehensive research |
| highlights | Factual questions, specific lookups, multi-step agent workflows |
| summary | Quick overviews, structured extraction, when you control the output size |
maxCharacters to cap token usage.
Verbosity Settings
When usingtext, control how much content is returned with the verbosity parameter:
| Content Type | Compact | Standard | Full |
|---|---|---|---|
| Main body text | ✓ | ✓ | ✓ |
Image placeholders (![], ![alt]) | ✓ | ✓ | |
| Infobox/metadata tables | ✓ | ✓ | |
| Navigation menus | ✓ | ✓ | |
| Footer content | ✓ | ||
| Legal/copyright notices | ✓ | ||
| Site-wide links (About, Privacy, etc.) | ✓ |
Content Freshness
Control whether results come from Exa’s index or are freshly crawled usingmaxAgeHours:
maxAgeHours: 24: Use cache if less than 24 hours old, otherwise livecrawl. Good for daily-fresh content.maxAgeHours: 1: Use cache if less than 1 hour old. Good for near real-time data.maxAgeHours: 0: Always livecrawl (ignore cache). Use when cached data is unacceptable.maxAgeHours: -1: Never livecrawl (cache only). Maximum speed, historical/static content.- Omit (recommended): Default behavior — livecrawl as fallback if no cache exists.
Category Filters
Usecategory to target specific content types where Exa has specialized coverage:
| Category | Best For |
|---|---|
company | Company pages, LinkedIn company profiles |
people | Multi-source data on people, LinkedIn profiles |
research paper | Academic papers, arXiv, peer-reviewed research |
news | Current events, journalism |
tweet | Posts from X/Twitter |
personal site | Blogs, personal pages (Exa’s unique strength) |
financial report | SEC filings, earnings reports |

