GuidesDeliver a score

Deliver a score

Send the same arguments you used to score a video and get a ZIP: the scored video, each section’s music as its own MP3 named by timecode, and the cue sheet. Downloading it asks for a quick sign-in on ainsof.io.

MCP tooldeliver_scoreRESTaction: "deliver_score"

Try it

curl https://mcp.ainsof.io/ \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AINSOF_API_KEY" \
  -d '{"action": "deliver_score", "video_url": "https://example.com/my-video.mp4", "brief": "warm, hopeful acoustic"}'

What you send

video_urlrequired

string

The same video link that was scored.

Also accepted as url

sign_in_code

string

The code returned with sign_in_required, once the person has signed in. Pass the same code to every video action; it stays valid for 30 days. Not needed with a key created on ainsof.io.

brief, track_id, version, music_offset_db, silences, sections

Exactly as sent to score_video. Any difference finds a different render (or none).

Good to know

Before AINSOF works with a video, a person signs in once on ainsof.io (Google or email). With a key created on ainsof.io this has already happened. Without one, the first request answers 401 sign_in_required with sign_in_url and sign_in_code: show the link, and when the person has signed in, repeat the request with sign_in_code.
Send the same arguments used for score_video (or the delivery_request.arguments it returned), plus sign_in_code if you signed in without a key, since delivery_request does not include it. The most recent render with identical arguments from the last 7 days is delivered; nothing is re-rendered.
If a render has no package but its video exists, the response is 200 with format: "mp4" and a download_url that opens the video's watch page (/v/<id>).
Downloading the zip opens ainsof.io, which asks for a quick sign-in (Google or email) first.

Every field it returns, and its errors, in the API Reference