Deezer tags AI music: what to keep from a Sume Music job

Deezer tags fully AI-generated tracks and removes them from recommendations and editorial playlists. What a Sume Music job returns and what record to keep.

4 min readSume
All posts

Deezer's newsroom says it explicitly tags fully AI-generated music for listeners and removes detected AI tracks from algorithmic recommendations and editorial playlists. If you publish Sume Music output as a track, expect that tag to apply if the detector flags it, and plan for distribution without recommendation reach. Sume does not control Deezer's detection; what it gives you is a clear job record of how the audio was made.

What Deezer says

The figures below are from Deezer's July 2026 newsroom post.

Deezer statements, read 2026-10-02
TopicWhat the page says
TaggingAI music explicitly tagged for listeners as of June 2026
RecommendationsDetected AI tracks removed from algorithmic recommendations and editorial playlists
VolumeAbout 90,000 fully AI-generated tracks per day, over 50% of uploads at the June 2026 peak
FraudUp to 85% of streams on fully AI tracks identified as fraudulent in 2025 and demonetized

What a Sume Music job gives you

POST /v1/music-router/generate returns an audio artifact (audio/mpeg hosted on media.sume.com) and, when present, result.lyrics. job.request.routed_model names the engine that produced it. Price is $0.125 per accepted generation.

Keep the job id, the prompt and routed_model with the file. If a distributor or platform asks how a track was produced, you can answer from your own records.

import os, requests

r = requests.post(
    "https://api.sume.com/v1/music-router/generate",
    headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}",
             "Idempotency-Key": "track-ledger-001"},
    json={"prompt": "A 90-second ambient piano bed. Instrumental."},
)
job = r.json()
print(job.get("id"), job.get("request", {}).get("routed_model"))

Where AI tracks still fit

Background beds for video, podcasts and ads do not depend on streaming-service recommendations. For those uses, the Deezer policy is mostly irrelevant. If your goal is streaming-platform discovery, assume a fully AI track will be labelled.

Worked example

A simple record-keeping routine costs almost nothing.

  • Store the job id, prompt and routed_model in your asset sheet.
  • Save the audio artifact itself; do not rely on a hosted URL alone.
  • Note the date, since platform policies change.

Checklist before you commit

If you plan a release, read your distributor's AI rules as well as Deezer's. Deezer's page describes its own platform only.

  • Decide whether the track is a video bed or a release.
  • Tag AI-made tracks in your own catalog.
  • Do not claim a human performed what a model generated.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume