FAQ
Frequently asked questions
Straight answers about what the checker, API and audits do and don't do.
My distributor already validates. Why check first?
Distributor checks catch format errors at upload; style-guide problems (featuring in the title, version tags after a dash, search terms in titles, missing AI disclosure) often pass upload and get flagged or altered by the store later. The checker catches those before you deliver.
Which stores' rules do you check?
Rules cite Spotify (v2.2.0), Apple Music (2.4), the Music Business Association style guide (2.0), DDEX ERN 4.3.2, the ISRC Handbook and GS1, plus distributor and DSP help pages. Each finding shows its source.
What input do you accept?
CSV or pasted rows, and JSON or CSV via the API. Not DDEX XML, audio or artwork.
Do you check artwork, audio or genre taxonomies?
No. GENRE_MISSING only checks a genre is present; it doesn't map to store taxonomies.
How fast is it?
A typical release returns in about a second. Limits: 2 MB and 5,000 rows per check.
Is there an API?
Yes: POST /api/v1/check and GET /api/v1/usage. Starter is 10,000 tracks/month at 60 requests/min; Growth 100,000 at 300/min. Keys are issued on request.
Do you store my file?
No. The file is processed in memory. If you unlock the full report we keep your email, consent record and the report's summary counts.
Is a clean result a guarantee?
No. It means none of the 21 rules fired. Stores make the final call.
What if a store changes its guide?
We update the rule and its source, and log the change in the version history.