Skip to content

Selective revision guide

Regenerate one panel without restarting the entire comic.

The regeneratePanel action targets a pageIndex and panelIndex within an existing generation and can include a focused panelPrompt plus reference images for the replacement.

Selective regeneration limits the revision surface, but it does not edit pixels deterministically or guarantee that every surrounding visual detail remains identical. Compare the replacement against the approved page.

Inspect panel regeneration

Account, API key, usage, and billing open on LlamaGen.AI.

Direct answer

The decision this page is for.

Last verified:

Regenerate one panel by PATCHing an existing generation with action regeneratePanel, the current pageIndex and panelIndex, and a focused panelPrompt. Optional reference images can add context; the replacement still needs comparison and approval.

Verifiable request

Replace the third panel on the first page

cURL
curl -X PATCH \
  https://api.llamagen.ai/v1/comics/generations/gen_abc123 \
  -H "Authorization: Bearer $LLAMAGEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "regeneratePanel",
    "pageIndex": 0,
    "panelIndex": 2,
    "panelPrompt": "Keep the rainy street and courier. Move the parcel into the courier’s left hand.",
    "images": ["https://cdn.example.com/signed/courier-reference.webp"]
  }'

Structured response

State your application can route

response.jsonILLUSTRATIVE
{
  "id": "gen_abc123",
  "status": "LOADING"
}

Revision walkthrough

Repair one panel while reviewing the page around it.

The proof comparison makes panel selection, a bounded revision prompt, continuity review, and approval tangible.

A comic editor holds marked and revised page proofs to compare one repaired rainy bicycle panel in context
Editorial illustration generated with AI; it is not a customer photograph and not a generated API result.Art direction · European technical ligne claire

Revision loop

Preserve the approved page and make one bounded replacement.

A selective repair is trustworthy only when the application records the original, the requested change, the returned replacement, and the approval decision.

  1. 01Reviewer

    Identify the defect

    Describe one observable failure such as the wrong hand, missing prop, broken costume, or unsafe caption.

  2. 02Application

    Resolve the indexes

    Read the current generation data and map the reviewed page and panel to their numeric indexes.

  3. 03Server

    Send a bounded prompt

    PATCH regeneratePanel with the target indexes, one precise change, and only the references needed for that panel.

  4. 04Reviewer

    Compare versions

    Check the requested fix plus identity, background, lighting, lettering, and transitions into adjacent panels.

  5. 05Publishing or fulfillment system

    Record approval

    Keep the accepted asset and revision reason; stop when the product's retry or review limit is reached.

Capability and boundary facts

Facts an integration can verify.

Last verified:

Operation
PATCH /v1/comics/generations/{generationID}
Action
regeneratePanel
Target fields
pageIndex and panelIndex
Revision context
panelPrompt and optional images
Verification
Contract checked against the LlamaGen OpenAPI file on 2026-10-28

Good fit

Use it when

  • Repairing one continuity or composition failure
  • Preserving already approved panels
  • Merchant and creator approval workflows

Wrong fit

Do not use it for

  • Pixel-perfect inpainting guarantees
  • Changing the full story arc
  • Retrying indefinitely without usage and approval limits

Production limits

Plan for the boundaries.

  • 01Confirm indexes against the latest stored generation response before patching; stale page state can target the wrong panel.
  • 02A replacement can alter composition, lettering, anatomy, lighting, or continuity beyond the requested detail.
  • 03The public contract documents 402 and 429 responses; do not promise that selective regeneration is free or unlimited.
  • 04The example response is illustrative contract data, not a recorded regeneration result.
  • 05Generation is asynchronous; production interfaces must handle processing and failure states.
  • 06Outputs should be reviewed against product, brand, safety, and print requirements before delivery.
  • 07You must have the rights to prompts, photos, scripts, and reference assets submitted to the API.

Authoritative sources

LlamaGen Comic API documentationLlamaGen OpenAPI contractCurrent pricingTermsService status

Questions

Direct answers before you integrate.

01Which fields target the panel?
Use pageIndex and panelIndex from the latest generation data. Resolve them at review time so a stale interface does not patch the wrong panel.
02Does panel regeneration preserve the rest of the page exactly?
It limits the requested revision to one panel, but it is not deterministic pixel editing. Review composition, character identity, props, lighting, lettering, and transitions to adjacent panels.
03Is selective regeneration free?
Do not assume that. The operation documents billing and rate-limit response classes. Check current LlamaGen pricing and usage before defining revision allowances.

Related evaluation paths

FormatCharacter Consistency API for Multi-Panel ComicsUse caseComic API for Indie Creators and Serialized ComicsUse casePrint-on-Demand Comics from Ecommerce Orders

Next step

Move from evidence to a real API request.

LlamaGen provides the playground, API key, usage, billing, and authoritative service documentation.

Inspect panel regeneration