My track is flagged as AI-generated

The "Possibly AI" badge on a track means one or more digital streaming providers (DSPs) detected AI-related metadata in the track's audio chain. It does not mean the track is fully AI-generated. artist.tools mirrors this badge from DSPs — we do not create the classification ourselves.

This classification comes from DSP metadata, not artist.tools. We scan and mirror the AI content flags exposed by streaming platforms.

What "Possibly AI" means

The badge is a binary indicator that AI was detected somewhere in the production pipeline, including:

  • AI-assisted vocals

  • AI-generated instruments or stems

  • AI mastering tools

  • AI mixing or production elements

  • Fully AI-generated tracks

There is no distinction between these levels. A track flagged for AI mastering receives the same badge as a fully AI-generated track.

What artist.tools checks — and does not

artist.tools answers: "Has this track been classified as AI-generated by any of the DSPs I distribute to?"

We do not generate the AI classification ourselves. We scan DSP-level metadata from digital streaming providers, including Spotify, Apple Music, Tidal, Deezer, and many others. We do not listen to the audio or analyze spectral patterns, tempo, phase, or vocal characteristics. If you need a deeper, independent audio-based assessment, use a dedicated audio AI detector.

How to dispute the badge

Hover over the Possibly AI badge and click Wrong? Dispute. This opens our in-app support chat so you can start a conversation with our team. We can overwrite the rating on request if you are confident it is wrong.

Overriding or hiding the badge on artist.tools is visual only. It does not remove the AI flag from the DSPs where it was originally detected. If the DSP metadata still carries the AI classification, the underlying flag remains there and may reappear on other platforms or services that read the same data.

What you should do first

  1. Audit your production pipeline. Talk to your team, producer, or mixing engineer and trace exactly which tools, stems, or plugins were used at each stage. Even standard AI-assisted plugins can trigger the flag.

  2. If you are confident no AI tools were used and the DSP metadata is clearly wrong, contact our support team with the track URL and production details.

  3. If the flag is correct but you want to clear it, work with the DSP to update your distributor metadata or clear the classification at the source.

Related states

  • Possibly AI / AI — AI signals were detected in the audio chain

  • No AI signals found / No AI — no AI metadata or forensic indicators were detected

  • Could not verify / N/A — insufficient data or the track was not scanned

Need more help?

Contact support via the chat widget in the app or visit our Contact Support page. Include the track URL, the badge state, and any relevant production details.

Was this helpful?