Performs comprehensive web searches using the Heurist ExaSearch Digest Agent, returning AI-synthesized summaries of search results with support for domain filtering, time-based filtering, and disambiguation. Ideal for research, fact-checking, and gathering current information from across the web. | Input: Accepts a natural language search query, optional time filter (past week/month/year), domain inclusion list, result limit, and disambiguation context for unclear terms. | Output: Returns an AI-synthesized summary of web search results with cited sources, organized by topic and context, along with the original search parameters used. | Use cases: I need to research the latest developments in a specific technology or project; Get me a comprehensive summary of what people are saying about a topic online; I want to find information from specific websites or domains about a subject; Help me understand a new or ambiguous term by searching and synthesizing web results
This action will execute the specified operation when your workflow runs.
This integration requires a connector to be configured before it can be used in workflows.
Debug mode flag. ALWAYS use false.
falseIf the search query contains ambiguous entity names, new projects, new technology, or niche acronyms AND when you have contexts pointing to what it is exactly, describe the entity with one sentence to help clarify, for example 'Heurist is a Web3 AI project'. If you don't have confident clarifications or when searching common-sense info, leave this field blank.
List of domains to include in search (e.g., ['arxiv.org', 'papers.com']). Supports paths (e.g., 'example.com/blog') and wildcards (e.g., '*.substack.com')
Number of pages
10Natural language search query. Phrase naturally and concisely. Boolean operators (AND/OR) are NOT supported.
REQUIRED for time-sensitive queries
past_weekpast_monthpast_yearPayment details from x402 facilitator
Fields
amountPaidAmount paid in smallest token unitassetToken address used for paymentnetworkNetwork where payment was made (e.g., 'base')payerPayer wallet addresstransactionTransaction hash (may be null if server doesn't return x-payment-response header)The endpoint response data. Access fields with {{nodeId.result.resource.fieldName}}
Whether the request succeeded
HTTP status code