AI Mastering API

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. Run it through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the AI Mastering API?

Yes. Because you run Jentic One yourself, your own rules decide which AI Mastering operations and credentials the agent may use, so you can allow it to upload audio via POST /audios and create jobs via POST /masterings while blocking calls it should not make, such as GET /plans or listing every job. Since the audio and mastering ids sit in the URL path (/audios/{id}, /masterings/{id}), you can pin the agent to the resources it created rather than any arbitrary id. The API key is injected at execution time and never enters the agent's prompt or context, so the agent acts only within the bounds you set.