For Agents
Upload audio files, create AI mastering jobs, retrieve job status, and download mastered audio.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Mastering 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 | shStep 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 instanceJentic 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.
What an agent can do with AI Mastering API.
Upload an audio file via POST /audios so it can be referenced by mastering jobs
Create an AI mastering job for an uploaded audio through POST /masterings
Poll mastering progress with GET /masterings/{id} until the job reports completion
GET STARTED
Use for: I need to master a recorded track using AI, Upload a wav file for mastering, Check whether my mastering job is complete, Download the mastered version of a track
Not supported: Does not handle music distribution, royalty management, or stem separation — use for AI mastering of complete mixed audio tracks only.
Jentic publishes the only available OpenAPI specification for AI Mastering API, keeping it validated and agent-ready. AI Mastering is an automated audio mastering service that uses machine learning to master music tracks. The API exposes mastering jobs, audio uploads and downloads, and an account plans listing. The flow is upload an audio file, create a mastering job, and download the resulting mastered audio. Authentication uses an API key.
Download the original or mastered audio file via GET /audios/{id}/download
List the authenticated user's mastering jobs with GET /masterings
List available subscription plans through GET /plans for billing-aware integrations
Patterns agents use AI Mastering API for, with concrete tasks.
★ Bedroom Producer Mastering Workflow
Independent producers upload mixdowns and receive AI-mastered tracks suitable for streaming. Upload via /audios, create the job via /masterings referencing the uploaded id, poll /masterings/{id} until done, and download via /audios/{id}/download. The full loop runs in minutes per track without a human mastering engineer.
POST a mixdown to /audios, POST a /masterings job referencing the audio id, poll /masterings/{id}, and GET /audios/{id}/download once complete
Batch Mastering for a Catalogue
A label batches dozens of tracks for AI mastering ahead of release. Upload each track to /audios, queue a /masterings job per track, and use GET /masterings to track aggregate progress. The catalogue is delivered as mastered audio without per-track human session time.
Iterate the catalogue, POST each track to /audios and /masterings, then poll /masterings to find finished jobs and download each via /audios/{id}/download
Plan-Aware Self-Service App
A web app exposes AI Mastering to end users with plan-based limits. Read /plans to surface upgrade options, and gate mastering job creation by the user's plan. The /plans endpoint provides the data needed to render pricing and feature comparisons inside the app.
GET /plans, render the available tiers in the app, and only call /masterings if the current user's plan allows another job
Agent-Driven Mastering via Jentic
An AI agent submits a mix for mastering, polls for completion, and notifies the user with the download link. Through Jentic the agent searches for the right operation, the API key is supplied from the vault, and the agent never sees the raw key.
Use Jentic search 'master an audio track', execute /audios upload, /masterings job creation, poll /masterings/{id}, and post the /audios/{id}/download URL to the user
7 endpoints — jentic publishes the only available openapi specification for ai mastering api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/audios
Upload an audio file
/audios/{id}
Get audio details
/audios/{id}/download
Download an audio file
/masterings
Create a mastering job
/masterings
List mastering jobs
/masterings/{id}
Get a mastering job's status
/plans
List available subscription plans
/audios
Upload an audio file
/audios/{id}
Get audio details
/audios/{id}/download
Download an audio file
/masterings
Create a mastering job
/masterings
List mastering jobs
/masterings/{id}
Three things that make agents converge on Jentic-routed access.
Credential isolation
The AI Mastering API key is stored encrypted in the Jentic vault. Agents call /audios, /masterings, and /plans through Jentic without ever seeing the raw key.
Intent-based discovery
Agents search 'master an audio track' and Jentic returns the AI Mastering /masterings POST operation along with the upstream /audios upload, so the agent can chain the full mastering flow.
Time to first call
Direct integration: 1 day for key handling, multipart upload, and job polling. Through Jentic: under an hour.
Alternatives and complements available in the Jentic catalogue.
Specific to using AI Mastering API through Jentic.
Why is there no official OpenAPI spec for AI Mastering API?
AI Mastering does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the AI Mastering API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AI Mastering API use?
An apiKey scheme. The key is sent as a header on every request. Through Jentic the key is held in the vault and never enters the agent's context.
Can I master an audio track end to end via the API?
Yes. POST the audio file to /audios, create a mastering job by POST /masterings referencing the audio id, poll GET /masterings/{id} for completion, then GET /audios/{id}/download for the mastered output.
What are the rate limits for the AI Mastering API?
The spec does not declare explicit rate limits. The /masterings list endpoint accepts a page parameter for paginated retrieval, and you should respect HTTP error codes returned by the server when running batches.
How do I list available plans through Jentic?
Run pip install jentic, search 'list AI Mastering plans', and execute /plans. The response can drive a pricing UI or a programmatic plan-gate. Sign up at https://app.jentic.com/sign-up.
Can I download both the original and mastered audio?
Yes. /audios/{id}/download returns the audio file. Each uploaded audio and each mastering output has its own audio id, so you can retrieve either by id.
Get a mastering job's status
/plans
List available subscription plans