Auphonic API

Is there an Auphonic MCP server?

You don't need an MCP server to give your agent Auphonic. Jentic connects it directly from the API Directory: import it, store your Auphonic credential once, and your agent calls the production and preset operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

What authentication does the Auphonic API use?

Auphonic documents three schemes: API key authentication, HTTP Basic authentication, and OAuth 2.0. API key authentication sends the key as a bearer token in an Authorization header and is Auphonic's recommended method for your own resources. HTTP Basic uses the account's username and password. OAuth 2.0 is intended for third-party applications acting for multiple Auphonic accounts; Auphonic documents it, but it is not declared in the spec behind this page. Through Jentic the credential is held by your own Jentic One instance 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 in the preset field, upload the file via POST /production/{uuid}/upload.json, and trigger POST /production/{uuid}/start.json. Poll GET /production/{uuid}.json until status_string='Done' (status 3) and read the output URLs from the response.

What are the rate limits for the Auphonic API?

Auphonic documents per-operation limits in its own OpenAPI document and returns 429 when one is exceeded. Listing productions and fetching a single production allow 60 requests per 4 minutes each. Creating a production allows 40 requests per 2 minutes, or 100 for business accounts. Downloads allow 30 per 5 minutes per production. For frequent status checks Auphonic points you at webhooks rather than polling.

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 the preset field in the body. The bearer token is resolved from your Jentic One instance at execution time.

Is the Auphonic API free?

Auphonic is free for 2 hours of processed audio per month. Recurring credit plans run from 9 hours to 250 hours per month, with one-time credits available as well. What you pay for is processing volume; the per-operation request limits above apply on top of it.

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

Yes. Because you run Jentic One yourself, your own rules decide which Auphonic operations and credentials the agent may use. Auphonic puts the production UUID in the URL path, such as POST /production/{uuid}/upload.json and POST /production/{uuid}/start.json, so you can pin the agent to uploads and starts for a single production. You choose the operations it may call, so a destructive action like DELETE /production/{uuid}.json stays out of reach unless you add it.