Inline prompt boost, resizable prompt/form, final job price

[dawidope]

Three additions to the request form and the jobs list, plus what the live API actually does with each.

1. Inline prompt boost (enhance_prompt)

A Boost in request checkbox next to the prompt sends enhance_prompt with the generation request, so deAPI boosts the prompt as a pre-step of the job instead of rewriting the field first. The manual Boost button stays for the "rewrite it in the form, let me edit it" flow.

• Only four endpoints accept the flag (/images/generations, /images/edits, /videos/generations, /videos/animations) — the checkbox appears only there.
• Multipart sends 1, not "true" — Laravel's boolean rule rejects the string.
• The choice is remembered per endpoint.
• The boosted prompt comes back on the job status and opens from the row's ✨ boosted chip: original → boosted, with copy.

2. Prompt field / form sizing

• The prompt textarea fills the form panel (twice the slack of secondary text fields) and can be dragged to a fixed height, remembered per field, with a reset control. Grabbing the resize corner pins the current height first — flex-grow otherwise overrides whatever the browser's native resize sets, and the drag does nothing.
• A splitter under the form panel resizes the form against the jobs list (it was capped at 45vh), also persisted.

3. Final price

deAPI reports price {amount, is_estimated} once a request is terminal. It is persisted on the job and merged into the live row, so the badge shows the estimate while the job runs and the charged price after: one figure when they match, estimate struck through next to the final figure when they differ, and a ~ marker while a partner-model charge is still settling.

Billing: measured, not assumed

The /price endpoints do not accept enhance_prompt, so the boost fee is quoted separately at POST /prompts/enhancements/price (multipart, top-level {price}). The open question was whether that fee lands inside the job's price. Measured on the live API — balance before/after each request, with no-boost controls and repeats to beat background traffic on the account:

case	job price	balance delta	boost quote	residual
img, no boost (×2)	0.00190931	0.001909	—	−3.1e−07
img, boost, 3-char prompt	0.00190931	0.002335	0.000426	0.00042569
vid, boost, 33-char prompt	0.00245681	0.002888	0.000431	0.00043119
img, boost, 912-char prompt (min of 3)	0.00190931	0.002481	0.0005725	0.00057169

• price.amount equals the /price quote exactly, in every run, boosted or not — it covers the inference only.
• The boost is charged on top of it, and the amount charged equals what we quote (differences are within the ±1e−06 resolution of the 6-decimal balance).
• The fee scales with prompt length and does not depend on how long the boosted output is.

So the estimate compared against the final price is the base quote, and the boost is reported next to it as +$X rather than folded in — folding it in would show a phantom difference on every boosted job. Dev/sandbox environments quote the boost at 0, and there the badge is hidden.

Not covered

Partner models (is_estimated: true, where the charge settles after inference — the UI marks those with ~), refund behaviour when a job fails after a successful boost, and the 422 path for a model with no booster guide.

🤖 Generated with Claude Code