Can I change video playback speed with both Codex and Claude?

Yes. Codex and Claude can use medux_change_video_speed through Medux MCP. Choose the matching tab for client-specific prompting while using the same Medux operation and request contract.

Which Medux MCP tool does this tutorial use?

This workflow uses medux_change_video_speed. Review the linked API reference for the current request and response contract.

Unified Codex + Claude tutorial · media

How to change video playback speed with Medux MCP

Learn to change video playback speed with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/process/video/change_video_speed

Speed up or slow down a video.

Open the Change Video Speed 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 Change Video Speed as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the source video and exact speed multiplier, select medux_change_video_speed, 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_change_video_speed through Medux MCP to change video playback speed.
First inspect and identify the source video and exact speed multiplier.
Show me the exact tool arguments before execution.
After the task completes, return the speed-adjusted video and verify that the duration and playback speed match the request and the full video plays correctly.

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 speed-adjusted video. The final check is explicit: confirm that the duration and playback speed match the request and the full video plays correctly.

What this tutorial does

Medux operation

Speed up or slow down a video.

Agent workflow

Codex selects medux_change_video_speed, 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.

Speed up or slow down a video.

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.

Field	Type	Requirement	Purpose
`input_file_id`	string	Required	Input video file id.
`speed`	number	Required	Positive float, e.g. 1.5 for 1.5x speed.
`model_id`	string	Optional	Model Default: change-video-speed-default.
`title`	string	Optional	Optional task title.

Step-by-step workflow

Connect Medux MCP to Codex

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

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.

Ask Codex to run Change Video Speed

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

Review and approve the tool call

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

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_change_video_speed
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Change Video Speed
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Change Video Speed API through MCP?

Codex can call the medux_change_video_speed Medux MCP tool to speed up or slow down a video. 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_change_video_speed. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Change Video Speed as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source video and exact speed multiplier before proposing medux_change_video_speed. 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 change video playback speed with Medux MCP.
Restate which input fulfills each role: the source video and exact speed multiplier.
Propose the medux_change_video_speed call and summarize its arguments before asking for approval.
When it finishes, return the speed-adjusted video with a checklist confirming that the duration and playback speed match the request and the full video plays correctly.

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 speed-adjusted video plus a concise validation checklist confirming that the duration and playback speed match the request and the full video plays correctly.

What this tutorial does

Medux operation

Speed up or slow down a video.

Agent workflow

Claude selects medux_change_video_speed, 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.

Speed up or slow down a video.

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.

Field	Type	Requirement	Purpose
`input_file_id`	string	Required	Input video file id.
`speed`	number	Required	Positive float, e.g. 1.5 for 1.5x speed.
`model_id`	string	Optional	Model Default: change-video-speed-default.
`title`	string	Optional	Optional task title.

Step-by-step workflow

Connect Medux MCP to Claude

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

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.

Ask Claude to run Change Video Speed

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

Review and approve the tool call

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

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_change_video_speed
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Change Video Speed
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Change Video Speed API through MCP?

Claude can call the medux_change_video_speed Medux MCP tool to speed up or slow down a video. 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_change_video_speed. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I change video playback speed with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_change_video_speed 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 change video playback speed

This tutorial addresses developer workflows for change video speed API and speed up or slow down video 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 fits a broader AI video editing pipeline alongside video watermark removal, logo removal, object cleanup, resizing, and output validation for owned or authorized media.

Remove a watermark from video with AI Remove a static or moving logo from video Remove an unwanted object from video

Can Codex or Claude change video playback speed 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

Apply rights-aware controls when you change video playback speed

Use this as an authorized AI media processing workflow for change video playback speed. Codex or Claude can expose the selected files, tool arguments, task status, and result checks, making the edit easier to review than an opaque one-click video operation.

Only process media you own or are permitted to modify. For production and commercial publishing, retain the source license or authorization, review the changed region, and record who approved the final output.

What should I verify before running an AI video editing API?

Verify ownership or permission, choose the operation that matches the requested edit, inspect the complete output, and keep the task record with the approved source file.

Build with the API

API reference and official examples

Change Video Speed API referenceCurrent request fields, response data, limits, and examples.
Official Codex workflow exampleClient-specific prompt, approval, and result-verification example.
Official Claude workflow exampleClient-specific prompt, approval, and result-verification example.