> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/binders/binders-general.md).
# Binders: general
Binders are bundles of single documents that follow the same styling, terminology, definitions, etc. (binders typically take the form of a a main agreement with several annexes attached to it, like a master services agreement with a number of statements of work or a share purchase agreement with schedules attached to it).
To open a binder, click on the button on the top right-hand side of the screen when in Assemble Document mode and choose *New Binder*.
You will quickly note that binders are virtually identical to documents in the way that they are presented in the document toolbar and the operations pane. For example, the “terms” and “datafield” menu of the operations panel function in the exact same way for binders as they do for documents.
How to manage (existing and new) documents in a binder is [described more in detail here](/assemble-document-operations-panel/binder-pane.md).
---
# 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.clause9.com/binders/binders-general.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.
button on the top right-hand side of the screen when in Assemble Document mode and choose *New Binder*.