> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/similar.md). # Exa Similar Blocks for finding web pages similar to a given URL using Exa's Find Similar API, which Exa has deprecated. ## Exa Find Similar ### What it is Deprecated by Exa: prefer the Exa Search block with a query describing the source page. Finds pages similar to a URL using Exa's findSimilar API. ### How it works Exa has deprecated Find Similar; for new workflows, use the Exa Search block with a query that describes the source page. This block sends the URL to Exa's `/findSimilar` endpoint in one request and returns pages similar to it, each with up to 10,000 characters of page text unless you change Contents. You can filter by domain, published date, category and (deprecated by Exa) text, and leave out the source URL's own domain. Legacy categories are translated as in Exa Search ('research paper' to 'publication', 'linkedin profile' to 'people'), the crawl dates are never sent because Exa ignores them, and Moderation is still sent when enabled although Exa no longer documents it here. The run is billed from the dollar cost Exa reports, at 150 credits per US dollar. ### Inputs | Input | Description | Type | Required | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | url | The url for which you would like to find similar links | str | Yes | | number\_of\_results | Number of results to return (1 to 100) | int | No | | exclude\_source\_domain | Leave out results from the same domain as the source URL | bool | No | | category | Focus the search on one kind of page: company, people, news, publication (scholarly papers, preprints and journal articles), personal site or financial report. 'company' and 'people' do not support published-date filters, and 'people' does not support Exclude Domains. Legacy: 'research paper' is sent as 'publication' and 'linkedin profile' as 'people', the replacements Exa documents; 'pdf', 'github' and 'tweet' are being retired by Exa. | "company" \| "people" \| "news" \| "publication" \| "personal site" \| "financial report" \| "research paper" \| "linkedin profile" \| "pdf" \| "github" \| "tweet" | No | | include\_domains | List of domains to include in the search. If specified, results will only come from these domains. | List\[str] | No | | exclude\_domains | Domains to exclude from search | List\[str] | No | | start\_crawl\_date | Deprecated by Exa and ignored by the API, so this block no longer sends it. Use Start Published Date instead. | str (date-time) | No | | end\_crawl\_date | Deprecated by Exa and ignored by the API, so this block no longer sends it. Use End Published Date instead. | str (date-time) | No | | start\_published\_date | Start date for published content | str (date-time) | No | | end\_published\_date | End date for published content | str (date-time) | No | | include\_text | Deprecated by Exa. Strings that must appear in the page text (approximate, word-level matching) | List\[str] | No | | exclude\_text | Deprecated by Exa. Strings that must not appear in the page text | List\[str] | No | | contents | What to return for each result. Left empty, each result gets up to 10,000 characters of page text. | ContentSettings | No | | moderation | Legacy: Exa's Find Similar API no longer documents moderation; still sent when enabled. | bool | No | ### Outputs | Output | Description | Type | | ------------- | -------------------------------------------------------------------------------------------------------- | ----------------------- | | error | Error message if the request failed | str | | results | List of similar documents with metadata and content | List\[ExaSearchResults] | | result | Single similar document result | ExaSearchResults | | context | Deprecated by Exa: the results as one string for LLMs, returned only when Contents > Context is enabled. | str | | request\_id | Unique identifier for the request | str | | cost\_dollars | Cost breakdown for the request | CostDollars | ### Possible use case **Content Discovery**: Find related articles, blog posts, or resources similar to content you already like. **Competitor Analysis**: Discover similar companies or products by finding pages similar to known competitors. **Research Expansion**: Expand your research by finding additional sources similar to key reference materials. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://agpt.co/docs/integrations/block-integrations/similar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.