> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/help-and-resources/minted-documents.md).
# Minted Documents
Removing the Documint branding watermark
#### Active Templates
Documents that are created from an active template will be free of any Documint branding or watermark and will count towards your merge quota. For instance, if you are using the free plan, you have 10 branding-free merges and each document that is created from an active template will decrement the number of merges by one. Once you have used up all 10 merges on the free plan, the Documint branded footer will be displayed on all subsequent documents. To continue generating documents free of any Documint branding or watermark, consider upgrading your account. This will enhance your experience.
---
# 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.documint.me/help-and-resources/minted-documents.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.
