list_characters

pro.aicut/aicut · Verify this server

Returns the characters saved on this aicut account, newest first, one page at a time: `kind: "uploaded"` entries the user created from their own photos, and `kind: "cast_member"` entries generated as AI Video Story cast. Each carries an id, a display name, a portrait `image_url` where one exists, and (for cast members) the visual `world` it was authored in. WHEN: the user wants to reuse an existing character ("use my character", "same cast as last time"), or you want to show what characters the account already has before generating something character-based. This tool only READS the library; it creates nothing and spends nothing. `world` DOES NOT IDENTIFY THE SERIES, and nothing on these rows does. A cast member is stored with its visual world (`fruits`, ...) and that world is shared by many series, so a library of fruit characters cannot be sorted back into the series each was written for. THE CONSEQUENCE IS A MONEY ONE: 'use the same cast as last time' cannot be answered from this list alone. Never pick members for a story create by matching `world` to the series - name the candidates to the user (by `name`, and by portrait where the client renders one) and let them confirm, or draft a fresh cast with `generate_cast`, which is free. A wrong pick is only discovered after the frames have been drawn and charged. WHAT EACH KIND CAN DO TODAY: `cast_member` ids are what `generate_story_video` takes as `cast_member_ids`. A cast member's portrait `image_url` is usually one of this account's own generated images and can then also be passed into `generate_*` media fields (e.g. as an image-to-video source); members built on a series' stock preset image carry a shared preset url instead, which those fields refuse. `uploaded` characters are LIST-ONLY on this surface for now - no generate tool consumes them, and their portrait urls are refused by the media fields; use them in the aicut webapp. Paging: pass `cursor` from the previous response's `next_cursor` while `has_more` is true. 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.