Write the score's plan with AI (costs credits)

One text call to Gemini Flash-Lite writes how each section of the score should sound (2-6 positive and up to 4 negative styles, and a one-line reason) and the film's global styles, from the film (each section's moments, action prompts, lines heard, light and weather, its place in the story: the opening, a decision's wait, the end) and the owner's direction (setScoreDirection), which outranks the rest. The sections are the ones POST .../score composes; the answer is stored in the storyboard (doc.score.sections, by ai), so the next score composes exactly that plan. Sections edited by hand (setScoreSection, by owner) are kept and not asked for. Costs credits: score_plan per call (see /v1/pricing), checked before the call and charged after a readable answer is on the storyboard, through your token so its daily cap applies. Quote first with dry_run: true: credits, sections (to write) and kept (yours); available: false comes with a reason. Read the plan back with POST .../score { dry_run: true }. A storyboard whose owner approves agent spending answers 403 except for the quote.