Auphonic API
★ Only Publicly Available OpenAPI DocumentMediaAudio Processingbasic, bearer17 EndpointsREST
For Agents
Run automatic audio post-production: create a production, upload audio, attach a preset, start processing, and retrieve the cleaned-up output via a Bearer or Basic-authenticated REST API.
Use for: Create a new Auphonic production for a podcast episode, Upload a recorded interview to a production for processing, Start audio post-production on an existing production, Apply a saved preset to a new production
Not supported: Does not handle hosting, RSS feed publishing, or distribution — use for automatic audio post-production, presets, and rendered output retrieval only.
Jentic publishes the only available OpenAPI specification for Auphonic API, keeping it validated and agent-ready. Auphonic is an automatic audio post-production service that handles loudness normalisation, leveling, noise and hum reduction, filtering, and multi-format encoding for podcasters, journalists, and video producers. The API exposes the full production lifecycle: create a production, upload an audio file or pull from a service, attach a preset, start processing, and retrieve the rendered output. With 17 endpoints it covers productions, presets, account info, and reference data such as supported file types and output formats.
Install Jentic One Beta
Connect the Auphonic API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Auphonic 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with Auphonic API.
Create a new production with POST /productions.json and attach a preset
Upload an audio file to a production via POST /production/{uuid}/upload.json
Start automatic post-production with POST /production/{uuid}/start.json
Reset a production status to retry processing using /production/{uuid}/reset.json
List, create, update, and delete reusable presets via /presets.json and /preset/{uuid}.json
Fetch the current authenticated user's account info from GET /user.json
Inspect supported output file endings via GET /info/output_file_endings.json
Use Cases
Patterns agents use Auphonic API for, with concrete tasks.
★ Podcast post-production pipeline
Podcast teams want every recorded episode cleaned up consistently without manual mixing. The agent calls POST /productions.json with a preset_uuid that captures the show's loudness target and output formats, uploads the raw recording via POST /production/{uuid}/upload.json, and triggers POST /production/{uuid}/start.json. Once Auphonic finishes, GET /production/{uuid}.json returns the rendered file URLs, ready for the publishing step.
Create a production via POST /productions.json with a known preset_uuid, upload the source file with POST /production/{uuid}/upload.json, then call POST /production/{uuid}/start.json and poll GET /production/{uuid}.json until status='Done'.
Bulk archive cleanup
Radio stations and journalism archives sit on years of variably mastered recordings. An agent can iterate through stored files, create one production per file, attach a 'speech' preset, and process them through Auphonic to produce a normalised archive. /info/output_file_endings.json confirms the supported output formats up front, and /production/{uuid}/reset.json retries any failed productions in a second pass.
For each WAV in a working folder, POST /productions.json with a speech preset, upload via POST /production/{uuid}/upload.json, and start processing. After completion, write the output URL to a manifest file.
Show-specific preset management
Multi-show studios need a different loudness target, output bitrate, and intro/outro for each show. /presets.json lists, creates, and deletes presets, and /preset/{uuid}.json updates one in place. An admin agent can keep the preset catalog aligned with each show's spec without anyone touching the Auphonic web UI.
Update preset 'show-flagship' via POST /preset/{uuid}.json to set loudness_target=-16 LUFS and add an outro file, then verify with GET /preset/{uuid}.json.
AI agent integration via Jentic
A media-ops agent built on Jentic can run an Auphonic production without holding the Bearer token in its context. The agent searches an intent like 'process a podcast through Auphonic', Jentic returns the matching production-creation operation with its input schema, and execution uses the token resolved from the Jentic vault. The full chain (create, upload, start, poll) is orchestrated as one workflow.
Use Jentic search 'create an Auphonic production', load the schema for POST /productions.json, and execute it with a preset_uuid and metadata for a new episode.
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for auphonic api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/productions.json
List all productions
POST
/productions.json
Create a new production
POST
/production/{uuid}/upload.json
Upload an audio file to a production
POST
/production/{uuid}/start.json
Start processing a production
POST
/production/{uuid}/reset.json
Reset a production status
GET
/presets.json
List all presets
POST
/presets.json
Create a preset
GET
/user.json
Get the current user's account info
GET
/productions.json
List all productions
POST
/productions.json
Create a new production
POST
/production/{uuid}/upload.json
Upload an audio file to a production
POST
/production/{uuid}/start.json
Start processing a production
POST
/production/{uuid}/reset.json
Reset a production status
GET
/presets.json
List all presets
POST
/presets.json
Create a preset
GET
/user.json
Get the current user's account info
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Auphonic credentials (Basic or Bearer) are stored encrypted in the Jentic vault. Tokens are refreshed automatically and injected at execution time, so the agent never sees the raw secret in its context.
Intent-based discovery
Agents search by intent (e.g., 'create an Auphonic production') and Jentic returns the matching operation with its input schema, so the agent calls /productions.json, /production/{uuid}/start.json, or /presets.json without reading the help docs.
Time to first call
Direct Auphonic integration: 1-2 days for OAuth setup, multipart upload, and the create-upload-start-poll sequence. Through Jentic: under 30 minutes from search to first executed call.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Auphonic API through Jentic.
Why is there no official OpenAPI spec for Auphonic API?
Auphonic publishes API help pages at auphonic.com/help/api but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Auphonic 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 Auphonic API use?
The Auphonic API supports HTTP Basic authentication with the account's username and password and OAuth 2.0 Bearer tokens. Bearer tokens are recommended for production integrations. Through Jentic the credentials are held in the vault and injected at execution time.
Can I run automatic post-production on a single file with the Auphonic API?
Yes. Create a production via POST /productions.json with a preset_uuid, upload the file via POST /production/{uuid}/upload.json, and trigger POST /production/{uuid}/start.json. Poll GET /production/{uuid}.json until status='Done' and read the output URLs from the response.
What are the rate limits for the Auphonic API?
Auphonic charges by processing minutes rather than enforcing a strict per-call rate limit. Concurrent productions are capped per account; check /user.json for current credit and active production count rather than retrying tightly on errors.
How do I attach a saved preset to a new production through Jentic?
Run jentic search 'create an Auphonic production', load the schema for POST /productions.json, and pass preset_uuid in the body. The Bearer token is resolved from the Jentic vault at execution time. With pip install jentic the call is one async invocation.
Is the Auphonic API free?
Auphonic offers free monthly processing credit on its starter tier and paid plans for production volume. The API is available on every plan; the limit is processing minutes per month rather than API call volume.
GET STARTED