The current integration with the Exa AI Search API (/search endpoint) does not utilize several available date filtering parameters.
According to the official documentation:
https://exa.ai/docs/reference/search
The API supports the following fields which are currently not included in our implementation:
startCrawlDate
endCrawlDate
startPublishedDate
endPublishedDate
Problem
Without these parameters, search results cannot be filtered effectively by:
When content was crawled
When content was originally published
This limits the relevance and freshness of results, especially for time-sensitive queries (e.g., news, trends, recent updates).
Expected Behavior
Update the Exa Search API integration to support passing the above date filters as optional parameters in the request payload.
Impact
Improves search relevance
Enables time-based filtering
Enhances downstream features like trend analysis and newsletters
The current integration with the Exa AI Search API (/search endpoint) does not utilize several available date filtering parameters.
According to the official documentation:
https://exa.ai/docs/reference/search
The API supports the following fields which are currently not included in our implementation:
startCrawlDate
endCrawlDate
startPublishedDate
endPublishedDate
Problem
Without these parameters, search results cannot be filtered effectively by:
When content was crawled
When content was originally published
This limits the relevance and freshness of results, especially for time-sensitive queries (e.g., news, trends, recent updates).
Expected Behavior
Update the Exa Search API integration to support passing the above date filters as optional parameters in the request payload.
Impact
Improves search relevance
Enables time-based filtering
Enhances downstream features like trend analysis and newsletters