Developer docs

Rewrite a song’s brief from the song

MCP tool
rewrite_song_brief
CLI
kinetune songs rewrite-brief
POST/api/v1/songs/{song_id}/brief

Not sent from the docs: it changes your workspace. Run it with curl, the CLI or its MCP tool.

Drop the user’s correction and read the song again

Writes the brief again from the song as it is now (its lyrics and analysis), in the background: the answer has status writing; poll get_song until brief.status is ready, usually within half a minute. The user’s correction (brief.edited) is dropped, so ask first. Free; a few times a day per song (429 past that). 409 while the song is being analysed.

headerAuthorizationBearer <token>

An organization API key (kt_live_…) or an OAuth access token

song_id*string

The song id

Length1 <= length <= 120
application/json
  1. body

Response Body

OK

application/json
  1. response
status*string

writing: being written (the fields are null until ready)

Value in"writing""ready"
theme*|

What the song is about, in a sentence

tone*|

Its register, in a few words

story*|

The story or situation under the words (null for a mood piece)

mood_arc*array<>

How the feeling moves through it, section by section

setting*|

An era, a place or a scene it evokes (null when none)

edited*boolean

The user corrected it: directors read their version, and nothing replaces it until rewrite_song_brief

updated_at*string|null
[key: string]?unknown
Example Request
curl -X POST 'https://kinetune.com/api/v1/songs/string/brief' \
  -H 'Content-Type: application/json' \
  -d '{}'
Example Response
{
  "status": "writing",
  "theme": "string",
  "tone": "string",
  "story": "string",
  "mood_arc": [
    {
      "section": "string",
      "feeling": "string"
    }
  ],
  "setting": "string",
  "edited": true,
  "updated_at": "string",
  "property1": null,
  "property2": null
}