MusicGPT API

Name: MusicGPT API
Brand: MusicGPT API
Availability: InStock

✓ Official Vendor SpecAI/MLSpeechbearer28 EndpointsREST

For Agents

Generate songs, change voices, separate stems, and convert audio to MIDI through MusicGPT's AI music platform. Returns generated audio URLs and job results across 28 operations.

Install Jentic One Beta

Connect the MusicGPT API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MusicGPT API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MusicGPT API.

Generate complete songs from a text prompt via the Music AI endpoints

Remix an existing track by changing genre, tempo, or instrumentation

Extend an audio clip seamlessly or inpaint a missing section

GET STARTED

Start building with MusicGPT API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MusicGPT API for, with concrete tasks.

★ Prompt-to-Song Generation

Turn a written prompt into a full song with vocals, instrumentation, and structure. The /v2/MusicAI endpoint accepts a prompt, optional genre and mood, and returns a generated track URL. For batch creative exploration, /v2/MusicAI/batch accepts multiple prompts in a single call. This collapses creative iteration that would otherwise involve a producer and session musicians.

Call POST /v2/MusicAI with a prompt like 'lo-fi hip hop track with rain sounds and a saxophone melody' and return the generated audio URL.

Stem Separation for Remixing

Split a finished song into individual vocal, drum, bass, and instrument stems for remixing or sampling. The /v1/Extraction endpoint runs source separation and returns each stem as a downloadable file. Producers and content creators get clean stems in seconds rather than running local separation models on their own hardware.

Submit a song URL to POST /v1/Extraction and return the URLs for the vocal and drum stems for use in a remix.

Voice Cover Generation

Re-sing an existing song in a different voice for cover videos, fan art, or creative experiments. POST /v1/Cover takes a source song and a target voice and returns the cover. POST /v1/VoiceChanger does the same for spoken or sung audio without requiring a full re-render. Both expose model selection and quality controls in the request body.

Submit a song URL and target singer voiceId to POST /v1/Cover and return the generated cover audio URL.

Audio-to-MIDI Conversion

Convert a hummed or sung melody into a MIDI file for use in a digital audio workstation. POST /v1/audio_to_midi accepts audio and returns the transcribed MIDI, which a downstream DAW can import directly. This collapses the manual transcription step that producers traditionally perform note by note.

Submit a hummed melody to POST /v1/audio_to_midi and store the returned MIDI file in the user's project folder.

AI Agent Music Workflow

Drive a Jentic-powered agent that composes, remixes, and reshapes audio in response to user instructions. The agent searches Jentic for 'generate a song from a prompt', loads the schema for /v2/MusicAI, and chains it with /v1/Extraction or /v1/VoiceChanger as needed. Jentic injects the bearer token at execution time, so the agent never sees the MusicGPT secret.

Through Jentic, search for 'generate a song from prompt', call POST /v2/MusicAI, then chain POST /v1/Extraction on the result to return individual stems.

Key Endpoints

28 endpoints — the musicgpt api generates music, transforms voices, and processes audio through ai models exposed as a single-bearer-token rest surface.

METHOD

PATH

DESCRIPTION

POST

/v2/MusicAI

Generate a song from a prompt (V2)

POST

/v1/Remix

Remix an existing track

POST

/v1/Extraction

Separate audio into stems

POST

/v1/Cover

Generate a cover in a different voice

POST

/v1/VoiceChanger

Change the voice on a recording

POST

/v1/audio_to_midi

Transcribe audio to MIDI

POST

/v1/sound_generator

Generate sound effects from a prompt

POST

/v1/TextToSpeech

Synthesize speech from text

POST

/v2/MusicAI

Generate a song from a prompt (V2)

POST

/v1/Remix

Remix an existing track

POST

/v1/Extraction

Separate audio into stems

POST

/v1/Cover

Generate a cover in a different voice

POST

/v1/VoiceChanger

Change the voice on a recording

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The MusicGPT bearer token is stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Agents never see the raw token in their context, which keeps API keys out of prompts and logs.

Intent-based discovery

Agents search Jentic with intents like 'generate a song' or 'separate stems' and Jentic returns the matching MusicGPT operation with its input schema, removing the need to browse MusicGPT docs.

Time to first call

Direct MusicGPT integration including auth, async polling, and error handling typically takes 1-2 days. Through Jentic the search, load, execute flow runs in under an hour.

FAQs

Specific to using MusicGPT API through Jentic.

What authentication does the MusicGPT API use?

MusicGPT uses HTTP bearer token authentication. Each request must include an Authorization header with a token issued from the MusicGPT dashboard. Through Jentic, the bearer token is stored in the Jentic vault and applied to every request automatically, so agent code never handles the raw secret.

Can I generate a full song from a text prompt with the MusicGPT API?

Yes. POST /v2/MusicAI accepts a prompt and optional genre or mood parameters and returns a generated song. Use POST /v2/MusicAI/batch when generating multiple variants from different prompts in a single call.

How do I separate a song into stems through Jentic?

Through Jentic, search for 'separate a song into stems', load POST /v1/Extraction, and submit the source audio URL. The response contains URLs for each stem (vocals, drums, bass, other) which Jentic returns to the agent without exposing the bearer token.

What are the rate limits for the MusicGPT API?

The OpenAPI spec does not declare specific rate limit values. MusicGPT publishes plan-based limits on its pricing page; respect Retry-After headers on 429 responses and stagger batch jobs to stay within the limits on your tier.

Can I convert a hummed melody into MIDI?

Yes. POST /v1/audio_to_midi accepts an audio file and returns a MIDI transcription suitable for import into a DAW. This is one of 28 endpoints covering generation, processing, and conversion workflows.

Does the MusicGPT API support streaming generation?

Yes. The Streaming tag covers operations that emit audio progressively as it is generated, which is useful for long-form tracks where the agent wants to start playback before the full file is ready.

MusicGPT API

Connect the MusicGPT API to your agent

Capabilities

Start building with MusicGPT API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs