> For the complete documentation index, see [llms.txt](https://doc.montoyer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.montoyer.com/welcome.md).
# Welcome!
Montoyer.com is the doc that you missed at the EU Institutions
{% hint style="info" %}
**Disclaimer about this documentation:** The info published here is unofficial documentation collected from the knowledge of former IT consultants working for the Commission, the Council, the Parliament and other EU Institutions. In no way we can be seen as accountable for the quality of the content.
{% endhint %}
For **aspiring IT consultants**, this space will be helpful during the selection process and your first days within the Institutions, to better learn about how the EU works.
For **long-time IT consultants**, this space will act as a reminder and allow you to find answers about contracts, admin and policies, etc.
How to use it?
This space is designed to be read linearly, so start with our Introduction pages and work down from there! We recommend reading everything through in one sitting and then revisiting and re-reading if you need to.
Contributing
If you want to contribute changes, start a new change request and submit it for review. The Montoyer team will review it soon after.
---
# 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://doc.montoyer.com/welcome.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.
