Artlist's Lyria 3 Pro tracks: the same engine through Sume's router

Is Artlist's AI music the same as Lyria 3 Pro? Per Music Business Worldwide (read 2026-10-04), Artlist added Google's Lyria 3 Pro the day after Google announced it, and its AI Music category, built on Lyria 3 and Lyria 3 Pro, launched on March 26, 2026 according to coverage in the search results. It generates from text or up to 10 images and can make tracks up to three minutes long, with a commercial-use license included in Artlist's offering.

Sume's Music Router names the same two Google engines as routable ids, lyria-3.5 and lyria-3-pro, and sends requests with no model to sume/music-auto, which resolves to Lyria 3.5 today. The difference is the surface: Artlist is a creator app with a licence; Sume is an API that returns a file inside a job.

What Artlist reports

The MBW report and Artlist's own prompting guide are the sources for this post. I treat Artlist's licence terms as Artlist's alone; Sume's docs do not describe them and neither does this page.

Side by side

Pin the engine

Leave model off to let the router choose, or pass a routable id to pin one. Unknown ids fail with 400 model_not_found and a catalog_url, so a typo does not silently fall back.

import os
import requests

r = requests.post(
    "https://api.sume.com/v1/music-router/generate",
    headers={
        "Authorization": "Bearer " + os.environ["SUME_API_KEY"],
        "Idempotency-Key": "artlist-pro-001",
    },
    json={
        "model": "lyria-3-pro",
        "prompt": "[0:00-0:30] Intro: sparse piano. [0:30-1:30] Verse: add soft drums. Instrumental, no vocals.",
        "mode": "async",
    },
    timeout=60,
)
print(r.status_code)
print(r.json())

Which to use

Pick Artlist if you want its library, apps and licence in one subscription. Pick the Music Router if the track must come back as a file inside an automated pipeline: generate, cut, caption and render in one place. Either way, check the licence that applies to your use before you publish.