pixelkiln 0.92.2 → 0.92.3

package/docs/ENDPOINTS.md

@@ -62,7 +62,9 @@ more than planned or finishes in a shape PixelKiln cannot read.
 14 are mock only (`objectPro` base, state and `pro` animation, `1dir`, Pro
 `terrain`, `uiAsset`, `uiElement`, Pro and Pro Flash character bases, states,
 portraits, outfit transfer, `interpolate`, `edit-animation`), and their rows
-say so.
+say so. Since then `objectPro` base, `uiElement`, `interpolate` and
+`edit-animation` have each run live (November 2026), but without a palette, so
+the palette claim on them is still mock only.
 
 **Free acceptance probe** (November 2026): for 13 of those 14 routes, a request
 carrying only a valid four-colour `target_palette` and none of the required
@@ -95,13 +97,13 @@ not probed.
 | `POST /correct-pixelart` | revision `correct-pixelart` | Measured live | 0.1 generations at 32×32 ([Cleanup tier, measured](#cleanup-tier-measured)). | Larger canvases and multi-frame sets, as above. | Low |
 | `POST /unzoom` | `pixelkiln unzoom` | Unknown | "Cost unmeasured; PixelLab's MCP tool description claims 0.1" ([Cleanup tier, measured](#cleanup-tier-measured)). Nothing records a live run. | Everything. | Low |
 | `POST /normal-map` | revision `normal-map`, `pixelkiln normal-map` | Measured live | An 8-frame 1304×26 strip and a 64×64 revision each billed 0.5; the map comes back the input's size with matching alpha ([Normal map](#normal-map-post-normal-map-measured-once), October 2026). | The `directx` convention; strips near the 32-frame limit. | Low |
-| `POST /generate-ui-v2` | `uiElement` | Schema only | Documented 10 to 25; "no call has been billed yet" ([GENERATORS.md](./GENERATORS.md#uielement)). Planned on the 10/15/25 ladder. `target_palette` sent, mock only. | The price, and the completed-job shape (`pollUiElement` reads it defensively); the concept-image path. | High |
+| `POST /generate-ui-v2` | `uiElement` | Measured live | A 32×32 call billed 10 and the review page showed 64 candidates at 32×32 (November 2026, Tier 3; the plan said 1 candidate and now follows `uiElementCandidateCount`). Planned on the 10/15/25 ladder ([GENERATORS.md](./GENERATORS.md#uielement)). `target_palette` sent, mock only. | Other sizes (the 15 and 25 tiers and the other candidate bands, which come from PixelLab's published grid), and the concept-image path. | High |
 | `POST /create-1-direction-object` (+ `GET /objects/{id}`) | `1dir` | Measured live | A 32px, 3-description `batch` billed 20 (the pre-cut floor) and `item_descriptions[0]` owned slot 0 ([Candidates](#candidates)); candidate counts follow size. `target_palette` sent, mock only. | No bill since the October 2026 cut (10 / 15 / 25 is PixelLab's published ladder); tiers above the floor under `item_descriptions`. | High |
 | `POST /objects/{id}/select-frames` | `1dir` and `batch` pick | Run live, not measured | Promoted three candidates in the live batch run ([Candidates](#candidates)); `indices` is plural. | Its cost was not recorded. | Low |
 | `GET /objects?limit=&offset=` | `adopt`, `salvage` | Measured live | Free; a March 2026 sprite still resolved four months on ([Object lifecycle](#object-lifecycle)). | None recorded. | Low |
-| `POST /create-object-pro-flash` | `objectPro` base | Mock only | Assumed to price like `character` pro-flash: 6 at 64px, 1 from a `reference` ([GENERATORS.md](./GENERATORS.md#objectpro), "Cost is not independently measured"). `target_palette` sent, mock only. | Price, completed-job shape, 8-direction output. | Medium |
-| `POST /objects/{id}/states` | `objectPro` state | Mock only | Same assumption. `target_palette` sent, mock only. | Price and shape. | Medium |
-| `POST /objects/{id}/animations` | `objectPro` animation (`v3`, `pro`) | Mock only | Same assumption; `pro` mode is documented 10 to 25 per direction. `target_palette` sent on `pro` only, mock only. | Price, shape, per-direction billing. | High |
+| `POST /create-object-pro-flash` | `objectPro` base | Measured live | A 32px base billed 6 and returned 8 files at 32×32 (the rotations), matching the plan, which prices it like `character` pro-flash (November 2026, Tier 3; [GENERATORS.md](./GENERATORS.md#objectpro)). `target_palette` sent, mock only. | Other sizes and the 1-generation `reference` path. | Medium |
+| `POST /objects/{id}/states` | `objectPro` state | Mock only | Assumed to price like `character` pro-flash; the base ran live, this route did not. `target_palette` sent, mock only. | Price and shape. | Medium |
+| `POST /objects/{id}/animations` | `objectPro` animation (`v3`, `pro`) | Mock only | Same assumption as the state row; `pro` mode is documented 10 to 25 per direction. `target_palette` sent on `pro` only, mock only. | Price, shape, per-direction billing. | High |
 | `PATCH /objects/{id}/tags`, `PATCH /characters/{id}/tags` | tagging in `fetch`, `adopt`, `salvage` | Unknown | Only the negative is documented: pixflux, pixen and bitforge results "cannot be tagged" ([Object lifecycle](#object-lifecycle)). | A recorded live call. | Low |
 | `DELETE /objects/{id}`, `POST /objects/{id}/dismiss-review`, `DELETE /characters/{id}` | `salvage`, account cleanup | Unknown | Not discussed in the docs. | A recorded live call. | Low |
 | `DELETE /characters/{id}/animations` | replacing a loop's direction | Unknown | "Deleting one direction of a shared group has not been run live" ([Skeleton-driven motion, measured](#skeleton-driven-motion-measured)). | Whether the rest of the group keeps its motion. | Low |
@@ -123,12 +125,12 @@ not probed.
 | `POST /characters/{id}/portrait` | `character` portrait attach | Measured live | Free (`usage.generations: 0`); the reply holds the only copy of the stored URL ([Characters, measured](#characters-measured)). | None recorded. | Low |
 | `POST /transfer-outfit-v2` | `character` outfit | Measured live | A 2-frame 92×92 job billed 20 (before the cut); frames return inline in `last_response.quantized_images` ([Characters, measured](#characters-measured)). `target_palette` sent, mock only. | Other frame counts (2 to 16) and canvases; the price after the cut. | High |
 | `GET /characters/{id}`, `GET /characters?limit=&offset=` | `adopt`, `fetch --refresh`, `salvage` | Measured live | Free; carries no `usage`; image URLs carry `?t=<updated_at>` ([Object lifecycle](#object-lifecycle)). | None recorded. | Low |
-| `POST /animate-with-text-v3` | revision `animate` | Schema only | Request fields from the OpenAPI document; the completed-job shape is a guess ([REVISIONS.md](./REVISIONS.md#animation-and-interpolation)). Cost borrows `character`'s v3 formula. | Price, completed shape, frame-list field. | High |
-| `POST /animate-pixminimax` | revision `animate-pixminimax` | Schema only | Same as above. PixelLab's MCP now prices it by time (64×64 at 4 / 8 / 16 / 40 frames: 1 / 1 / 2 / 6); the placeholder gives 1 / 1 / 1 / 3 ([roadmap](../skills/pixelkiln/references/pixellab-roadmap.md), "Generated effects with PixMiniMax"). | Price, completed shape, and whether the input frame is in the output. | High |
+| `POST /animate-with-text-v3` | revision `animate` | Measured live | A 64×64, 4-frame call billed 1 and returned 5 frames at 64×64 (the input frame plus 4); the plan, which borrows `character`'s v3 formula, said 1 (November 2026, Tier 3; [REVISIONS.md](./REVISIONS.md#animation-and-interpolation)). | Other sizes and frame counts (up to 16 frames at 256px reads 16 by the borrowed formula). | Medium |
+| `POST /animate-pixminimax` | revision `animate-pixminimax` | Measured live | 64×64 at 8 frames billed 1 and returned 9 frames at 64×64 (the input frame plus 8); at 16 frames billed 2 and returned 17. The plan said 1 for the 16-frame call because its old placeholder under-read; it now follows PixelLab's published table (64×64 at 4 / 8 / 16 / 40 frames: 1 / 1 / 2 / 6), see `pixMiniMaxCost` (November 2026, Tier 3; [roadmap](../skills/pixelkiln/references/pixellab-roadmap.md), "Generated effects with PixMiniMax"). | 40 frames and other sizes are unbilled (the table is PixelLab's, not a bill); `enhance_prompt`'s 0.05 is the schema's number. | Medium |
 | `POST /animate-with-skeleton-v3` | revision `animate-skeleton` | Measured live | 8 frames at 64×64 billed 3 and returned 8 frames at 64×64; `description` and `action` are both required, and sent with neither the endpoint returns 422 ([Skeleton-driven motion, measured](#skeleton-driven-motion-measured), October 2026). | Other frame counts (3 = 2 and 15 = 4 are PixelLab's anchors, unbilled). | Low |
 | `POST /estimate-skeleton` | `pixelkiln estimate-skeleton`, gallery pose helper | Run live, not measured | Ran on a 64×64 sprite before the 8-frame revision ([REVISIONS.md](./REVISIONS.md#skeleton-driven-animation)). | Its cost; the reply's `usage` is typed `unknown`. | Low |
-| `POST /interpolation-v2` | revision `interpolate` | Schema only | No usage example in the schema; price borrows the 10/15/25 Pro tiers ([REVISIONS.md](./REVISIONS.md#interpolate-between-two-keyframes)). `target_palette` sent, mock only. | Price, completed shape. | High |
-| `POST /edit-animation-v2` | revision `edit-animation` | Schema only | Same; priced on the packed frame grid (four 32×32 frames price as 64×64). `target_palette` sent, mock only. | Price, completed shape. | High |
+| `POST /interpolation-v2` | revision `interpolate` | Measured live | A 64×64 start sprite with a `lastFrame` keyframe and the default frame count billed 10 and returned 14 frames at 64×64 (November 2026, Tier 3; [REVISIONS.md](./REVISIONS.md#interpolate-between-two-keyframes)). The planner said 25, a 2.5× over-read, and now prices the canvas on the 10/15/25 ladder. `target_palette` sent, mock only. | Canvases above 65536px² (15 and 25 tiers, unbilled) and other frame counts. | High |
+| `POST /edit-animation-v2` | revision `edit-animation` | Measured live | One text edit of a 9-frame 64×64 set billed 10 and the edited set was accepted into review (November 2026, Tier 3). The planner said 25 and now prices the packed grid (nine 64×64 frames: 192×192) on the same ladder. `target_palette` sent, mock only. | Larger sets and canvases, where the packed grid crosses 65536px² (unbilled, assumed to follow the ladder). | High |
 | `POST /vfx`, lite artist, no sprite | `pixelkiln vfx --description`, `vfx` block `description` | Measured live | One effect billed 1 (balance 5104 to 5103); 163×26, 8 frames, sheet and atlas cut into 8 correct frames ([VFX artist](#vfx-artist-post-vfx-measured-once), October 2026). | The `files` shape (list or map) is undocumented; PixelKiln reads three. | Low |
 | `POST /vfx`, sprite, pro artist, `effect_id` change or `game_pack` | same | Mock only | Quoted from the OpenAPI table: pro 6 (8 with a sprite), 14 and 28 for larger sprites; plans count twice the quote ([VFX artist](#vfx-artist-post-vfx-measured-once)). | Every variant above. | High |
 | MCP `tools/call` `vfx_workbench` at `api.pixellab.ai/mcp` | `pixelkiln vfx`, `vfx` block `preset` or `recipe` | Measured live | Free on a subscription; same recipe re-rendered byte-identical; exports a sheet, GIF, atlas and optional game pack ([VFX workbench (MCP only), measured](#vfx-workbench-mcp-only-measured), October 2026). | "Busy, retry" is the only recorded error; sprites by asset are not wired. | Low |
@@ -145,29 +147,29 @@ The High and Medium rows that are Mock only, Schema only or Run live, not
 measured, most exposed first. A live run of the top ones also settles the most
 uncertainty per generation.
 
-1. **`/animate-pixminimax`** (Schema only). The estimate under-reads long
-   clips (a 40-frame 64×64 clip costs 6, the placeholder says 3), so `--budget`
-   can be set too low, and the completed shape is a guess.
-2. **`/interpolation-v2` and `/edit-animation-v2`** (Schema only). Priced from
-   borrowed 10/15/25 tiers with no usage example; a whole frame set goes in one
-   call, so a miss is a full Pro tier, and the finished job is read defensively.
-3. **`/animate-with-text-v3`** (Schema only). Up to 16 generations a call by
-   PixelKiln's own formula, billed per animation, completed shape guessed.
-4. **`/objects/{id}/animations`, `/create-object-pro-flash`, `/objects/{id}/states`**
-   (Mock only). `objectPro` assumes `character` pro-flash prices; its `pro`
-   animations are 10 to 25 per direction.
-5. **`/generate-ui-v2`** (Schema only). 10 to 25, never billed, shape read
-   defensively.
-6. **`/animate-character` template and v3** (Run live, not measured). One job
+1. **`/objects/{id}/animations`, `/objects/{id}/states`** (Mock only).
+   `objectPro` assumes `character` pro-flash prices; the base ran live and
+   matched (6 at 32px), but its `pro` animations are 10 to 25 per direction.
+2. **`/animate-character` template and v3** (Run live, not measured). One job
    per direction, so an 8-direction loop is eight bills no one has recorded.
-7. **`/create-character-state`** (Run live, not measured). One rough bill
+3. **`/create-character-state`** (Run live, not measured). One rough bill
    (about 22) taken beside other jobs and before the cut.
-8. **`/vfx` with a sprite, the pro artist, a change or a game pack** (Mock
+4. **`/vfx` with a sprite, the pro artist, a change or a game pack** (Mock
    only). Up to 28 generations a call, and plans reserve twice the quote.
-9. **`/edit-image-pro-flash`, `/inpaint-image-pro-flash`** (Mock only). 5 to 6
+5. **`/edit-image-pro-flash`, `/inpaint-image-pro-flash`** (Mock only). 5 to 6
    per call on provisional quotes, no completed response seen.
-10. **`/create-character-v3`** (Run live, not measured). 2 at 64px, up to 9 at
-    256px, and the one recorded bill was an unreadable zero.
+6. **`/create-character-v3`** (Run live, not measured). 2 at 64px, up to 9 at
+   256px, and the one recorded bill was an unreadable zero.
+
+Measured in November 2026 and no longer on this list: `/animate-pixminimax`,
+`/animate-with-text-v3`, `/interpolation-v2`, `/edit-animation-v2`,
+`/generate-ui-v2` and the `objectPro` base. Their remaining exposure is the
+sizes and frame counts the row says were not billed. Two of the planners were
+wrong: `interpolate` and `edit-animation` over-read 2.5× (25 planned, 10 billed)
+and `animate-pixminimax` under-read a 16-frame clip (1 planned, 2 billed). Both
+are now calibrated to those bills, and the PixMiniMax planner follows PixelLab's
+published points at 4, 8, 16 and 40 frames, which the 40-frame point has not
+been billed against.
 
 Also worth a second look because they are measured on an old price list: the
 `1dir`, `/portrait-character-pro`, `/transfer-outfit-v2` and `/edit-images-v2`
@@ -1068,15 +1070,15 @@ Listed so the gaps are known rather than assumed away:
   across every frame of a set) are wired the same way, as the `interpolate`
   and `edit-animation` modes; see
   [Interpolate between two keyframes](./REVISIONS.md#interpolate-between-two-keyframes).
-  All four are schema-only for the *request* (live OpenAPI document, not an
-  observed call); the *completed job* response shape is a genuine unknown —
-  no usage example exists for either endpoint at all, only the generic
-  background-job one — so `pollAnimateRevision` checks several plausible
-  field names defensively rather than assume one. Cost borrows `character`'s
-  own measured v3-loop formula as a placeholder, for the same reason
-  `objectPro` borrowed `character` pro-flash's; `interpolate` and
-  `edit-animation` borrow the 10/15/25 Pro canvas tiers instead, since
-  neither schema carries a usage example.
+  All four ran live in November 2026 (Tier 3): 64×64 PixMiniMax at 8 and 16
+  frames billed 1 and 2, `animate-with-text-v3` at 4 frames billed 1,
+  `interpolate` billed 10, and `edit-animation` of a 9-frame set billed 10.
+  Every completed job was read correctly. PixMiniMax returned the frame count
+  plus the input frame (9 and 17 frames); `interpolate` returned 14 frames at
+  the default count. Cost: `animate` borrows `character`'s measured v3-loop
+  formula; `animate-pixminimax` follows PixelLab's published table, which the
+  borrowed formula under-read; `interpolate` and `edit-animation` price the
+  canvas on the 10/15/25 Pro ladder (the planner had read them as 25).
 - `/generate-font-pro` (+ `GET /generate-font-pro/{job_id}`) — an 80-glyph
   atlas PNG plus a `.ttf` from a style description, `weight`
   (`Bold`/`Regular`), and `glyph_px` (8/16/32/64). Documented at 15

package/docs/GENERATORS.md

@@ -19,9 +19,9 @@ account; [ENDPOINTS.md](./ENDPOINTS.md) contains the detailed experiments.
 | Controlled pose/expression sequence in ComfyUI | `frames` | 0 `free` provider units | one atomic ordered set |
 | Animated GIF or spritesheet from Retro Diffusion | `animation` | $0.07–$0.25 per animation (published price) | 1 GIF or PNG sheet |
 | A character facing 4 or 8 directions, its poses, and its animations | `character` | 1 per base (standard), 10–25 per pose or portrait, 1 per template loop (2–4 as `skeleton-v3`), 20 per outfit (measured once) | one set of directions, one ordered loop, or one portrait |
-| A prop, creature, or vehicle with rotations, states, or loops but no character rig | `objectPro` | about 6 per base at 64px (unmeasured) | one set of directions, or one ordered loop |
+| A prop, creature, or vehicle with rotations, states, or loops but no character rig | `objectPro` | 6 per base (measured at 32px; about 6 at 64px) | one set of directions, or one ordered loop |
 | UI chrome — panels, buttons, health bars, toolbars | `uiAsset` | 20 generations (measured once, at 256x192) | 1 composited image |
-| One UI element from a description, 16px and up, optionally guided by a concept image | `uiElement` | 10–25 generations (unmeasured) | 1 image |
+| One UI element from a description, 16px and up, optionally guided by a concept image | `uiElement` | 10–25 generations (a 32×32 call billed 10) | 1 image |
 | A styled still on the Pro Flash model, or the south sprite a Pro Flash character will rotate | `imageProFlash` | 5–9 generations (PixelLab's provisional quote) | 1 image |
 | An animated effect (spell, hit, explosion, aura), on its own or around a sprite | `vfx` | free from presets and parts; 1–28 when described to PixelLab's artist (lite measured at 1; plans at twice the quote) | one ordered frame set |
 
@@ -288,11 +288,13 @@ and regenerating the parent makes the child stale.
 | portrait | portrait-character-pro | 10–25 by `size` (16px billed exactly 20 live, before the October 2026 cut) |
 | outfit | transfer-outfit-v2 | 20 (a 2-frame, 92×92 job billed exactly this live; not yet measured at other frame counts or canvases) |
 
-The 20–40 tiers are PixelLab's; the tier is resolved from the canvas when
-the job runs and reserved against the floor, so `plan` reports the tier the
-canvas lands in. `plan` prices a 64px state at 40 (the 1dir tier for that
-many pixels); one live 64px state in September 2026 moved the balance by
-about 22, so the estimate reads high, which is the safe side for a budget.
+The 10–25 tiers are PixelLab's (20–40 before its October 2026 cut); the tier
+is resolved from the canvas when the job runs and reserved against the floor,
+so `plan` reports the tier the canvas lands in. `plan` prices a 64px state at
+25 (the 1dir tier for that many pixels); one live 64px state in September
+2026, before the cut, moved the balance by about 22 against the then 20–40
+tiers, so there is no bill on the new list, and the estimate is read as high,
+which is the safe side for a budget.
 `poll` now reads what a job like this actually billed and records it
 alongside the estimate as `billed`; `pixelkiln history`, `plan --json`, and
 the gallery show both when they differ, though `gen`'s wave budget still
@@ -351,12 +353,13 @@ ignored, since none of them reach the API for an object.
   restricted to the fields above (no `template`/`subject`, since neither
   applies). See [Working with a cast](./CHARACTERS.md#working-with-a-cast).
 
-**Cost is not independently measured.** `objectProCost()` assumes
-`/create-object-pro-flash`/its state/its animation price identically to
+**Cost: the base is measured, the rest is assumed.** `objectProCost()` prices
+`/create-object-pro-flash`/its state/its animation identically to
 `character`'s own measured pro-flash formula (`proFlashCharacterCost`),
-since the request bodies are near-identical minus `template_id` — treat it
-as a working assumption, not a confirmed number, until checked against a
-live account.
+since the request bodies are near-identical minus `template_id`. A 32px base
+billed exactly 6 live (November 2026, Tier 3) and returned 8 files at 32×32,
+matching the plan. The state route, the `pro` animation and other sizes
+are still mock only; treat them as a working assumption.
 
 Adoption (`pixelkiln adopt`) has not been extended for `objectPro`'s own
 `<object id>#<animation group id>` remote-id scheme yet, unlike `character`'s
@@ -440,12 +443,13 @@ plain `revision` (image-to-image) of the base panel, which already carries
 this for every other generator.
 
 **Cost: confirmed live at one data point — 20 generations for a 256x192
-canvas**, the low end of the `create_ui_asset` MCP tool's "20–40
-generations" claim. PixelKiln still estimates with the same canvas-tier
-formula as `1dir`/`tiles`, which predicts the 40 ceiling for every valid
-`uiAsset` size (its 192px floor is already past that formula's top tier) —
-the measured call proves the formula wrong here, since it billed the floor
-price at an area well above where `1dir`/`tiles` would bill the ceiling.
+canvas**, the low end of the `create_ui_asset` MCP tool's then "20–40
+generations" claim (before PixelLab's October 2026 cut to 10–25). PixelKiln
+still estimates with the same canvas-tier formula as `1dir`/`tiles`, which
+predicts the 25 ceiling for every valid `uiAsset` size (its 192px floor is
+already past that formula's top tier) — the measured call proves the
+formula wrong here, since it billed the floor price at an area well above
+where `1dir`/`tiles` would bill the ceiling.
 Left as an over-read for `--budget` until a second size is measured; see
 [ENDPOINTS.md](./ENDPOINTS.md) for the full writeup.
 
@@ -529,15 +533,20 @@ to 16×16, which suits icons and small widgets:
 - `uiColorPalette` is sent as `color_palette`, the same free-text hint
   `uiAsset` takes. PixelLab removes the background by default; set
   `noBackground: false` on the style to keep it.
-- One call is expected to return one image, recorded straight away. If the
-  endpoint ever returns several, they go to candidate review like
-  `imagePro`'s.
-
-**Unmeasured.** The schema carries no usage example and no call has been
-billed yet. The plan prices it on the same 10/15/25 canvas tiers as
-`1dir`/`tiles`, the safe over-read for a Pro endpoint, and the completed
-job's shape is read defensively (`pollUiElement` names the keys it got if
-the shape is not the documented `images` list).
+- A small element returns many candidates (64 at 32×32, measured), which go
+  to candidate review like `imagePro`'s; a call that returns one image is
+  recorded straight away.
+
+**Cost: measured once.** A 32×32 call billed 10 live (November 2026, Tier 3)
+and the review page showed **64 candidates** at 32×32, which the plan said as
+1 until it followed the `/generate-image-v2` size tiers (`uiElementCandidateCount`:
+64 up to 32px, 49 at 33–35, 36 at 36–41, 25 at 42–50, 16 at 51–64, 9 at
+65–84, 16 at 85, 4 at 86–170, 1 above). Only the 32px point is a bill; the
+other bands are PixelLab's published grid. A size with more than one candidate
+goes to review. The plan prices the canvas on the 10/15/25 tiers as
+`1dir`/`tiles` do; other sizes are unbilled, and the completed job's shape
+is still read defensively (`pollUiElement` names the keys it got if the shape
+is not the documented `images` list).
 
 ## `vfx`
 

package/docs/PIXELLAB.md

@@ -77,9 +77,9 @@ unapproved files. See [Manifest quality profiles](./MANIFEST.md#quality-profiles
 | `imageProFlash` | You need a still on the Pro Flash model, optionally styled from one image, 16 to 256px | 5 to 9 generations (provisional quote) |
 | `vfx` | You need an animated effect (spell, hit, explosion, aura), on its own or around a sprite | free from presets and parts; 1 to 28 when described to PixelLab's artist (lite measured at 1) |
 | `character` | You need a character in 4 or 8 directions, with states, loops, portraits, or outfits | See [Characters](./CHARACTERS.md) |
-| `objectPro` | You need a prop or creature with rotations, states, or loops but no character rig | about 6 at 64px (unmeasured) |
+| `objectPro` | You need a prop or creature with rotations, states, or loops but no character rig | 6 per base (measured at 32px) |
 | `uiAsset` | You need a UI panel composited from pieces and named elements, 192px and up | 20 generations (measured once) |
-| `uiElement` | You need one UI element from a description, 16px and up | 10 to 25 generations (unmeasured) |
+| `uiElement` | You need one UI element from a description, 16px and up | 10 to 25 generations (a 32×32 call billed 10) |
 
 `map` accepts these values:
 

package/docs/REVISIONS.md

@@ -400,17 +400,20 @@ review** first (`pixelkiln pick`), not straight to downloadable output; there
 is no per-candidate choice to make (it is one ordered set, previewed as a
 loop), just accept or reject the whole thing.
 
-**Neither endpoint's completed-job response shape has been exercised against
-a live account.** The request fields above come from PixelLab's live OpenAPI
-document; the shape of a *finished* job (which key holds the frame list, and
-whether it's hosted URLs or inline base64) is an informed guess checked
-against several plausible shapes (see `pollAnimateRevision` in
-`src/providers/pixellab.ts`), the same defensive posture `pollRevision`
-already takes for `image-to-image`/`inpaint`. Cost is likewise unmeasured:
-`estimate()` borrows `character`'s own measured v3-loop formula
+**Both endpoints ran live in November 2026 (Tier 3), and every completed job
+was read correctly.** A 64×64 `animate` of 4 frames billed 1 and returned 5
+frames at 64×64; a 64×64 `animate-pixminimax` billed 1 at 8 frames (9 frames
+back) and 2 at 16 frames (17 back). PixelLab includes the input frame in the
+set, so a set holds the requested count plus one. `pollAnimateRevision` still
+checks several plausible field names defensively rather than assume one.
+Cost: `animate` borrows `character`'s measured v3-loop formula
 (`ceil(width × height × frames / 65536)`, since the request shapes are
-near-identical) as a placeholder, plus `enhancePrompt`'s own documented
-+0.05-generation surcharge, which is a real schema number rather than a guess.
+near-identical), which matched the one bill; `animate-pixminimax` follows
+PixelLab's published table (64×64 at 4 / 8 / 16 / 40 frames costs 1 / 1 / 2 /
+6), because that formula read the 16-frame clip as 1 against a bill of 2 (see
+`pixMiniMaxCost`; 40 frames is the published number, not a bill). Both add
+`enhancePrompt`'s documented +0.05-generation surcharge. Other sizes and
+frame counts are unbilled.
 
 ### Interpolate between two keyframes
 
@@ -468,10 +471,12 @@ time.
 
 `interpolate` and `edit-animation` land in candidate review like `animate`,
 take `fps` (defaulting to the parent's own rate when it has one, else 8), and
-reject `strength`. Neither has been exercised against a live account: request
-fields come from PixelLab's live OpenAPI document, the completed job is read
-by the same defensive frame-list lookup `animate` uses, and cost is an
-estimate (see [PixelLab](#pixellab) below).
+reject `strength`. Both ran live in November 2026 (Tier 3) and the completed
+job was read correctly by the same frame-list lookup `animate` uses: a 64×64
+`interpolate` with a `lastFrame` keyframe billed 10 and returned 14 frames at
+64×64, and an `edit-animation` of a 9-frame 64×64 set billed 10. The plan
+now prices them at those 10 (it used to read 25). Larger canvases are
+unbilled (see [PixelLab](#pixellab) below).
 
 ComfyUI supports none of the four frame-set modes: its revision path always
 writes a single output image, and an animation is a frame set — a structural
@@ -698,25 +703,24 @@ further — there is nothing to ask.
   image; a whole member set is still one call, but whether its price stays
   flat is unmeasured.
 - `interpolate` (`/interpolation-v2`) and `edit-animation`
-  (`/edit-animation-v2`) are both documented "Pro" endpoints with no usage
-  example in the schema and no live measurement. `estimate()` borrows the
-  same 10/15/25 canvas tiers the other unmeasured Pro edits use, sized on the
-  keyframe for `interpolate` and on the packed frame grid for
-  `edit-animation` (four 32×32 frames price as a 64×64 canvas, the 10 tier).
-  Over-reading is the safe direction for `--budget`; expect a live bill at or
-  below the plan.
+  (`/edit-animation-v2`) are "Pro" endpoints and bill on the 10/15/25 canvas
+  ladder (`proTierCost`: 10 up to 65536px², 15 up to 102400px², 25 above).
+  `estimate()` sizes the canvas on the keyframe for `interpolate` and on the
+  packed frame grid for `edit-animation` (nine 64×64 frames pack into
+  192×192). Measured live in November 2026: a 64×64 `interpolate` and a
+  9-frame 64×64 `edit-animation` each billed 10, where the plan used to say
+  25. Larger canvases are unbilled and follow the same ladder; over-reading
+  is the safe direction for `--budget`.
 - `animate` calls `/animate-with-text-v3`, `animate-pixminimax` calls
   `/animate-pixminimax` — both real async background jobs, unlike the two
   Cleanup-tier modes above, since they generate new frames rather than
   transform the source. Both take at most 256 pixels per side; `animate`
   additionally caps at 16 frames (`animate-pixminimax` allows up to 40). See
   [Animation and interpolation](#animation-and-interpolation) above for the
-  full field list, the frame-set output shape, and its own (still unmeasured)
-  cost caveat — unlike the Cleanup tier above, neither `animate` nor
-  `animate-pixminimax` has been exercised against a live account yet, and the
-  request/response shapes come from PixelLab's live OpenAPI document, not an
-  observed call. Treat the exact field names as provisional until a real
-  call confirms them.
+  full field list, the frame-set output shape, and the live bills: both ran
+  live in November 2026 (64×64 `animate` at 4 frames billed 1; `animate-pixminimax`
+  at 8 and 16 frames billed 1 and 2), and the completed jobs were read
+  correctly.
 - `animate-skeleton` calls `/animate-with-skeleton-v3`, also a real async
   background job, at most 256 pixels per side and 3-15 frames (the frame
   count comes from `keypointsFile`, not a manifest field). See

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pixelkiln",
-  "version": "0.92.2",
+  "version": "0.92.3",
   "description": "Manifest-driven pixel-art generation, review, recovery, and packaging with deterministic provenance.",
   "type": "module",
   "sideEffects": false,

package/skills/pixelkiln/references/pixellab-fidelity.md

@@ -46,7 +46,8 @@ Two engine-specific data points worth the same treatment:
   pro engine at the same canvas ("even at 256×256, we can generate eight
   animation frames, which we didn't have before even with the pro tools") —
   consistent with pixelkiln's documented `character` cost model, where v3
-  scales `ceil(size²×8/65536)` and pro sits in the flat 20–40 tier regardless.
+  scales `ceil(size²×8/65536)` and pro sits in the flat 10–25 tier regardless (20–40 before PixelLab's
+  October 2026 cut).
   Prefer v3 over pro for a loop unless pro's quality is specifically needed.
 - `portrait-character-pro` (not part of this adapter) renders sizes 128 and
   160 at "2K" internal resolution versus "1K" for 16–64, at a measured cost

package/skills/pixelkiln/references/pixellab-roadmap.md

@@ -153,11 +153,11 @@ and which tutorial(s) demonstrated real (not hypothetical) demand for it.
   rotation, states, or animation for a plain object. Closed by the
   `objectPro` generator; see `pixellab.md`. It reuses `character`'s own
   `asset.state`/`asset.animation` authoring shapes and mirror handling
-  rather than inventing parallel ones. **Cost is not independently
-  measured**: assumed identical to `character` pro-flash's own measured
-  formula, since the request bodies are near-identical minus `template_id` —
-  a real assumption pending a live check, not a confirmed number the way
-  `isometricTile`'s now is. Batch "pack" generation (N distinct objects from
+  rather than inventing parallel ones. **The base is measured**: a 32px
+  base billed 6 and returned 8 files (November 2026), matching `character`
+  pro-flash's formula, which the estimate assumes since the request bodies
+  are near-identical minus `template_id`. States and `pro` animations remain
+  that assumption pending a live check. Batch "pack" generation (N distinct objects from
   one call) is covered on `1dir` by its `batch` field — see below.
 - **Pixel correction** (`/correct-pixelart`, a dedicated cleanup pass distinct
   from `image-to-pixelart` — the latter is documented, docs/ENDPOINTS.md, as
@@ -209,17 +209,21 @@ and which tutorial(s) demonstrated real (not hypothetical) demand for it.
   `pixellab.md`. `lastFrame` covers both the "pin an ending pose" and the
   "chain from a prior animation's final frame" cases — it is just a
   manifest-relative image, which can be any earlier asset's own generated
-  output file. **Neither endpoint's cost or completed-response shape is
-  measured against a live account** — cost borrows `character`'s own
-  measured v3-loop formula, and the frame list is extracted defensively from
-  several plausible field names rather than one confirmed shape, the way
-  `pollRevision` already handles `image-to-image`/`inpaint`. The dedicated
+  output file. **Both ran live in November 2026**: `animate` at 64×64 and 4 frames
+  billed 1 (5 frames back, input included), `animate-pixminimax` billed 1 at 8
+  frames and 2 at 16 (9 and 17 frames back), and the completed jobs were read
+  correctly. `animate`'s cost borrows `character`'s measured v3-loop formula;
+  `animate-pixminimax` follows PixelLab's published table. The frame list is
+  still extracted defensively from several plausible field names. The dedicated
   **Interpolate** endpoint (`/interpolation-v2`, a separate "Pro" two-keyframe
   tool distinct from `last_frame` pinning on the animate endpoints above) is
   now wrapped too, as the `interpolate` revision mode (parent = start
   keyframe, required `lastFrame` = end keyframe), alongside
   `/edit-animation-v2` as `edit-animation` (one text edit across a whole
-  frame set). Both unmeasured, both borrowing the 10/15/25 Pro canvas tiers.
+  frame set). Both ran live in November 2026 and billed 10 each (a 64×64
+  `interpolate` returning 14 frames; an `edit-animation` of a 9-frame 64×64
+  set), on the 10/15/25 Pro canvas tiers; the planner used to read them as 25
+  and is calibrated. Larger canvases are unbilled.
   Real demonstrated demand for Interpolate: "Level Up Your Game: Custom
   Sprite Animation Tutorial" used it
   repeatedly, in Aseprite via PixelLab's own extension, as the fix for an
@@ -284,7 +288,8 @@ and which tutorial(s) demonstrated real (not hypothetical) demand for it.
   `/generate-ui-v2` ("Generate UI (Pro)": one element from a description,
   16px and up, with an optional concept image and palette hint), found on a
   later full read of the path list and now wrapped as the `uiElement`
-  generator; see `docs/GENERATORS.md#uielement`. Unmeasured. **Splitting into individual elements and
+  generator; see `docs/GENERATORS.md#uielement`. A 32×32 call billed 10 and
+  returned 64 candidates (November 2026). **Splitting into individual elements and
   nine-slice are not buildable at all**: `GET /ui-assets/{id}` returns one
   flat composited image with no per-piece sub-image or bounding-box data in
   its response schema, regardless of how many `pieces` the request declared.
@@ -303,10 +308,11 @@ and which tutorial(s) demonstrated real (not hypothetical) demand for it.
   this one. **Cost confirmed live, and it overturned the borrowed
   formula**: a real 256x192 call against a Tier 2 account billed exactly 20
   generations (balance 4979.8 → 4959.8), the low end of the `create_ui_asset`
-  MCP tool description's "20-40 generations" claim. No dedicated cost branch
+  MCP tool description's then "20-40 generations" claim (10-25 since the
+  October 2026 cut). No dedicated cost branch
   exists, so `uiAsset` still falls through to the same canvas-tier formula
   `1dir`/`tiles` use, which — given this generator's 192px floor — always
-  predicts the 40 ceiling; the measured call billed the floor price at an
+  predicts the 25 ceiling; the measured call billed the floor price at an
   area well past where that formula would bill the ceiling, so it does not
   actually describe `uiAsset`'s pricing. Left unpatched from one data point:
   over-reading stays the safe `--budget` direction, but a real call likely
@@ -542,15 +548,17 @@ missing:
 - **Trimming a loop's repeated frame.** The video deletes the last frame of
   a fireball loop because it repeats the first. `animate_image_pixminimax`
   says `get_image` returns `frame_count + 1` images with index 0 the input
-  unchanged. pixelkiln's frame extraction for this mode is unexercised live,
-  so whether the input frame lands in the set is unknown. There is no
-  manifest way to drop a frame either way.
-- **The cost estimate under-reads long clips.** The MCP tool now prices
-  PixMiniMax by generation time: 64×64 at 4, 8, 16, and 40 frames costs 1, 1,
-  2, and 6 generations. pixelkiln's placeholder,
-  `ceil(width × height × frames / 65536)`, gives 1, 1, 1, and 3 for the same
-  clips. Unlike every other unmeasured estimate here, this one under-reads,
-  so `--budget` can be too low.
+  unchanged. Confirmed live (November 2026): an 8-frame clip came back as 9
+  frames and a 16-frame clip as 17, with pixelkiln's frame extraction reading
+  all of them, so the input frame is in the set. There is no manifest way to
+  drop a frame.
+- **The cost estimate used to under-read long clips (fixed).** The MCP tool
+  prices PixMiniMax by generation time: 64×64 at 4, 8, 16, and 40 frames costs
+  1, 1, 2, and 6 generations. pixelkiln's old placeholder,
+  `ceil(width × height × frames / 65536)`, gave 1, 1, 1, and 3, and a live
+  16-frame clip billed 2 against a plan of 1. The estimate (`pixMiniMaxCost`)
+  now follows the published points and extrapolates above them; the 40-frame
+  point has not been billed.
 - **Joining two clips.** The video joins two orb animations end to end in
   Aseprite. pixelkiln has no frame-set concatenation; `lastFrame` can pin a
   clip's ending to another clip's frame file, but the two sets stay separate.

package/skills/pixelkiln/references/pixellab.md

@@ -26,11 +26,11 @@ providers, or before any PixelLab account operation.
 | `tiles` | Ground variations or connected structures | 10–25 generations |
 | `terrain` | A two-terrain Wang tileset for elevation (grass-to-water, floor-to-cliff), or a sidescroller platform set | Sidescroller **3**, measured. Pro **15** at 32px, measured (a connected second set also billed 15). Pro **25** at 64px and standard **3** measured too; standard plans at 4, the top of PixelLab's quoted 1–4 |
 | `imagePro` | A larger or non-square background/scene, or real style transfer; takes the style `palette` as a hard constraint | **10–25 generations** by canvas (64px billed 10; a flat 40 before October 2026) |
-| `character` | A character in 4 or 8 directions, its poses (`state`), its loops (`animation`), bust `portrait`s, and `outfit` transfers onto a loop | 1 per standard base, 6 per pro-flash base at 64px (1 from a `reference`), 20–40 per pose or portrait, 1 per template loop per direction (2–4 as `skeleton-v3`), 20 per outfit (measured once) |
-| `objectPro` | A prop, creature, or vehicle that needs rotations, states, or loops but has no character rig | 6 per base at 64px (1 from a `reference`), **unmeasured**; assumed to match `character` pro-flash |
+| `character` | A character in 4 or 8 directions, its poses (`state`), its loops (`animation`), bust `portrait`s, and `outfit` transfers onto a loop | 1 per standard base, 6 per pro-flash base at 64px (1 from a `reference`), 10–25 per pose or portrait (20–40 before the October 2026 cut), 1 per template loop per direction (2–4 as `skeleton-v3`), 20 per outfit (measured once, before the cut) |
+| `objectPro` | A prop, creature, or vehicle that needs rotations, states, or loops but has no character rig | 6 per base (billed 6 at 32px, November 2026; 1 from a `reference`, unmeasured); states and animations assumed to match `character` pro-flash |
 | `isometricTile` | One standalone isometric tile (a raised mesa, a cliff block), 16–64px | **1 generation, measured once** (32px `block`) |
-| `uiAsset` | A UI panel, button, health bar, or other chrome, from precise `pieces` and/or named `elements` | **20 generations, measured once** (256×192); the borrowed canvas-tier estimate still predicts 40 |
-| `uiElement` | One UI element (button, slot, bar, dialogue box) from the prompt, 16px and up, with an optional concept image | 10–25 generations, **unmeasured** |
+| `uiAsset` | A UI panel, button, health bar, or other chrome, from precise `pieces` and/or named `elements` | **20 generations, measured once** (256×192, before the October 2026 cut); the borrowed canvas-tier estimate still predicts the 25 ceiling |
+| `uiElement` | One UI element (button, slot, bar, dialogue box) from the prompt, 16px and up, with an optional concept image | 10–25 generations (a 32×32 call billed 10; 64 candidates at 32×32) |
 | `vfx` | An animated effect (explosion, aura, lightning, status icons) from a `vfx` block: a `preset` or `recipe`, `parts`, an optional `sprite` to build around; cut into an ordered frame set. Or a `description` (+ `artist`: `lite`/`pro`, a local PNG `sprite`) for PixelLab's paid VFX artist | workbench **free** (a renderer, not a model); `description`: lite 1–5, pro 6–28 by sprite size, billed up to 2× the quote, which is what plan counts (a lite effect with no sprite billed its quote of 1, measured once) |
 | `imageProFlash` | A styled still on the Pro Flash model (style image + `styleTraits`), 16–256px in multiples of 4; also the natural source for a Pro Flash character's south sprite | 5–9 generations, PixelLab's provisional quote |
 
@@ -243,11 +243,12 @@ target `south` — passing any other direction, or `directions` at all to the
 API for a 1-direction object, is what the endpoint itself 400s on.
 Regenerating an already-animated direction is simpler than `character`'s
 own "find and delete the prior take" dance: `/objects/{id}/animations` has
-its own `replace_existing` flag, which PixelKiln always passes. **Cost is
-not independently measured** — `objectProCost()` assumes it prices
-identically to `character` pro-flash's own measured formula
-(`proFlashCharacterCost`), since the request bodies are near-identical minus
-`template_id`; treat it as a working assumption pending a live check.
+its own `replace_existing` flag, which PixelKiln always passes. **Cost: the
+base is measured** (32px billed 6 and returned 8 files, November 2026) —
+`objectProCost()` prices it identically to `character` pro-flash's own
+measured formula (`proFlashCharacterCost`), since the request bodies are
+near-identical minus `template_id`. States and `pro` animations are still
+that assumption, pending a live check.
 `objectPro`'s own place in `pixelkiln adopt` is not modeled yet. (N distinct
 objects from one call, PixelLab's Object Creator "pack", is the `1dir`
 `batch` field above.) `pixelkiln gallery --edit` offers "+ New state" and
@@ -317,10 +318,11 @@ dedicated "state" mechanism — it is a plain `revision` (image-to-image) of
 the base panel, the same mechanism every other generator already has.
 **Cost: confirmed live at one data point.** A real 256×192 call against a
 Tier 2 account billed exactly 20 generations (balance 4979.8 → 4959.8),
-matching the low end of the `create_ui_asset` MCP tool's "20–40 generations"
-claim. No dedicated cost branch exists, so pixelkiln still estimates it with
-the same canvas-tier formula `1dir`/`tiles` use — which predicts the 40
-ceiling for every valid `uiAsset` size, since the 192px floor already clears
+matching the low end of the `create_ui_asset` MCP tool's then "20–40
+generations" claim (PixelLab cut it to 10–25 in October 2026). No dedicated
+cost branch exists, so pixelkiln still estimates it with the same
+canvas-tier formula `1dir`/`tiles` use — which predicts the 25 ceiling
+for every valid `uiAsset` size, since the 192px floor already clears
 that formula's own top tier. The measured call disproves the formula for
 this generator (it billed the floor price at an area where `1dir`/`tiles`
 would bill the ceiling), but the estimate is left as-is, an intentional
@@ -331,9 +333,10 @@ the prompt, no `pieces`/`elements` layout, sizes from 16×16 (up to 792 wide,
 688 tall, aspect-gated upstream). A style's one `styleImages` entry becomes
 the `concept_image` (design guidance); `uiColorPalette` is sent as
 `color_palette`. Reach for it over `uiAsset` for icons, slots, and small
-widgets under `uiAsset`'s 192px floor. Unmeasured: the plan borrows the
-10/15/25 canvas tiers, and the completed job's shape has not been observed
-live.
+widgets under `uiAsset`'s 192px floor. A 32×32 call billed 10 and returned
+64 candidates (November 2026); the plan borrows the 10/15/25 canvas tiers and
+counts candidates by size (`uiElementCandidateCount`), and sizes other than
+32px are unbilled.
 
 `imageProFlash` wraps `/create-image-pro-flash`, the Pro Flash model as a plain
 still: priced 5 up to 96px, 6 up to 208px, 9 beyond (PixelLab's own