Chaptershift

Generate an AI portrait for a character in the project's picture style. Costs credits. The portrait is stored on the character and shown in the Chaptershift app. The new portrait is shown to the user in an inline panel that renders everything in `display` — don't describe display.picture_url or tell the user to open it; only share the link if they explicitly ask for the file.

Start AI cover generation (background job — poll with get_cover_status). Uses the project's premise, title, genre, and picture style. Costs credits; a failed generation is not charged. The finished cover is set on the project and shown in the Chaptershift app.

Generate an AI picture for a location as it looks at a scene of the timeline (omit for the start of the story), attached to one of its change records (get change ids from get_location). Costs credits; the picture appears in the Chaptershift app. The new picture is shown to the user in an inline panel that renders everything in `display` — don't describe display.picture_url or tell the user to open it; only share the link if they explicitly ask for the file.

A character's full sheet: every attribute group and their insights. Their portrait is shown to the user in an inline panel that renders everything in `display` — don't describe display.picture_url or tell the user to open it; only share the link if they explicitly ask for the file.

The story's core elements: premise, genre, central conflict, plot outline, point of view, world definition.

The project's current cover, displayed to the user in an inline panel. The panel already renders everything in `display` — don't describe display.picture_url or tell the user to open it; only share the link if they explicitly ask for the file. When there is no cover yet, generate one with generate_cover.

Poll the status of a cover generation job (idle | generating | completed | failed).

A location's state as of a scene of the timeline (omit for the start of the story) plus its change history — change ids anchor record_* edits and generate_location_picture. The inline panel already renders everything in `display` — don't describe display.picture_url or tell the user to open it; only share the link if they explicitly ask for the file.

The location hierarchy as of a scene of the timeline (omit for the start of the story). Use get_location for one location's full state and change history.

The book's structure review: the issues it found, from the story as a whole down to single scenes, each with what is wrong (`problem`) and a way to fix it (`direction`). `open` holds the issues to work on, highest level first: story, threads, rhythm, scenes. An issue's `status` and `latest_update` say what the latest review that judged it said, `new` until one has. An issue in `open` whose `state` is `addressed` has been marked handled by the writer, until the next review clears the mark. `kept` holds the issues the writer marked deliberate, with their `kept_reason`. These two lists are the only issues the marks apply to. `left` lists what the last review found fixed or no longer applying. `on_hold` lists the issues waiting on another one (`waits_on_title`) or, with none named, on the story. `brief` says what changed since the review before. `stands_at` is the level the last review stood at, the highest with open issues when it ended. `stopped_at_story` means it found the story itself doesn't work yet, and reviewed nothing below it. `status` is `running` while a review works on the book. A `failed` review leaves the previous result in place.

A scene in full (summary, participants, beat spine) plus its place in the structure and the state of its location.

The drafted prose of a scene, one section per active beat (empty when nothing has been drafted yet). A skipped beat has no section, even when it was drafted before being skipped.

The project's prose style profile (register, sentence style, narrator voice, audience, devices, avoidances, character voice notes); null when not set up yet.

The story order: every scene once, in timeline order, with its free-text time label (positions are 0-based). Different from list_scenes' reading order, which follows the acts and slots.

List your book projects with their ids — the entry point for every other tool.

The manuscript's chapter grouping — each chapter with its resolved scene ids, plus act titles.

List the project's characters with ids, the protagonist flag, and one-line summaries.

The book's reading order: Act I, II and III, each listing its nine canonical slots (filled or empty) and its extra scenes, in order.

Make this character the protagonist. The current protagonist, if any, loses the flag in the same operation — there is at most one per book.

The writer's mark that an open issue is handled: set it when the writer says so. The issue stays in `open`, marked, until the next review clears the mark. reopen_issue takes the mark back.

The writer's mark that an open issue points at something they intend, so the story stays as it is. `reason` is the writer's reason, in their words. The issue moves to `kept`, and later reviews don't judge it again and respect the reason. reopen_issue takes the mark back.

Move a scene in story order: `position` counts the other scenes only, 0 = first. Every scene moves, canonical included, and the reading order is untouched — use move_scene for a reading-order move.

Move an extra scene to a position in any act. Canonical scenes never move.

Record an in-story (diegetic) change to a location at a scene of the timeline — e.g. damage, renovation, renaming. History before that scene is untouched.

Record that a location ceases to exist in-story at a scene of the timeline (destroyed, demolished…). It remains part of the world's history before that scene — this is not a data deletion.

Save (or clear, with empty content) the prose for one scene beat. A skipped or removed beat has no section: the save fails with section.not_found until the beat is restored (its previous prose, if any, is still in storage).

Save the full chapter grouping: each chapter names the scene id it starts at, in reading order. Populated acts the list leaves uncovered get untitled chapters.

Save the project's prose style profile (replaces the whole profile; set is_draft=false when it is final).

Set the free-text time label on a scene's timeline entry. It carries no semantics and is never judged; an empty string clears it.

Update the central conflict driving the story.

Merge attribute groups into a character (only the groups you provide are touched).

Change a character's insights one by one: set, add or remove, each by id.

Update the genre (free-text label, e.g. 'Thriller', 'Dark Fantasy').

Update the plot outline (exposition, inciting incident, rising action, dilemma, climax, denouement).

Update the book-level narrative point of view, and through whose eyes a single_character book is told (omit pov_character_id for the protagonist).

Update the story premise.

Update a scene. Only the fields you include are changed — omitted fields keep their current values (no need to resend the whole scene). Explicit null clears point_of_view, pov_character_id or location_id. pov_character_id (whose eyes the scene is told through) must be one of the scene's participants; removing that participant clears it. Write beats with `beat_changes`, one entry per beat you touch, by the beat ids get_scene returns: `set` changes a beat's label, description or skipped flag, `insert` adds an extra beat after `after_beat_id` (null = first), `remove` drops an extra beat. Canonical beats are skipped, never removed.

Rename a book project.

Update the world definition. time_period and world_type are always required; the optional fields (world_rules, cultural_context, atmosphere_keywords) keep their current values when omitted — explicit null clears them.

The Chaptershift account behind this connection and whether it can use these tools.