Unified Codex + Claude tutorial · media

How to reverse an audio file with Medux MCP

Learn to reverse an audio file with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/process/audio/reverse_audio

Reverse an audio file.

Open the Reverse Audio API reference →
Choose your AI client

Follow the Codex or Claude workflow

The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.

Codex-specific workflow

Run Reverse an Audio File as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the source audio file, select medux_reverse_audio, and keep the Medux task ID and returned output with the rest of the project. Naming the input roles and the expected result prevents an agent from guessing which file should be used where.

Codex prompt pattern

In this workspace, use medux_reverse_audio through Medux MCP to reverse an audio file.
First inspect and identify the source audio file.
Show me the exact tool arguments before execution.
After the task completes, return the reversed audio and verify that the output duration matches the source and playback is fully reversed.

Approval gate

Before approving the call, compare the selected tool, file or asset IDs, ordering, timing, and output settings with the request. If a local filename was mapped to an uploaded Medux file ID, keep that mapping visible so it can be audited later.

Result verification

Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the reversed audio. The final check is explicit: confirm that the output duration matches the source and playback is fully reversed.

What this tutorial does

Medux operation

Reverse an audio file.

Agent workflow

Codex selects medux_reverse_audio, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Upload the source file and create a file reference before calling this endpoint.
  • Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
  • All file inputs must be uploaded and persisted as file references before submission.

Prompt Codex

Start with a clear instruction that names the Medux operation and the intended inputs.

Reverse an audio file.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
input_file_idstringRequiredInput audio file id.
model_idstringOptionalModel Default: reverse-audio-default.
titlestringOptionalOptional task title.

Step-by-step workflow

01

Connect Medux MCP to Codex

Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_reverse_audio tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Codex to run Reverse Audio

Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_reverse_audio and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Codex selects medux_reverse_audio
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Reverse Audio
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Reverse Audio API through MCP?

Codex can call the medux_reverse_audio Medux MCP tool to reverse an audio file. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_reverse_audio. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Reverse an Audio File as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source audio file before proposing medux_reverse_audio. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.

Claude prompt pattern

Using the assets and requirements in this conversation, help me reverse an audio file with Medux MCP.
Restate which input fulfills each role: the source audio file.
Propose the medux_reverse_audio call and summarize its arguments before asking for approval.
When it finishes, return the reversed audio with a checklist confirming that the output duration matches the source and playback is fully reversed.

Context checkpoint

Have Claude summarize the intended transformation, identify every source asset by role, and list the important constraints. Review that summary together with the proposed tool arguments; correct the conversation first if a file, order, time range, or setting is ambiguous.

Result verification

Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the reversed audio plus a concise validation checklist confirming that the output duration matches the source and playback is fully reversed.

What this tutorial does

Medux operation

Reverse an audio file.

Agent workflow

Claude selects medux_reverse_audio, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Upload the source file and create a file reference before calling this endpoint.
  • Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
  • All file inputs must be uploaded and persisted as file references before submission.

Prompt Claude

Start with a clear instruction that names the Medux operation and the intended inputs.

Reverse an audio file.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
input_file_idstringRequiredInput audio file id.
model_idstringOptionalModel Default: reverse-audio-default.
titlestringOptionalOptional task title.

Step-by-step workflow

01

Connect Medux MCP to Claude

Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_reverse_audio tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Claude to run Reverse Audio

Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_reverse_audio and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Claude selects medux_reverse_audio
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Reverse Audio
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Reverse Audio API through MCP?

Claude can call the medux_reverse_audio Medux MCP tool to reverse an audio file. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_reverse_audio. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I reverse an audio file with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_reverse_audio call, and verify the returned result. The tabs above keep client-specific prompting on one canonical page.

Can I use the same Medux tool in Codex and Claude?

Yes. The client interaction differs, but both use the same Medux MCP tool and API request contract shown in this tutorial.

Related developer intent

Use AI agents to reverse an audio file

This tutorial addresses developer workflows for reverse audio API and play audio backwards programmatically by making the task repeatable through the Medux API. Codex or Claude can prepare inputs, show the MCP tool arguments for approval, monitor processing, and return an output that can be checked against the original request.

This capability also fits a broader AI lip sync and talking-avatar pipeline: prepare an approved voice or avatar asset, run audio-to-video lip sync, then verify timing, mouth motion, and final playback.

Build an AI lip sync video with Medux MCPCreate a talking photo from image and audioPrepare a reusable voice for avatar workflows
Can Codex or Claude reverse an audio file through Medux MCP?

Yes. Use the client-specific tab above to prepare the inputs, review the Medux tool call, run the operation, and verify the returned result. The linked API reference remains the source of truth for supported fields and limits.

Production, trust, and developer intent

Use an auditable audio workflow to reverse an audio file

This AI audio processing API workflow lets Codex or Claude reverse an audio file while keeping file roles, tool arguments, task IDs, and output checks visible. Use authorized source audio and preserve an input-to-output record when the result feeds voice, dubbing, lip sync, or production video.

A security-conscious audio workflow keeps API keys outside prompts, limits uploaded media to what the task needs, and restricts result access in the calling application. Those operational controls complement the Medux tool call.

How do I make an AI audio workflow easier to audit?

Keep the source asset ID, approved parameters, Medux task ID, returned result, and final listening check together with the project that requested the edit.

Build with the API

API reference and official examples