How These Pages Stay Accurate
Who publishes the Aimusicis documentation, which statements are checked against the code that runs the service, what is produced at render rather than written, and how to report an error.
Aimusicis is operated by the team reachable through the contact page and at support@aimusicis.com. This page explains how the documentation and the tool pages are kept true, because a claim a reader cannot check is worth less than a number they can.
Numbers are pinned to the code that charges them
Every figure on the pages below is compared, by an automated test, against the configuration the service actually runs. If a price, a credit cost, an upload cap or a quoted error message changes in the code and the page is not updated, the test fails and the site cannot be built.
- Credits and Plans — every credit cost, plan grant, pack size, price and the per-tier concurrency ladder.
- Formats and Limits — accepted upload formats, size and length caps, the generator's model versions, and what a separation returns.
- Generator Inputs and Style Tags — every control on the AI Music Generator form and the style-tag groups.
- Errors and What to Do — every quoted message is the exact string the interface shows.
- Who Can See What You Generate — each statement about privacy is pinned to the code that enforces it.
- Account Security and Sign-in — how long the sign-in history goes back.
- Generate Sound Effects — the prompt length, tempo range, keys and cost.
- Text to Speech and Speech to Text — the text and recording limits, the voice count, the speech model and both rates, including the worked examples.
- AI Images and Videos — the credits for every image and video model at each resolution.
- Music Video Types and Export — the visualizer's templates, the price of a story clip on every clip model at each resolution, how many characters and locations a story video takes, the price of a scene redo, and the AI singer video's rate a second and its section length.
The same discipline applies to the pricing page: a card may list only rights the plan-rights table grants, every plan's stated generation count must equal what its credits buy, and the commercial-use licence row appears only on the plans that carry it, with the same price the licence dialog charges — see Commercial license.
Some passages are produced, not written
A few sections are generated from the site's own catalogues at build time, so they cannot drift from the source they describe:
- The "How many credits does this use?" answer on each tool page comes from the credit table.
- The related-tools links, the tool index on each hub page, and the middle step of every breadcrumb come from the tool-cluster catalogue.
- Every page's markdown twin (
.md) is serialised from the same content as the HTML page.
What is deliberately not claimed
The pages avoid statements the code cannot back: there is no invented download cap, no round-the-clock support promise (support is staffed on business days), and no testimonial without a verifiable source.
Reporting an error
If a statement disagrees with what the product does, use the contact page and name the page. Corrections change the source, so the fix reaches every locale and the markdown twin together.