> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/intelligence/chatbot/tools/web-search.md).

# Web Search

CRAFTSMAN INTELLIGENCE can search the public web, bringing current information into your conversation without leaving CRAFTSMAN+.

***

#### How It Works

Ask a question that depends on up-to-date or outside information and the assistant searches automatically. While the search runs, the chat shows a searching status. The assistant then reads the results and answers with what it found, woven into its reply like any other response.

You can also ask it to search directly:

* *"Search the web for the top hybrid casual trends this year"*
* *"Look up how match-3 games typically structure their end cards"*

***

#### When to Use It

Web search is most useful when your question reaches outside your project:

* Researching current trends in a genre or vertical before a build
* Looking up a brand, game, or competitor for reference
* Checking facts, stats, or dates the assistant would not otherwise know
* Gathering inspiration and references for a new concept

{% hint style="info" %}
*The more specific your request, the better the results. Include the market, genre, timeframe, or brand you care about.*
{% endhint %}


---

# 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://help.craftsmanplus.com/intelligence/chatbot/tools/web-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.