Playground
Run any Segmind model in the browser: the compose dock, one-click settings, up to three generations at once, the session strip, and editing the raw request as JSON.
Every model page has a playground. It is the fastest way to find out what a model does before you write a line of code, and it calls exactly the same API your integration will — so a result you get here is a result you can reproduce.
Open segmind.com/models, pick a model, and you land on its Playground tab. History, API and Pricing sit alongside it, and the estimated time for one run is shown on the right.
Screenshot coming soon
The compose dock stays in view on the left; results fill the canvas on the right
/images/platform/playground-compose.webp
The compose dock
Everything you need to start a run is in one panel that stays put while you work.
| Control | What it does |
|---|---|
| Prompt | The main text input. The placeholder is written for the model in front of you, so it is worth reading once. |
| Expand prompt editor | Opens the prompt fullscreen — the one to use for scene-length prompts and scripts. |
| Ask Pixxe | Hands your prompt to an assistant that rewrites it, and can suggest parameter values to match. |
| Image input list | Attaches reference images. Filled tiles show the filename, so you can tell several references apart. |
| More input options | The inputs that do not fit on the face of the dock. |
Two controls reshape the workspace itself: drag the divider between the dock and the canvas to resize either side, and use Maximize dock or Move inputs to the bottom when a model has more parameters than fit comfortably beside the output.
Settings are pills, not dropdowns
The common enum and boolean parameters render as pills under the prompt — aspect ratio, size, output format, and whatever else the model exposes. Selecting one opens a short list with a tick against the current value and a Clear option to fall back to the model's default. It is one click to change, and the current value is readable without opening anything.
Running
Press Generate. The run goes through the same asynchronous path the API uses, which is what makes the next three things possible.
Up to three generations run at once. Fire a second and a third while the first is still going; they run in parallel. At the limit the Generate button is disabled and explains why — "Up to 3 generations can run at once. Wait for one to finish." — rather than silently ignoring the click.
The session strip tracks them all. A row of chips labelled This session appears above the canvas as soon as you start a generation, one chip per run, each counting up while it works and turning into a thumbnail when it lands. Select any finished chip to bring that result back on screen. The strip stays hidden until there is something to put in it.
A run survives the page. Navigate away and come back, or refresh mid-run, and the playground reconnects to the job and picks up where it left off — the chips keep counting from where they were. You do not need to keep the tab still to keep a long generation.
Video coming soon
Composing a prompt, running three generations in parallel, and jumping back to a finished result from the session strip
https://segmind-resources.s3.amazonaws.com/docs/platform/playground/tour.mp4
Screenshot coming soon
Three runs in flight at once, tracked by the session strip
/images/platform/playground-session-strip.webp
Reading the output
The canvas renders the result in its native form, with a download control anchored to it:
- Images appear at full size; a request that returns several arrives as a gallery.
- Video plays at its true aspect ratio — portrait 9:16 fills the player properly rather than being letterboxed into landscape.
- Multi-clip output, such as a job that returns a set of short clips, shows a main preview plus a filmstrip of the whole set, each clip playable and downloadable on its own.
- 3D output from image-to-3D models is rendered in a viewer rather than
dumped as raw
.plyor.splatdata.
Screenshot coming soon
Multi-output jobs arrive as a gallery rather than a single first result
/images/platform/playground-gallery.webp
Editing the request as JSON
Edit request as JSON opens the exact payload the playground is about to send. Change anything in it — including parameters the form does not surface — and the form updates to match. A validator under the editor reads Valid JSON or Invalid JSON as you type, and Format and Minify tidy the body.
This is the quickest way to try an advanced parameter before committing it to code, and the JSON you end up with is the JSON you can paste into your own request.
Screenshot coming soon
The raw request, editable, validated as you type
/images/platform/playground-json-mode.webp
Get API code does the other half of the job: it hands you the same request as a runnable snippet. The model's API tab has the full reference, with synchronous and asynchronous examples per language.
Restricted models
If your team's admin has restricted a model, it carries a Restricted badge with a lock icon and the Generate button is disabled — on the model page, in PixelFlow, and in search. You find out before you compose a prompt rather than after you press Generate. See Teams for who can set this.
The classic layout
Switch to classic interface returns the playground to its previous layout, and the choice is remembered in your browser. Use it if you prefer the older arrangement while the current design settles.
Playground runs are billed exactly like API calls and appear in Generations alongside them, tagged with Web as their source. If you are comparing spend, that filter is what separates experimenting from production traffic.