> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/websearch/free-search.md).

# Free Online Mode

Want to let AI go online without spending money? Cherry Studio has two **free** options, neither requires a paid API:

## Option 1: The default Exa MCP (ready to use, no key required)

Cherry Studio **By default** just set the search provider to **Exa MCP**— uses public endpoints,**no API key required**. After installing, click 🌐 in the chat input box **globe** icon to enable online access for the current conversation; no extra configuration needed.

See [online mode](/docs/en-us/pre-basic/settings/websearch.md).

## Option 2: SearXNG (self-hosted, completely free)

If you're willing to deploy it yourself,**SearXNG** is an open-source metasearch engine that can run entirely locally / on your own server, with unlimited calls, and privacy is more controllable.

See deployment and integration steps in [SearXNG local deployment and configuration](/docs/en-us/pre-basic/settings/websearch/searxng.md).

{% hint style="info" %}
Want better retrieval results, or to use services like Tavily that **require a key** services? That counts as setting up a search provider in [online mode](/docs/en-us/pre-basic/settings/websearch.md) separately, and is not within the "free" category.
{% endhint %}

***

### Get help and submit feedback

If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to [Feedback and Suggestions](/docs/en-us/question-contact/suggestions.md) for the official channels provided.


---

# 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://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/websearch/free-search.md?ask=<question>&goal=<user_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.