> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/legal/services-terms/experience-open-source-software-licenses/experience-2022.7-software-licenses.md).

# Experience 2022.7 software licenses

Apache-2.0

BSD 2-clause, 3-clause, 4-clause and like license

BSL-1.0

CC-BY-2.5

CC-BY-3.0

CC-BY-4.0

CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

CDDL + GPLv2 with classpath exception

Common Development and Distribution License (CDDL), Version 1.0

Common Public License Version 1.0

Creative Commons Legal Code

Custom

Day-Addendum

Dual license consisting of the CDDL v1.1 and GPL v2

Eclipse Public License

GNU GPL CE

GNU GPL

GNU LGPL

Go License

ISC

ITV-OSS

JSON

MIT

MPL-2.0

ODC-By-1.0

OFL-1.1

OpenSSL License

Public Domain

The Unlicense

Unicode/ICU License

W3C

WTFPL


---

# 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.nexthink.com/legal/services-terms/experience-open-source-software-licenses/experience-2022.7-software-licenses.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.