US and EU.
In the team workspace sidebar, the label is Playground under the Library section. That sidebar entry opens the standalone playground page in a new tab.
What the page shows
The page has two main sections:| Section | What it is for |
|---|---|
| Generation section | Build a request, send it to the BabySea public /v1/generate API, and inspect the response |
| Management section | Run content-management calls for an existing generation_id |
Top bar
The top bar includes these controls:| Element | What it does |
|---|---|
Playground label | Shows that you are in the playground page |
| Image and Video tabs | Switch the model list and request schema between image and video models |
| Model selector | Opens a searchable dropdown of available model identifiers |
| Region switcher | Switches between US and EU playground regions |
| API key field | Accepts your BabySea API key |
| API key lock button | Locks the current API key in memory and enables request sending |
Main layout
In desktop view, the generation section uses three resizable columns:| Column | Header |
|---|---|
| Left | Schema |
| Center | Request Body |
| Right | Response |
| Mobile tab | What it shows |
|---|---|
schema | The current endpoint schema |
input | The request form |
response | The live response panel |
How the playground works
Choose the model type and model identifier
Use Image or Video, then pick a model from the searchable model selector.
Enter and lock your API key
Paste your BabySea API key into the top-bar field, then click the lock button. The generation and management send buttons stay disabled until the key is locked.
Fill the request form
The playground builds the form from the current model schema and highlights required fields.
Send the public API request
The page sends your request directly to the BabySea public
/v1 API for the selected region.Public and internal routes used by the page
| Route type | Route |
|---|---|
| Public generation route | POST /v1/generate/image/{model_identifier} or POST /v1/generate/video/{model_identifier} |
| Public content info route | GET /v1/content/{generation_id} |
| Public cancel route | POST /v1/content/generation/cancel/{generation_id} |
| Public delete route | DELETE /v1/content/{generation_id} |
| Internal status helper | GET /api/playground/generation-status/{generation_id} |
/api/playground/generation-status/{generation_id} route is used only to improve the live timeline after a generation has started. It is not a public API integration route.
Next steps
- Generate - Send image and video requests and understand the response timeline
- Request & schema - Use the schema panel, request form, field types, and validation rules
- Manage content - Get info, cancel a generation, or delete content by
generation_id