@slatesvideo/shared 0.5.6 → 0.5.8

package/skills/slates-prompting-seedance-2-5.md

@@ -0,0 +1,290 @@
+---
+name: slates-prompting-seedance-2-5
+description: How to prompt Seedance 2.5 and Seedance 2.5 Edit. Read before calling slates_generate_video with model seedance-2.5, or slates_edit_video with model seedance-2.5-edit. 2.5 is a SECOND SEAT next to 2.0, not an upgrade — it buys 30-second takes, 30 image references, audio-only references and INTEGER-SECOND TIMESTAMPS, and it gives up 1080p and 4K entirely. Timestamps are the one grammar difference that matters: 2.0 ignores them and answers only to shot numbers, 2.5 acts on them. Otherwise it shares 2.0's grammar (read slates-prompting-seedance for subject binding, camera and constraint vocabulary); this file covers what is different, plus the two hazards unique to 2.5 — the prompt-intent task classifier and the cost trap at 720p.
+---
+
+# Seedance 2.5 — prompting
+
+**Read `slates-prompting-seedance` first.** The prompt GRAMMAR is the same model family: the
+8-slot advanced formula, subject binding by `<Subject_N>@<Image_N>`, camera vocabulary,
+externalised emotion, inline constraint words, the anti-twin fix. None of it is restated here.
+This file is only what 2.5 changes — and the biggest change is that **2.5 acts on timestamps
+where 2.0 ignores them.**
+
+---
+
+## The one fact that decides whether you use it at all
+
+**Seedance 2.5 is 480p or 720p. There is no 1080p and no 4K, on any provider.**
+
+That is not a Slates limitation or a tier gate — the model does not produce those resolutions.
+So 2.5 does not replace 2.0; it sits beside it:
+
+| | Seedance 2.0 | Seedance 2.5 |
+|---|---|---|
+| Resolution | 480p / 720p / 1080p / **native 4K** | **480p / 720p only** |
+| Length | 4–15s | **4–30s in one take** |
+| Reference budget | 15 (9 image + 3 video + 3 audio) | **50 (30 image + 10 video + 10 audio)** |
+| Combined reference video/audio | ≤15s | **≤30s** |
+| Audio-only reference | ✗ (needs an image or video alongside) | **✓** |
+| **Timestamps in the prompt** | **✗ — ignored; shot numbers only** | **✓ — integer seconds, acted on** |
+| Multi-view image as ONE subject reference | ✗ (not recommended) | **✓ (up to 5 subjects)** |
+| Video edit as its own task type | ✗ | **✓ (`seedance-2.5-edit`)** |
+| Default video model | **yes** | no |
+
+**Route to 2.5 when the shot needs LENGTH, MANY REFERENCES, or an audio-only reference.
+Route to 2.0 when resolution matters at all** — which, for anything a client will see full-screen,
+is most of the time.
+
+---
+
+## 🚨 Hazard 1 — the prompt-intent task classifier
+
+This is the one that costs money and time, and it has no equivalent on 2.0.
+
+**Seedance 2.5 sorts every request into one of five task types** — text-to-video,
+reference-to-video, first/last-frame, **video edit**, **video extend** — from the reference roles
+attached **plus the intent of your sentence**. Each type then has its own parameter constraints,
+and a violation comes back **asynchronously**: the task queues, credits are reserved, and only then
+does it fail.
+
+The trigger words are ordinary English:
+
+| Reclassified as | Words that do it (ByteDance's own list) |
+|---|---|
+| **video edit** | `edit video` · `add` · `insert` · `remove` · `delete` · `modify` · `replace` · `change to` |
+| **video extend** | `extend forward` · `extend backward` · `continue` · `continue from` · `extend the story` |
+
+So a perfectly legitimate reference-to-video prompt — *"a wide shot of the workshop, **remove** the
+tripod from frame"* — gets classified as an edit and fails on constraints it never set.
+
+**What to do:**
+
+1. **If you mean to edit an existing clip, say so with the MODEL, not the sentence.** Call
+   `slates_edit_video` with `model: 'seedance-2.5-edit'`. That routes to a dedicated
+   task-typed endpoint and the classifier never has to guess.
+2. **If you mean a fresh shot, describe the finished frame rather than an instruction to change
+   one.** Not *"remove the tripod"* → *"the workshop bench, clear and uncluttered"*. Not
+   *"add rain"* → *"heavy rain falling through the streetlight"*. This is better prompting anyway:
+   the model renders what you describe, it does not take edits to an imagined draft.
+3. The trigger only fires when **references are attached**. A plain text-to-video prompt is safe
+   however it is worded.
+
+**Slates will warn you, and it will never rewrite your prompt.** When a 2.5 reference generation's
+prompt contains one of these words, the composer shows a warning that NAMES the words and the agent
+route returns the same string. Silently editing the user's sentence to dodge a provider classifier
+is forbidden — the words that reach the model are always the words the user can see.
+
+---
+
+## 🚨 Hazard 2 — 720p is not "the cheap one" any more
+
+Every other model in Slates trains the habit that lower resolution means lower cost. 2.5 breaks it,
+because the thing that moves the bill is **length**, and 2.5's length ceiling is double 2.0's.
+
+Worked, at the shipped rates:
+
+| Generation | Credits |
+|---|---|
+| 2.5 · 480p · 5s · faceless | 28 |
+| 2.5 · 720p · 5s · faceless | 59 |
+| 2.5 · 720p · 30s · faceless | 355 |
+| 2.5 · 720p · 30s · AI-face route | **484** |
+| 2.5 · 720p · 30s · consented real-face route | **710** |
+| *(for scale)* 2.0 · 1080p · 15s · AI-face route | 411 |
+
+**A 30-second 720p clip can cost more than a 15-second 1080p one** — and a base licence starts
+with 1,000 credits. Someone who reads "720p" as "cheap" and asks for a 30-second take on the
+real-face route has spent 71% of their welcome grant on one clip.
+
+**Discipline:**
+
+- **Always quote with `slates_estimate_generation_cost` before a take over ~10 seconds,** and say
+  the number out loud before generating.
+- **Draft at 480p and 4–8 seconds.** Prove the composition, the motion and the identity first;
+  spend the length only on the take you already know works.
+- **Length is a creative decision, not a default.** 30 seconds is available; it is rarely the right
+  answer for a single shot. Multi-shot storyboards inside one 30s generation are what the length is
+  actually for.
+- Read `slates-cost-discipline` — all of it applies, more sharply here.
+
+---
+
+## Timestamps — the one grammar change
+
+<!-- @inject:seedance-25-timestamps -->
+**2.0 does not respond to timestamps and answers only to shot numbers. 2.5 responds to
+integer-second timestamps.** That is ByteDance's own first line under "Differences from Seedance
+2.0", and it is why a 30-second take is usable at all: the length is only worth buying if you can
+say *when* things happen inside it.
+
+Both formats are valid on 2.5, and you can mix them — `Shot N` blocks for a storyboard whose
+pacing you are happy to leave to the model, timestamps when a beat has to land at a moment.
+
+**Three ways to control time, all first-party:**
+
+| Form | Write it like |
+|---|---|
+| **Interval** | `0-3 seconds… 3-7 seconds… 7-15 seconds` or `[1s-4s]… [4s-8s]… [8s-12s]` |
+| **Time point** | *"Quick left sideways transition at the 5-second mark."* |
+| **Relative** | *"After 3 seconds, everyone around him shakes their head."* · *"The frame freezes for 1 second after he presses the shutter."* |
+
+**The rules that come with them:**
+
+- **One second is the smallest unit.** Integers only — no `2.5s`, no frames.
+- **No gaps in the timeline.** `0-3s… 5-6s…` leaves 3-5s unspecified and the model fills it however
+  it likes. Intervals must abut: `0-3s`, `3-7s`, `7-15s`.
+- **Budget the plot to the seconds.** Too little content in a range and the model improvises to
+  fill it; too much and you get extra cuts or dropped beats. This is the actual craft of a 30s take.
+- **Never time-code a high-frequency action.** *"Shake your head three times per second"* is
+  explicitly called out as a misuse — timestamps schedule beats, they don't choreograph frames.
+- **Transitions want both halves:** the moment AND the method — *"At the 5-second mark, the camera
+  transitions leftward with a left wipe into a natural dissolve."*
+- **Timestamps work on an EDIT too**, and that is where they earn the most: they scope a change in
+  time as well as in content — *"Change the man's action from drinking coffee to mopping the floor
+  from 4-6 seconds in Video 1, and leave the rest of the content unchanged."* Without a range, a
+  whole-clip instruction is applied to the whole clip.
+
+Do **not** carry this back to 2.0, and do not carry Veo's `[00:00-00:02]` bracket syntax into
+either — 2.0 ignores time entirely, and the cross-model syntax swap is its own known failure.
+<!-- @end:seedance-25-timestamps -->
+
+---
+
+## What the extra reference budget is actually for
+
+30 image references (up from 9) does **not** mean "attach 30 images". Every rule in
+`slates-prompting-seedance` about references still holds — 2–4 strong references beat both
+extremes, and one reference per role.
+
+**Where 2.5 moves the ceiling, per ByteDance's own input recommendations:**
+
+| | Stable | Works, but expect re-rolls |
+|---|---|---|
+| Subjects bound by IMAGE reference | 1–8 | 9–12 |
+| Subjects bound by VIDEO or AUDIO reference | 1–5 | 6–10 |
+| Reference clip length, per subject | 5–10s | longer drops stability |
+
+**Multi-view images of one subject are supported on 2.5** — a turnaround sheet can be a single
+reference image, where 2.0 wanted one authoritative rendering per subject. Past **5 subjects**,
+go back to single-view images, one per view, rather than one image carrying several viewpoints.
+
+The larger budget earns its keep in exactly two places:
+
+- **A long multi-shot take** where different shots need different subjects and locations bound —
+  the budget is spread across the storyboard, not stacked on one frame.
+- **Video and audio references alongside images**, which is where 2.5's 10 + 10 matters far more
+  than the image count.
+
+### Audio-only references — the genuinely new input
+
+2.0 required an image or video alongside any audio reference. **2.5 accepts audio on its own.**
+That makes one recipe possible that was not before: drive a scene's timing, voice or ambience from
+a recording with no visual anchor at all — a voice line, a music bed, a room tone — and let the
+model build the picture to it. Cite it the same way as any other reference
+(`Reference the timbre in <Audio_N> to generate…`), and remember that audio references carry **no
+billing dimension** on any Seedance route: audio is included.
+
+### Video references
+
+Up to 10 clips, ≤30s combined (2.0: 3 clips, ≤15s). A reference VIDEO switches the cost key to
+`seedance-2.5*-vref-{res}-{T}s`, where **T = Σ input seconds + output seconds** — the sum is across
+**every** clip attached, not just the longest. Three 6-second references on a 12-second output bills
+30 seconds, not 12 and not 18. Quote before confirming.
+
+**The cap is a refusal, not a trim.** Attach an eleventh clip, or push past 30 combined seconds, and
+the composition is rejected before anything uploads. That asymmetry is deliberate: reference images
+warn-and-trim because dropping one doesn't change the price, and a dropped reference VIDEO would be
+one you were quoted for and the model never saw.
+
+### Mixing all three in one call
+
+50 files total (30 image + 10 video + 10 audio) is a shared budget. Everything is cited positionally
+by type — `image 1`, `video 2`, `audio 1` — in attachment order, so reordering the attachments
+renumbers the citations. Write the prompt against those numbers:
+
+```
+Marcus (image 1) performs the motion from video 1 in the workshop from image 2,
+speaking the line in audio 1. Preserve his identity, appearance and outfit.
+```
+
+Frames and reference media stay mutually exclusive, in every combination — the reference endpoint
+has no first/last-frame parameters at all, so this is a shape mismatch rather than a preference.
+
+---
+
+## Seedance 2.5 Edit (`slates_edit_video`, `model: 'seedance-2.5-edit'`)
+
+Its own picker row and its own op call, deliberately: the task type is **the model you chose**,
+never something inferred from your sentence.
+
+**Why route here at all:** it is the **only edit engine in Slates that accepts a clip longer than 15
+seconds** (4–30s, versus Kling O3 Edit's 3–15s and Omni Flash Edit's 3–10s). For a clip inside the
+others' range, choose on fidelity instead — Omni Flash Edit won the prompt-only head-to-head, and
+Kling O3 Edit is the one that takes element and style reference images.
+
+**How it behaves:**
+
+- **Output length follows the SOURCE clip**, and the bill is the ceiled source length. The provider
+  requires an automatic duration on this task type, so there is no length knob — the clip you attach
+  is the quote. The returned clip can differ from the source by up to ~0.3s, which only compresses
+  transition frames; a clip that 2.5 itself generated comes back at exactly its input length.
+- **Source clips under 20 seconds edit more reliably.** 4–30s is what the task type accepts;
+  ByteDance's own recommendation is to stay inside 20 for quality. A 28-second source is legal and
+  will need more attempts.
+- **The aspect ratio follows the source clip too.** No ratio control; the frame is the clip's frame.
+- **480p or 720p output**, native audio.
+- **Prompt and source clip only** on this op. The MODEL takes reference images on an edit
+  (ByteDance recommends 1–5 — *"replace the man in dark clothing in @Video 1 with @Image 2"*);
+  **Slates has not wired that path**, so today an edit that must lock an identity from a photo
+  goes to Kling O3 Edit. Constraint of our build, not of the model — worth revisiting.
+- **An edit bills roughly DOUBLE a plain 2.5 generation of the same length**, because every provider
+  charges an edit on input + output seconds. Read the confirm gate's number; do not reason from the
+  generation rate.
+- **Set `seedanceFace: true` when a character's face is visible in the clip.** The faceless provider
+  blocks faces outright — this is not a price optimisation, it is whether the job runs at all.
+- **There is no consented-real-face route for editing.** Real-person footage that the AI-face route
+  rejects has to go to Kling O3 Edit.
+
+**Prompting an edit** — the same discipline as every other edit engine: **describe only what
+changes.** The source already carries its composition, motion, timing and performance; re-describing
+them fights the model. Use Seedance's own edit grammar from `slates-prompting-seedance`
+(*"Strictly edit `<Video_1>`, and modify `<Original_Characteristic>` to `<New_Characteristic>`"*) and
+**never** write *"reference video 1"* in an edit — the official guide is explicit that this phrasing
+gets the request reclassified as a reference task, which is the same landmine as Hazard 1.
+
+Two things sharpen an edit prompt, both first-party:
+
+- **Say it as A → B, not as an outcome.** *"Change the man's action from drinking coffee to mopping
+  the floor"* beats *"the man mops the floor"* — naming what it currently is tells the model what
+  to overwrite.
+- **Timestamp a partial edit** — the edit task type reads the same integer-second timestamps the
+  generation path does. Rules and forms are in § Timestamps above; this is the single most useful
+  thing they buy.
+
+**Audio is editable too, and it is the least obvious use of this row.** The same op rewrites what
+is heard while the picture stays put: change a spoken line, change the accent, translate the
+dialogue and re-fit the lip movement, strip or replace the BGM or a sound effect. *"Only edit the
+man's dialogue in Video 1: change it to 'Don't come over here,' in an American accent"* is an edit,
+not a lip-sync job. Bill it like any other edit — on the source clip's length.
+
+---
+
+## Faces, and what does NOT change
+
+The three-tier face routing is identical to 2.0 — faceless → default route, an AI character's face →
+`seedanceFace: true` (the relaxed provider, a real cost premium), a real person's photo → the
+consent-gated premium route after a `[REAL_FACE_DETECTED]` rejection, with `realFaceConsent: true`
+set **only** after the user explicitly confirms they hold the rights to the likeness. The full rules,
+including why the real-vs-AI call is the provider's and not yours, are in
+`slates-prompting-seedance`.
+
+Also unchanged, and worth restating because 2.5's length makes each one more expensive to get wrong:
+
+- **One primary camera move per shot.**
+- **No lens / aperture / film-stock vocabulary.** That is image-model syntax and a Seedance
+  anti-pattern.
+- **No `negativePrompt` field** — constraints go inline, and 2.5 acts on negative phrasing in
+  exactly two dimensions: subtitles (*"no subtitles"*) and audio (*"no BGM; environmental and
+  action sounds only"*, *"no audio"*). Everywhere else, describe what you want, not what you don't.
+- **Legible in-shot text still belongs in a baked start frame**, not in the video prompt.

package/skills/slates-prompting-seedance.md

@@ -1,6 +1,6 @@
 ---
 name: slates-prompting-seedance
-description: How to prompt Seedance 2.0 (ByteDance video model). Read before calling slates_generate_video with model seedance-2. Seedance structures multi-beat prompts as a "Shot 1 / Shot 2 / Shot 3" storyboard against an 8-slot advanced formula — never per-second time stamps. Its syntax differs from Kling, Veo and the image models; don't cross-pollinate (in particular, no lens / aperture / film-stock vocabulary).
+description: How to prompt Seedance 2.0 (ByteDance video model). Read before calling slates_generate_video with model seedance-2. Seedance 2.0 structures multi-beat prompts as a "Shot 1 / Shot 2 / Shot 3" storyboard against an 8-slot advanced formula — never per-second time stamps, which 2.0 does not respond to (Seedance 2.5 does; see slates-prompting-seedance-2-5). Its syntax differs from Kling, Veo and the image models; don't cross-pollinate (in particular, no lens / aperture / film-stock vocabulary).
 ---
 
 # Seedance 2.0 — prompting
@@ -162,7 +162,7 @@ Seedance has **no `negativePrompt` field** — constraints go inline in this slo
 
 ## Worked examples `[official :1689-1745]`
 
-These are ByteDance's own end-to-end cases. Note the shape: an asset-binding preamble, then `Shot N` blocks in event order, then a trailing style + stability paragraph. No time stamps anywhere.
+These are ByteDance's own end-to-end cases. Note the shape: an asset-binding preamble, then `Shot N` blocks in event order, then a trailing style + stability paragraph. No time stamps anywhere — 2.0 does not respond to them at all, which is version-scoped and reverses on 2.5.
 
 **Example 1 — dormitory emotional short drama (dialogue-focused).** Assets: `@Image 1` half-body photo of the female lead · `@Image 2` dormitory scene reference · `@Video 1` camera-movement reference · `@Audio 1` indoor ambience.
 
@@ -202,7 +202,23 @@ These are ByteDance's own end-to-end cases. Note the shape: an asset-binding pre
 
 Reference-to-video accepts up to **9 reference images, 3 reference videos, 3 audio clips** `[official :275-281]`. Text+audio-only and audio-only inputs are not supported.
 
-**Mutually exclusive:** first-frame/last-frame mode CANNOT be combined with reference images. The error reads `"first/last frame content cannot be mixed with reference media content."` Pick one or the other. *(Official note `[:284]`: you can approximate first/last frames via prompt wording inside a multimodal call, but if the frames must be exact, use the dedicated first/last-frame route.)*
+**Mutually exclusive:** first-frame/last-frame mode CANNOT be combined with reference images. The error reads `"first/last frame content cannot be mixed with reference media content."` Pick one or the other. *(Official note `[:284]`: you can approximate first/last frames via prompt wording inside a multimodal call, but if the frames must be exact, use the dedicated first/last-frame route.)* The same rule covers reference VIDEO and AUDIO: they ride the reference endpoint, which has no frame parameters at all.
+
+### All three modalities go in ONE call
+
+The caps are a shared budget, not three separate features: **12 files total on 2.0** (9 image + 3 video + 3 audio), **15 seconds of reference video combined**, **15 seconds of audio combined**. On 2.0 an audio reference needs at least one image or video alongside it; 2.5 accepts audio on its own.
+
+Cite each by type and index, in the order they were attached — `image 1`, `video 1`, `audio 1`. The index is positional: reorder the attachments and the numbers move with them.
+
+```
+Marcus (image 1) performs the motion from video 1, in the workshop from image 2,
+speaking the line in audio 1. Preserve his identity, appearance and outfit.
+```
+<!-- slates-only -->
+**Attaching a clip is NOT the same as editing it.** "Add as reference" puts it in the composer alongside everything else and wipes nothing; "Edit with AI" makes the clip the canvas and clears the tray for a fresh instruction. Two different jobs, two different menu entries — never infer one from the other.
+
+**Over the cap is REFUSED, never trimmed.** A reference video is priced into the quote before it is sent, so a clip silently dropped after the quote would be a clip you paid for and the model never saw. Remove one and retry.
+<!-- /slates-only -->
 
 ### Motion transfer & lip-sync recipes (reference video / audio)
 

package/skills/slates-prompting-suno.md

@@ -1,110 +0,0 @@
----
-name: slates-prompting-suno
-description: How to prompt Suno in Slates. Read before calling slates_generate_audio with model suno. Full music tracks - EVERY call returns TWO variations for one flat price and duration is FREE up to 360 seconds. The rule that decides everything - in CUSTOM mode the prompt field is the EXACT LYRICS (sung as written), in DESCRIPTION mode it is a description and the lyrics get written for you. Covers the mode matrix, style vs prompt steering, instrumental scoring, negative tags, and the character caps.
----
-
-# Suno — prompting
-
-Full music generation, reached through the sunoapi.org wrapper. Models `V4`, `V4_5`, `V4_5PLUS`, `V4_5ALL`, `V5`, `V5_5`.
-
-**Two facts that should shape every decision:**
-
-1. **Every call returns TWO songs** — two genuinely different takes on the same brief, for one flat price. Audition both before re-rolling.
-2. **Length is free.** A 360-second track costs exactly what a default one costs (measured against the live provider balance 2026-07-31: a default call and a `duration: 240` call both debited the same). There is never a reason to generate a bed shorter than your edit.
-
-## Where it routes
-
-- **Anything a listener would call a song or a score** — theme, underscore, needle-drop, montage bed, end-card sting.
-- **NOT** ambience or room tone — that is `seed-audio`, which is cheaper and better at it.
-- **NOT** a single effect — that is `eleven-sfx`.
-- **AUDIO-ONLY.**
-
-## 🚨 THE RULE: which mode you are in changes what `prompt` means
-
-| `customMode` | `instrumental` | Required | What `prompt` means |
-|---|---|---|---|
-| `false` | either | `prompt` only (≤500 chars) | **A description.** Lyrics get written for you. |
-| `true` | `true` | `style`, `title` | **Unused.** Style + title do all the steering. |
-| `true` | `false` | `style`, `title`, `prompt` | **THE EXACT LYRICS**, sung as written. |
-
-Putting a description in the prompt field while `customMode: true` and `instrumental: false` gets your description **sung back at you**. This is the single most common Suno mistake and it costs a full generation every time.
-
-## Description mode — the fast path
-
-```
-customMode: false
-prompt: "brooding synthwave for a night drive, analog bass, no vocals, 90 bpm"
-```
-
-Use it when you need a mood and do not care about specific words. 500-character cap. This is the right default for background beds.
-
-## Custom mode — when the words matter
-
-```
-customMode: true
-instrumental: false
-style:  "dream pop, hazy, reverb-heavy guitars, female vocal, 100 bpm"
-title:  "Blue Hour"
-prompt: "[Verse 1]\nThe lights come on before we're ready\n..."
-```
-
-Structure tags (`[Verse]`, `[Chorus]`, `[Bridge]`, `[Outro]`) inside the lyrics are how you control the arrangement. Everything that is not a structure tag will be sung.
-
-## Instrumental scoring
-
-```
-customMode: true
-instrumental: true
-style: "tense orchestral strings, low brass swells, no percussion"
-title: "Approach"
-```
-
-`instrumental: true` is the right answer for almost every film bed — a vocal you did not ask for will fight your dialogue.
-
-## Steer with `style`, not with adjective piles
-
-Genre + era + instrumentation + tempo belong in `style`, not stuffed into `prompt`.
-
-```
-✓ style: "90s trip-hop, dusty breakbeat, Rhodes piano, upright bass, 85 bpm"
-✗ prompt: "a really cool dusty 90s trip hop song with a Rhodes and..."
-```
-
-`negativeTags` removes what keeps creeping in: `"brass, EDM drop, male vocal"`.
-
-## The steering knobs
-
-| Param | Range | Reach for it when |
-|---|---|---|
-| `duration` | 10–360s (**V5_5 + custom mode only**) | Always, when the bed must outlast the cut. It is free. |
-| `vocalGender` | `m` / `f` — **the wire values, not "male"/"female"** | A specific voice is required. |
-| `styleWeight` | 0–1 | The style field is being ignored (raise) or strangling the song (lower). |
-| `weirdnessConstraint` | 0–1 | Takes are too safe (raise) or falling apart (lower). |
-| `audioWeight` | 0–1 | Balancing an audio input against the prompt. |
-| `personaId` / `personaModel` | — | A series needs the same voice/sound across episodes. |
-
-## Character caps
-
-| Field | V4 | V4_5 / V4_5PLUS / V5 / V5_5 | V4_5ALL |
-|---|---|---|---|
-| prompt (custom = literal lyrics) | 3000 | 5000 | 5000 |
-| prompt (non-custom = description) | 500 | 500 | 500 |
-| style | 200 | 1000 | 1000 |
-| title | 80 | 100 | 80 |
-
-## Iterating
-
-- **Audition both returned songs first.** A re-roll costs a full generation; the second variation is already paid for.
-- Wrong genre → fix `style`. Wrong words → you are in the wrong mode, check the matrix above.
-- Something keeps appearing that you do not want → `negativeTags`, not more prompt.
-- Three failed generations on the same brief means the style field is too vague, not that the seed is unlucky.
-
-## Ops notes
-
-- Tracks take 2–3 minutes; a streamable preview exists ~30–40s in. Use `background: true` and poll.
-- The provider hosts files for a limited window — **Slates downloads and stores them locally as soon as the track finishes**, so nothing expires out from under a project.
-- Suno has **no official public API**; this rides an unofficial wrapper. Treat availability as best-effort and do not build a deadline around it.
-
-## Content notes
-
-Provider-side moderation rejects lyrics and style prompts naming real artists or protected material (`SENSITIVE_WORD_ERROR`). Describe the sound, not the artist. See slates-content-policy.