> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/truffle-hunt/faq/what-is-the-difference-between-the-strict-and-non-strict-option-when-searching-for-clauses.md). # What is the difference between the strict and non-strict option when searching for clauses? ClauseBuddy offers two search modes: Smart and Strict.\ The default mode is smart. Here, ClauseBuddy uses an intelligence layer to find semantically matching clauses. The search is not literal, so descriptions and synonyms usually also show the correct clause at the top. \ Strict search is possible by checking the box to the right of the search bar. A literal search is performed in this mode. Grammatical variations are allowed, but synonyms are excluded from the search results. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.clausebuddy.com/truffle-hunt/faq/what-is-the-difference-between-the-strict-and-non-strict-option-when-searching-for-clauses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.