Skip to content
Last updated

Music Studio

The Music Studio API generates AI music, organizes it into a personal library, groups tracks into collections, drives continuous focus sessions, and shares tracks or collections through public links.

All generation runs on the Aitronos music engine. Call List available music engines to discover the enabled engines and their capabilities (maximum duration, vocals, stems, supported languages, and licence class) before submitting a job.

Concepts

  • Engine — an Aitronos-branded music engine identified by an internal engine_key. Each engine advertises its own capabilities and licence class.
  • Generation job — an asynchronous request to produce a track. Submit it, then poll for status until it succeeds, fails, is cancelled, or is refused.
  • Track — a produced piece of audio (id prefixed mtrack_). Tracks expose freshly-minted, short-TTL signed playback URLs.
  • Library — your saved tracks. Saving adds a library edge (mlib_); it never modifies the track.
  • Collection — a user-owned, ordered grouping of tracks (mcoll_). A track may belong to many collections.
  • Focus session — a continuously generated stream of crossfade-able segments (mfocus_) toward a target length.
  • Share link — a public, token-based link (mslink_) to a track or collection. The raw token is shown once.

Authentication & scope

Every Music Studio endpoint (except the public share resolve) requires authentication via Bearer token or API key, and is scoped to an organization passed in the path as {organization_id}. The caller may only act within an organization they belong to.

Licence honesty

Each engine and track carries a truthful licence_class (commercial_cleared, commercial_enterprise, personal_only, or unclear), a commercial_use boolean, and a requires_attribution boolean. These are never overstated — always check them before using generated audio commercially.

Endpoints