> For the complete documentation index, see [llms.txt](https://support.dexes.eu/support-dexes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.dexes.eu/support-dexes/licenties/zo-werken-licenties.md).

# Zo werken licenties

## Wat zijn licenties?

[Licenties](https://support.dexes.eu/support-dexes/licenties/zo-werken-licenties.md) bepalen het auteursrecht van je product. Hierin geef je aan wat er met je product mag gebeuren na aankoop. Je kan hier allerlei specificaties in opnemen, zoals niet-commercieel hergebruik, naamsvermelding of wie de data mag verrijken.

## Waarom heb je ze nodig?

Licenties bewaken (intellectuele) eigendommen en waarborgen veiligheid van informatie. Zo communiceer je helder over wat je wil dat er met je data gebeurt. Het effect van licenties is altijd achteraf, en je moet zelf in de gaten houden of de licentie wordt nageleefd. In geval van overtreding meld je dit eerst bij de overtreder en probeer je het samen op te lossen. Lukt dat niet, dan kan je dit bij het DMI-ecosysteem melden bij de geschillencommissie.


---

# 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://support.dexes.eu/support-dexes/licenties/zo-werken-licenties.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.
