Audial's mastering runs your mix through the same hosted engine the rest of the platform uses and returns a finished master with level, tone and loudness balanced for release. One upload, one file back, no plugin chain to build.
Pass a reference track and the master is matched to it, so your mix lands in the same tonal and loudness territory as a song you already like. Without a reference, the engine masters the track on its own.
Call it wherever you work: drag a file into the mastering tab, call audial.master from Python, post the file to /functions/run/mastering as multipart form data, or ask Claude or Cursor to master a track through the Audial MCP server. Results land in your dashboard, and from the SDK and MCP they are also downloaded to a local results folder.
What you get
- Returns a single mastered file, tagged with the track's BPM and key
- Optional reference track to match tone and loudness
- Accepts MP3, WAV, FLAC, OPUS, OGG, AAC, M4A and AIFF up to 100 MB
- Runs on Audial's hosted GPUs, so nothing is installed on your machine
- Available from the website, the Python SDK, the REST API and MCP
Hear it
The same mix before and after mastering.
Use it from code
curl -X POST "https://api.audialmusic.ai/api/functions/run/mastering" \
-H "X-API-Key: your_api_key" -H "X-User-ID: your_user_id" \
-F "userId=your_user_id" \
-F "original=@/path/to/mix.mp3" \
-F "reference=@/path/to/reference.mp3"import audial
audial.config.set_api_key("your_api_key")
audial.config.set_user_id("your_user_id")
# Master on its own
mastered = audial.master("mix.mp3")
# Or match a reference track
mastered = audial.master("mix.mp3", reference_file="reference.mp3")
print(mastered["files"]["folder"])# In Claude, Cursor or any MCP client with audial-mcp installed:
"Master ~/Music/mix.wav to match ~/Music/reference.mp3 and tell me where you saved it."Frequently asked questions
It balances level, tone and loudness so the mix translates on normal playback systems. The master comes back as its own file next to the original, so you can A/B the two before committing.
Yes. Send a second file as the reference and the master is matched to its tonal and loudness character. The reference is optional.
Yes. Post to https://api.audialmusic.ai/api/functions/run/mastering with your X-API-Key and X-User-ID headers. The audio can ride along inline as multipart form data, so there is no separate upload step.
MP3, WAV, FLAC, OPUS, OGG, AAC, M4A and AIFF, up to 100 MB per file.
Yes. The Audial MCP server exposes mastering as the master tool, and the finished file is written into your results folder, which defaults to ~/Audial.
Yes. Every Audial API function, mastering included, requires an active subscription plus your API key and user ID. Without one the API answers HTTP 402 with the code SUBSCRIPTION_REQUIRED.