> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genviral.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Studio AI

> Generate AI Studio images and videos through Partner API with model parity, credits parity, and canonical video polling.

Use Studio AI endpoints to generate images and videos with the same model catalog and credit rules used in-app.

All routes are key-scoped and use the standard Partner API response envelope documented in [Response Pattern](/api-reference/response).

## Endpoints

| Endpoint       | Path                                          | Docs                                                          |
| -------------- | --------------------------------------------- | ------------------------------------------------------------- |
| List models    | `GET /api/partner/v1/studio/models`           | [Get Studio Models](/api-reference/get-studio-models)         |
| Generate image | `POST /api/partner/v1/studio/images/generate` | [Generate Studio Image](/api-reference/generate-studio-image) |
| Generate video | `POST /api/partner/v1/studio/videos/generate` | [Generate Studio Video](/api-reference/generate-studio-video) |
| Video status   | `GET /api/partner/v1/studio/videos/{videoId}` | [Get Studio Video](/api-reference/get-studio-video)           |

## Polling Flow

1. Call `POST /studio/videos/generate`.
2. Store `data.video_id`.
3. Poll `GET /studio/videos/{videoId}` until `data.status` is `succeeded` or `failed`.
4. Use `data.output_url` once status is `succeeded`.

## Input Contract

Studio generation endpoints use normalized partner input (`snake_case`) with optional `raw_params` for model-specific passthrough:

* `params`: stable normalized keys (`aspect_ratio`, `duration_seconds`, etc.)
* `raw_params`: optional advanced passthrough object

This keeps client payloads consistent while still allowing model-specific controls.