Exa Search
Search the web with Exa's neural (semantic) or keyword search and get relevance-ranked results. Returns titles, URLs, and snippets, with optional publication dates, authors, and full page text; supports category filters (company, news, research paper, github, etc.) and published-date ranges. Ideal for: web research, semantic discovery, finding papers or company pages, building RAG datasets, monitoring recent content.
Catalog action Integrations
Search the web with Exa's neural (semantic) or keyword search and get relevance-ranked results. Returns titles, URLs, and snippets, with optional publication dates, authors, and full page text; supports category filters (company, news, research paper, github, etc.) and published-date ranges. Ideal for: web research, semantic discovery, finding papers or company pages, building RAG datasets, monitoring recent content.
At a Glance
| Field | Value |
|---|---|
| Action ID | exa-search |
| Category | Integrations |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | exa, search, web, neural, semantic, research, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search query. Natural-language queries work best with 'auto'/'neural' search; 'keyword' matches terms literally. |
numResults | number | No | Number of results to return. Range: 1-100. Default: 10 |
type | string | No | Search type. 'auto' lets Exa choose, 'neural' is semantic/embeddings-based, 'keyword' is literal term matching. Default: 'auto' |
category | string | No | Optional content category filter to focus results on a specific type of page. |
includeText | boolean | No | Whether to include the full page text of each result (larger payload, higher cost). Default: false |
maxCharacters | number | No | Maximum characters of page text to return per result when includeText is true. Range: 1-10000. Default: 2000 |
startPublishedDate | string | No | Only include results published on or after this ISO 8601 date (e.g. '2024-01-01T00:00:00.000Z'). |
endPublishedDate | string | No | Only include results published on or before this ISO 8601 date (e.g. '2024-12-31T23:59:59.999Z'). |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
success | boolean | Yes | Whether the search request was successful |
results | array | Yes | Search results, ordered by relevance |
Examples
json{ "type": "exa-search", "payload": { "query": "status:open" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/exa-search/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "query": "status:open" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.