Release Packs

​

Start with the music

Ask your agent: “Create a release pack for this song.” Supply the audio or an accessible audio link. A listening page is not an audio file. Tell it whether this is a new release, an anniversary, a reissue, a remix, or a catalog rediscovery campaign. The agent reuses information you have already supplied and any selected, accessible Recoup context. It asks only for essential gaps: the correct artist and recording, the occasion, and artwork or creative direction. You can ask it to propose a direction from the music instead. It must distinguish that proposal from your established branding. You do not need an existing artist profile, Spotify history, connected social accounts, a catalog import, or a GitHub workspace to prepare a pack. An empty Recoup roster is a valid new account. Sign in through your host’s Recoup connection when the agent needs authenticated execution; it should resume the same request. “Plan a release” is a different request. It produces a creative brief and rollout plan. Ask for a release pack to produce media, or ask for both so the agent can carry the same brief into production. When ChatGPT supplies a selected attachment to the upload tool, the tool accepts its host file reference directly. It imports the selected download URL into private Recoup storage and validates the actual media bytes. Other hosts can use the supported source URL, inline or signed-upload modes; a filename alone is not an accessible recording. For direct API uploads, small inline files are limited to approximately 3 MB (4,000,000 base64 characters). For normal song files, request a private signed upload, transfer the file and finalize it, or import an accessible HTTPS source up to 50 MiB for audio or 10 MiB for a reference image. Supported transfers depend on your host; an attachment is usable only after the agent can access its actual bytes. Audio formats include MP3, WAV, FLAC and M4A. Source images can be PNG, JPEG or WebP.

​

What the brief contains

For anniversaries, the original release date and campaign date are separate. If the original date is unknown, the agent must obtain it before making dated anniversary claims. A catalog request needs a bounded selection of recordings; it must not silently generate a pack for every track. Research enriches the brief. Missing research or audience metrics should not force unrelated onboarding or fabricated statistics. Existing artwork and supplied preferences can be enough to propose strong creative work. An artist’s face is optional; artwork-led and typographic work are valid directions.

​

Scope and budget before generation

Preparation and generation are separate operations. Before paid production, the agent shows the proposed direction, deliverables, cost scope and maximum budget. The quote binds the current brief and deliverables. Changing the song or scope requires a new quote; an earlier approval cannot silently authorize different work. The default scope is 15 creative pieces: eight video clips, four quote cards, one artwork, one carousel and one visualizer, with captions. A carousel is one piece; its slides and alternate aspect ratios are identified as components or variants. You can request a smaller scope. The quote must describe the actual selected work, including chargeable stages and any retry allowance. Current quotes charge for image and motion generation; captioning, audio analysis, composition and inspection are included without an added customer fee. The approved amount is held before production; unused stages are refunded. A new paid retry needs its own quote. The older GET /api/content/estimate is an advisory per-video estimate. It is not a complete Release Packs quote. On insufficient credits the agent surfaces the returned billingUrl; it must not buy credits, switch accounts or retry paid generation automatically.

​

One job, with visible progress

The pack retains its brief, revision, quote, individual asset states and completed work. Signing in, waiting for a render, or recovering from a failed stage should not make you repeat the request or regenerate the whole pack. The first representative asset is produced and inspected early. The agent then continues the agreed batch within your budget, unless you requested a preview checkpoint. Progress distinguishes requested, generated, inspected and delivered assets. A partly generated pack is reported as partial.

​

Review and delivery

A finished music-bearing asset must contain the selected recording and the correct audio window. Inspection covers sound, timing, duration, framing, readable text, visual consistency and the campaign brief. A render request, a prompt or a concept is not a finished asset. Static image inspection and video inspection are separate. Delivery includes previews, usable files, captions, a manifest and any unresolved gaps. The agent retains successful work when a stage fails and retries only within the approved scope and budget. Release Packs stops at the assets: posting and scheduling need a separate request. After delivery, you can save confirmed artist preferences for next time. A one-off creative proposal must not overwrite established branding or become a permanent public knowledge-base entry automatically.

​

API and connected tools

Connected operations are prepare_release_pack, get_release_pack, estimate_release_pack, generate_release_pack, retry_release_pack, upload_release_pack_asset and export_release_pack. Discover their actual schemas in the connected host; older connections may need a refresh. The shared API contract separates preparation, reading, quoting, generation, retry and selected-asset upload. Connected tools use the same account and job rules. Credentials remain with the host; an agent must not extract OAuth tokens into REST requests or ask for an API key to compensate for a missing MCP tool. If a required operation is unavailable, the agent should name that operation, retain the brief and explain the next step. It must not claim the entire account is disconnected or present a plan as completed media.