> For the complete documentation index, see [llms.txt](https://help.cabi.org/cabi-digital-library-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cabi.org/cabi-digital-library-help/search/about-search-queries.md).
# About Search Queries
* A search query consists of one or more search terms, along with zero or more parameters, such as Boolean operators, and wildcards.
* An automatic AND is assumed between words entered next to each other in a search query. For example, a search for *bird cat dog* returns the same search results as *bird AND cat AND dog.*
* Query terms are not case sensitive, and punctuation marks, such as hyphens, commas, and semicolons, are ignored.
* Query length of up to 64,000 characters can be accommodated in both Advanced Search and the main keyword search.
* The search results query text rendered immediately above Search Results shows you how searches have been parsed.
Example of search query
---
# 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.cabi.org/cabi-digital-library-help/search/about-search-queries.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.
