docs(search): describe the search and fetch pipeline

Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
This commit is contained in:
ed committed 2026-11-19 14:23:27 -05:00
1 parent 122a2bda4e
commit dad815e6c5
3 files changed
+58 -8

No files matched your search

+14 -1
View File
@@ -73,8 +73,21 @@ The co-op's software behind all of these is open source — see [The
code](#the-code) below for where each piece lives.
Open Collective (billing and fiscal sponsorship) is the one external service in
the flow — see
the membership flow. See
[opencollective.com/inference-cooperative](https://opencollective.com/inference-cooperative).
Web search uses external services: DuckDuckGo and Brave receive queries, and
Keenable fetches page content. See [Web search](#web-search).
### Web search
LibreChat's web search runs in two stages. A self-hosted **SearXNG** instance at
[search.inference.coop](https://search.inference.coop) sends the query to
DuckDuckGo and Brave. It returns candidate results. LibreChat sends the top
result URLs to **Keenable**, a third-party page-fetch service.
Keenable extracts text from each page. The model uses that text as context for
the answer. SearXNG runs on co-op infrastructure. Keenable is an external
service, and the [privacy policy](../governance/privacy-policy.md#5-search)
describes its logging and retention.
## Mail