> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/au3/community/contributing/credits-and-license.md).

# Credits & License

These help articles have been created by the following people:

* Leo Wattenberg
* Gonzalo Guzmán
* (add your name here if you're editing some pages!)

## License

Contents on this page are licensed under the [Creative Commons - Attribution](https://creativecommons.org/licenses/by/4.0/) license. This does not necessarily apply to embedded videos.

## Contributors of the old Manual

[manual.audacityteam.org](https://manual.audacityteam.org) has been made possible by a tremendous amount of effort from the following people:

* Gale Andrews
* Richard Ash
* David Bailes
* Christian Brochec
* Matt Brubeck
* John Colket
* James Crook
* Steve Daulton
* Scott Granneman
* Greg Kozikowski
* Leland Lucius
* Dominic Mazzoni
* Edgar Musgrove
* Tony Oetzmann
* Alexandre Prokoudine
* Peter Sampson
* Martyn Shaw
* Vidyashankar Vella
* Bill Wharrie
* Leo Wattenberg

**Translators:**

* Carmelo Battaglia (Italian)
* Leo Clijsen (Dutch)
* Olivier Humbert (French)
* André Leu (French)
* Thomas De Rocker (Dutch)
* Daniel Winzen (German)

Some of their efforts have been ported over to this site.


---

# 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.audacityteam.org/au3/community/contributing/credits-and-license.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.