Segmind Release Notes (August 17–23, 2026)

1. New Model — Google Lyria 3 Music Generation

• What's new: Google Lyria 3 is live on the API. lyria-3 generates a 30-second clip and lyria-3-pro generates a full song, both returning MP3. In the playground, sung lyrics are rendered in time with the playhead — the current line highlights as it plays and you can click any line to seek to it — and the example output shows the lyrics before you generate anything.
• Impact: Generate original music with vocals from a prompt, and follow the lyrics against the audio instead of listening blind to work out what the model sang.
• Released: August 23, 2026

2. Seedance 2.5 — 1080p Output

• What's new: Seedance 2.5 gains a 1080p (10-bit) output tier, available on both the v1 and v2 endpoints.
• Impact: Render Seedance 2.5 clips at 1080p without stepping outside the same request you already use.
• Released: August 18, 2026

3. Seedance — Audio On by Default and Forgiving Input Handling

• What's new: generate_audio now defaults to true on Seedance 2.x, so a request that omits the flag comes back with audio rather than a silent video. Input images that fall outside the accepted size range are auto-resized by default. When a reference image conflicts with first/last-frame control, frame control now wins and the request returns a warning — an X-Warning header on v1, a warning field on v2 — instead of failing outright; this applies across the whole family (2.0, 2.0-fast, 2.0-mini and 2.5). In the playground, the input dock now shows only the input modes that are valid together, so frame-control and reference-media tiles no longer appear side by side.
• Impact: Fewer rejected requests and fewer surprises — an oversized reference image or a slightly over-specified request now runs and tells you what it did, instead of returning an error you have to decode.
• Released: August 18–20, 2026

4. Clearer API Errors — Authentication, Async, and gpt-image

• What's new: A 401 now names the actual cause rather than returning one generic "invalid or expired" message — for example, a key sent as Authorization: Bearer is never checked, and the response now says so. Failed v2 async requests surface the real upstream error instead of an opaque placeholder response. On the gpt-image side, a png output_format no longer returns a 400, and the gpt-image-1 family returns its moderation results instead of discarding them.
• Impact: When a request fails, the response tells you what to change — the wrong auth header, the real provider error, the actual moderation outcome — instead of leaving you to guess.
• Released: August 19–21, 2026

5. Cost Analytics and Inference History by Team Member

• What's new: Cost Analytics adds a Member filter that rescopes the entire page — total cost, request count, projected month-end and every chart — with per-member costs reconciling exactly to the team total. Console inference history (request history and generations) gains the same member filter, plus a "Requested by" row in the request detail sidebar. On the API, GET /request-metrics accepts user_id and user_email filters, and GET /team/get-details returns each member's user_id. Both the member filters and the metrics filters are available to team admins.
• Impact: Team admins can answer "who spent what" for any teammate across cost, requests and history, in the console or straight from the API.
• Released: August 19–20, 2026

6. Team Model Access Controls

• What's new: The team model catalog and blacklist endpoints now take an explicit team_id rather than inferring one from the caller's workspace, and the team settings "Edit access" dialog and Model Providers page pass the team id from the route.
• Impact: Team admins can set team-wide and per-member model restrictions again, on the right team, instead of running into a failed model catalog load.
• Released: August 22, 2026

7. Pixelflow — Reliable Runs, Legacy Migration, and Clearer Errors

• What's new: Published workflows with a multi-input Output node now return every connected wire, and a run that fails partway returns its partial results. Every execution path, including the WebSocket path, now runs through a single execution engine with publish as the only gate. Opening a workflow built in the old console now prompts you to convert it or open it read-only, instead of migrating and autosaving in the background — conversion is atomic and keeps a copy of the original — and legacy graphs no longer open with blank parameter panels. A published API URL now resolves back to the graph it belongs to, team-membership checks work for every member, and a workflow that won't open because of the active workspace now says exactly that.
• Impact: Published workflows return the outputs you paid for, legacy workflows migrate on your terms, and a workflow you can't open tells you why instead of showing one generic loading error.
• Released: August 20–23, 2026

8. Platform — Sign-In Reliability, Accurate Pricing, and Console Consistency

• What's new: Sign-in now mints a fresh verification token on every attempt, and a rejected verification shows a "we couldn't verify that request" notice on the console login page instead of leaving you signed out with no explanation. Email login lands on the current console, and a stale session cookie that could shadow the real one is now cleared. Model pages show correct usage-based pricing for models priced dynamically from your inputs, such as Grok Imagine video, so the quote on the page matches what you are billed. Across the console, the three dashboards share the same filters, presets and date caps, and the generations view explains the 31-day range limit rather than returning an empty result.
• Impact: Sign in without getting stuck, trust the price shown on a model page before you call it, and move between console dashboards without re-learning the filters.
• Released: August 20–23, 2026