Segmind Release Notes (May 25–31, 2026)

1. Expanded Multimodal Inputs Across LLM Models

What's new: Anthropic models (including claude-opus-4.7 and all Claude variants) now fully support the documented {prompt, image} and {prompt, pdf} payload format. OpenAI models now accept PDF and audio file inputs in addition to images. Gemini models now accept video and file inputs natively.
Impact: You can send PDFs, audio, and video directly to the corresponding models using Segmind's standard payload format — no need to hand-build complex messages arrays. If you were hitting validation errors with Anthropic models using the simple interface, those are fully resolved.
Released: May 28, 2026

What's new: The model playground on platform.segmind.com now lets you directly edit the raw API payload in JSON mode. Form mode and JSON mode stay in sync bidirectionally, and an inline validator highlights any JSON errors before you submit.
Impact: You can prototype and test custom API parameters without writing code — just switch to JSON mode, edit the payload, and run. Useful for exploring advanced parameters not exposed in the form UI.
Released: May 28, 2026

What's new: The maximum file size you can upload directly on the platform has been raised from ~6 MB to 2 GB.
Impact: Large video files, high-resolution images, and multi-minute audio clips can now be uploaded directly in the platform UI for use in your workflows — no more workarounds for large assets.
Released: May 28, 2026

What's new: When the Seedance 2.0 image-to-video provider is temporarily slow or unavailable, the API now returns a 503 with a Retry-After: 30 header instead of a hard 400.
Impact: Integrations that automatically retry on 503 will succeed once the provider recovers. Requests that return 503 are not charged. Previously these surfaced as 400 errors with no retry guidance.
Released: May 28, 2026

What's new: When a prompt is rejected by Responsible AI (RAI) content filtering on veo-3.1-fast, the API now returns a 400 with the specific filter reason included in the response body.
Impact: If your prompt triggers a content policy rejection, you now get an actionable error message explaining why — instead of a generic 500. This makes it much easier to iterate on prompts that run into content policy limits.
Released: May 28, 2026

What's new: PixelFlow workflows can now be shared directly to teams from the share modal. Use the Teams tab to select your team by checkbox, or paste a team ID to share with external collaborators.
Impact: Teams can now collaborate on shared workflows without passing links around manually. Useful for organizations where multiple members need access to the same automation.
Released: May 29, 2026