# Search and get page text in the same call

> Search and get page text in the same call: 7 companies fully do it, 6 with a limit, 76 carry the tag. Every listing in Web search APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/search.search-with-text/
- Markdown: https://www.anchorterminal.com/niches/search.search-with-text/index.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/niches/search.search-with-text/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/search.search-with-text/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 7 | 6 | 76 | 14 | 8 |

## What counts as done

Each of the top results carries extracted page text or highlights of a controllable length (a max tokens or characters parameter).

Measured, for our own tests: the whole response fits in a few thousand tokens.

How agents ask for it: find and read what the top pages say about X; give me the content, not only links; research X and quote the sources

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Brave Search API + MCP (Brave Software, Inc.)**: LLM Context returns extracted snippets per URL with maximum_number_of_tokens (1,024 to 32,768) and maximum_number_of_tokens_per_url; Web Search adds up to five extra_snippets per result.
- **Exa API + MCP (Exa Labs Inc.)**: contents.highlights or contents.text in the search request, each with maxCharacters; an informal test ranked Exa first for agent search.
- **Parallel Search and Task APIs (Parallel Web Systems Inc.)**: Results are excerpts per URL, capped by max_chars_total; basic mode returns extended snippets.
- **Perplexity Search API (Perplexity AI, Inc.)**: max_tokens_per_page and max_tokens cap the extracted snippet per result and for the response; a citation-checking user runs it at volume.
- **SerpKite (Anastasia Klimova, trading as SerpKite)**: include_content fetches that many result pages as Markdown in the same call at 1 credit a page, with highlights ranked against the query and fields or compact format to trim the rest.
- **Tavily API + MCP (AlphaAI Technologies Inc. dba Tavily)**: include_raw_content returns page text per result and chunks_per_source caps it; include_usage reports credits.
- **Valyu (Valyu.Network Ltd)**: Each result carries content, capped by response_length short, medium, large, max or a character count, with max_price bounding the request.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Web Search Tool on Amazon Bedrock AgentCore (Amazon Web Services, Inc. (regional AWS entities by account location))**: Each result's text field is a semantically extracted snippet, not a link only, but the only size control is maxResults; no token or character cap exists.
- **Cloudflare Web Search API (Cloudflare, Inc.)**: Ceramic returns descriptions up to 8,000 characters and Exa returns highlights as the description, but there is no size parameter.
- **Kagi Search API (Kagi Inc.)**: extract.count (1 to 10) replaces each snippet with the page Markdown in the same call, but it is billed at the Extract rate on top of the search and one user got no content back.
- **Linkup (Linkup Technologies SAS)**: Each result carries content (extracted text) and a snippet, but the reference has no character or token cap parameter.
- **SpecStream (SpecStream SAS)**: passages=true returns the text of the top pages closest to the request, adding about a second, with no length cap parameter.
- **You.com APIs (SuSea, Inc., d/b/a you.com)**: extraction_mode highlights or full_page (markdown or html) returns text per result, but there is no token or character cap, only crawl_timeout and count.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **DeepSeek Search and Fetch API (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.)**: Docs not opened (terms bar automated copying) and no account describes the need_content option.

- not this job: Arcmira (Arcmira, Inc.): Passage text comes from transcripts, not web pages; the use case asks for extracted web page text.
- not this job: Grounding with Bing Search (Microsoft Corporation): No page text or highlights are returned, only the model's text with citation links.
- not this job: Fetch (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): No search.
- not this job: Grep AI (Parcha Labs, Inc.): No search endpoint; runs return a report.
- not this job: Liner Search MCP (Liner): Results carry a description only; no extraction or highlights parameter.
- not this job: Mojeek Web Search API (Mojeek Limited): Results carry a description only; no extraction option.
- not this job: NewsCatcher (NewsCatcher, Inc.): Snippets are the start of the publisher's description, cut to the plan's length; no extraction.
- not this job: SearchAPI.io (SearchApi, LLC): SERP snippets only; no page extraction.
- not this job: SerpApi (SerpApi, LLC): output=md is the SERP as Markdown, not page text.
- not this job: Serper (Serper): Snippets only; no page text in the response samples.
- not this job: SERPHouse (Patoliya Infotech LLP): SERP fields only; page text needs the separate Scraper API.
- not this job: TinyFish Search (Tiny Fish, Inc.): Search returns snippets; page text needs a second call to the Fetch API.

## What stops agents finishing

- extraction billed on top of the search without a cap (Kagi, Tavily advanced)
- extracted text fills the context when no token cap is set (Perplexity)
- SPA pages come back empty with no error (Tavily extract)

## Around it

After: document-extraction.summarise, memory.store.

## Where this comes from

Weight 14 of 100 in Web search APIs: 8 of 44 accounts chose a provider because text came back with the results (Kagi extract, Exa highlights, Perplexity, Tavily raw content, Linkup) or complained a provider only returned links

As data: https://www.anchorterminal.com/api/v1/use-cases/search.search-with-text.json, or the MCP tool get_use_case with id search.search-with-text. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
