> For the complete documentation index, see [llms.txt](https://hitmakr.gitbook.io/hitmakr-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hitmakr.gitbook.io/hitmakr-whitepaper/ecosystem-overview/factory/licensing.md).

# Licensing

With an audio ledger, licensing and supplying various types of audio content becomes remarkably streamlined and efficient. Artists and content creators can easily register their works on the ledger, specifying the terms of licensing and distribution. This standardized process simplifies the negotiation and execution of licensing agreements, reducing administrative overhead and legal complexities.

Moreover, the immutable nature of the blockchain ensures that licensing agreements are securely recorded and tamper-proof, providing a reliable record of rights ownership and usage permissions. This transparency builds trust between licensors and licensees, facilitating smoother transactions and minimizing disputes.


---

# 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://hitmakr.gitbook.io/hitmakr-whitepaper/ecosystem-overview/factory/licensing.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.
