API & MCP terms

Effective: October 27, 2026 · Last updated: October 27, 2026

These rules apply to the website and to anyone, or any AI assistant or program, that uses our API or MCP (Model Context Protocol) service. They are part of the Terms of Use.

Who these rules bind. These rules bind the person or organization that operates the assistant, plugin or program that calls the service (the operator), and the user who tells an assistant to use it. If you operate a platform or directory that lists the Moose Tracker plugin, these terms also apply to your use of the service.

1. What the service is

The API/MCP service lets a program write songs in Moose Tracker's text format, edit them, and ask for audio. Moose Tracker is a synthesizer: it plays the notes it is given with its own built-in sounds. It is not an AI music model, and it does not copy recordings.

2. Fair use and limits

The service is free and runs on a small budget, so it is limited. These limits can change without notice: request size, audio renders per client per hour and per day, one render at a time per client, maximum song length and file size, and an overall daily and monthly budget. When a limit is reached the service answers with HTTP 429 and a Retry-After header, or returns a share link that opens the song in the website instead of an audio file. We may also pause rendering for everyone when the overall budget is used up.

3. You must not

Exceed or try to get around limits. Rotating IPs, API keys, user agents or platform IDs to avoid a limit, or running many assistants in parallel to the same end, counts as getting around limits.
Crawl or bulk-download the service with automated tools beyond ordinary use of the API. The demos and sounds are free to use, so if you want many of them, ask us at the contact below instead.
Probe, attack, overload or disrupt the service, or try to access anything that is not yours.
Use the service to host or distribute files for purposes other than getting the audio you asked for.
Submit unlawful content or content that infringes others' rights, use the service to produce material that infringes someone else's rights, or use it to evade a rights-holder's takedown request.

4. Our rights

We may throttle, block, or remove access for any client or address, change or remove any feature or limit, or stop the service entirely, at any time and without notice, to keep the service available or to protect it. There is no service level, uptime commitment or support. No one gets priority, and there is no paid tier.

5. Outputs

Audio and files produced through the API or MCP service are covered by the same Content license as the website: free to use for any purpose, and music you write is yours. Rendered files are temporary (see Privacy); download what you need.

Outputs are generated by software from the notes you or your assistant provide. We do not review them. You are responsible for what you ask for and for how you use the audio, subject to the Content license. We do not use song text or audio that pass through the service to train any model. We do not keep the request text; rendered audio files are deleted automatically about 2 hours after creation, and anyone with the download link can fetch a file until then.

Your assistant platform's own terms and privacy notices also apply to your use of that platform. We are not responsible for what a platform sends to us, stores or shows you.

6. No warranty

The API/MCP service is provided "as is". We do not promise it will be available, accurate or fast. See the Terms of Use for the full disclaimer and limitation of liability.

7. Reporting

To report abuse or a security problem, write to moose@moosetracker.app. To report a copyright concern, see Copyright.

Contact: moose@moosetracker.app.