Understanding the 'Possibly AI' Badge

The "Possibly AI" badge means AI-related metadata was detected somewhere in the track's audio chain by one or more digital streaming providers (DSPs). It does not mean the track is fully AI-generated.

What "Possibly AI" means

When you see the Possibly AI badge on a track, it means a DSP-level AI-detection system flagged the release for containing AI-generated or AI-assisted content at some point in production.

This includes, but is not limited to:

  • 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. The badge is a binary indicator that AI was detected somewhere in the pipeline, not a detailed breakdown of how much AI was used.

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

What artist.tools checks — and what it does not

artist.tools is designed to answer: "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. These platforms expose track-level AI labels or catalog metadata that identifies AI-generated content.

artist.tools is not a forensic audio analysis tool. It does not listen to the audio or analyze spectral patterns, tempo, phase, or vocal characteristics. It only reports what DSPs have already flagged in their metadata. If you need a deeper, independent audio-based assessment, use a dedicated audio AI detector instead.

Alternative: SubmitHub AI Song Checker

For a third-party opinion that actually analyzes the audio itself, SubmitHub's AI Song Checker is a useful complement. It works differently from artist.tools:

artist.tools

SubmitHub AI Song Checker

Reads DSP metadata flags

Analyzes actual audio features (spectral and temporal)

Answers: "Did a DSP flag this?"

Answers: "Does this audio match AI-generated patterns?"

Binary: Possibly AI / No AI / N/A

Probability score across 21 audio features, with model-specific detection

Instant, metadata-based

Requires audio upload for best results; streaming links are less reliable

SubmitHub's detector checks 21 audio features across three categories: basic spectral properties, harmonic analysis, and long-range pattern analysis. It is trained on a dataset of AI-generated and human-made samples. It can also identify specific AI models, including ElevenLabs 2.0, Google Lyria 3, MiniMax Music, Mureka v8.0, and Treblo v3.0.

For the most reliable SubmitHub results, upload an original MP3, WAV, or FLAC file rather than pasting a Spotify or YouTube link. Compressed streaming samples and short previews reduce accuracy.

Read more about how it works: AI Song Checker: How It Works and v4.0 update.

What to do if your track is flagged

The most productive first step is to audit your production pipeline. The track has an AI audio signature or fingerprint somewhere in the chain, which may have come from:

  • A producer, engineer, or collaborator who used AI-assisted tools without disclosing it

  • AI stems or samples used in the arrangement

  • AI mastering or mixing plugins applied by a third-party service

  • Remixes or alternate versions that were generated or modified with AI

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.

Dispute the badge

If you have audited your production pipeline and believe the flag is still incorrect, 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. However, the audit is the more important step. If the DSP metadata is correct but the flag is real, the underlying classification will still exist on the streaming platforms regardless of what we display on artist.tools.

What an override does

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

Overriding the badge on artist.tools is best used when the DSP metadata is clearly wrong, or when you have already audited your production pipeline and confirmed that no AI tools were used. The real fix is correcting the signal at the source—updating your distributor metadata, or working with the DSP to clear the classification if it was applied in error.

Related badge states

Not all tracks return an AI signal. The badge can appear in three 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

Use the AI Song Checker tool on artist.tools to scan a specific track and see its current badge state.

When to contact support

Reach out if:

  • You have audited your production pipeline and confirmed no AI tools were used, but the badge still appears

  • The badge is on a track that predates AI music tools and you want to dispute it

  • You have questions about which DSP flagged the track and why

Include the track URL, the badge state, and any relevant production details when you contact us.

Was this helpful?