> For the complete documentation index, see [llms.txt](https://docs.klausi-studios.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klausi-studios.de/welcoming/please-read-this-first.md).

# Please read this first

Please take short moment to read through the founder's welcoming message.

> *Thank you for your interest in our services. Me, the founder, has always been passionate about creating a group that stands out for its quality. While many equate quality with high costs, I firmly believe that "Good quality does not always have to be expensive!" With this vision in mind, Klausi Studios was born—a place where excellence and affordability go hand in hand. We hope you enjoy what we have to offer and look forward to serving you with the highest standards at reasonable prices.*
>
> ***Klausi***

At Klausi Studios, we strive to offer products at a reasonable price. Furthermore, we offer various promotions, which can be found under:

{% content-ref url="/pages/LhQuZcpLVYSQPFXcP1kd" %}
[Discounts](/discounts.md)
{% endcontent-ref %}

*"We don't need to charge unnecessary money; we only charge what we actually need for development!"*


---

# 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.klausi-studios.de/welcoming/please-read-this-first.md?ask=<question>&goal=<user_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.