list_videos

pro.aicut/aicut · Verify this server

Returns the signed-in account's videos, newest first, one page at a time. WHEN: the user asks what they have made, or you need to find a video from an earlier session. This is the account's whole video library, so it includes videos made in the aicut web app and with products this API cannot yet create - not only ones generated through these tools. THIS IS HOW YOU FIND A STORY EPISODE, and every story tool needs its id. A row that is an AI Video Story episode carries `kind: "story_episode"` and `story_stage` - the same stage vocabulary `get_video` uses. Pass `kind: "story_episode"` to get only those. A plain generation carries neither field. READ `story_stage`, NOT JUST `status`, ON AN EPISODE. `frames_review` means the episode is WAITING FOR THE USER, not for the engine - it is where the run parks so they can look at the pictures, and it reports `status: "processing"` like anything else that has not finished, so on `status` alone it is indistinguishable from a job that is genuinely busy. `ready_to_render` means the scene videos are done and the final file has NOT been made yet; `rendered` means it has. The other values (`starting`, `generating_frames`, `generating_scenes`, `rendering`, `writing_failed`) mean what they say. `story_stage` is omitted, never guessed, when the episode has no engine run yet - read that one job with `get_video`. Paging: pass `cursor` from the previous response's `next_cursor` while `has_more` is true. `status` is one of `queued` (accepted, not started), `processing` (running), `succeeded` (the `url` field is a public link to the finished file), or `failed` (terminal - `error.message` says why, and nothing further will arrive). OUTPUT: this returns JSON for you to read. When you report back to the user, give them the media URL plus a one-line summary. Do not paste the raw JSON, job ids, or internal field names into the conversation.