> For the complete documentation index, see [llms.txt](https://docs.meshmap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meshmap.com/unity-sdk/overview/license.md).

# License

## Apache 2.0

Similar to many other open-source projects, the use, reproduction, and distribution of the MeshMap Unity SDK is governed by the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0).

You can find a copy of this license in the LICENSE.md file included at the root level of each of our packages and sample projects. There is also a NOTICE file.

## Third-Party Licenses

Some of our packages and sample projects rely on third-party software dependencies.

You can find a list of third-party dependencies in the THIRD\_PARTY\_LICENSES.md file included at the root level of our packages and sample projects. The full text of each license and any provided NOTICE files are included in the /licenses/ folder.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meshmap.com/unity-sdk/overview/license.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
