Viral video remake

Capability key: video.edit · API origin: https://api.anycap.io

Viral video remake renders a new video from a source video you own. The platform keeps the source motion, camera work, composition and timing, and applies your editing instruction together with target reference images, reference videos and reference audio: replace a person, a product, an object or a background, or transfer a consistent style. It is an asynchronous task: submit once, then read the durable task state until it completes.

Unified API (recommended)

New integrations call POST /v1/generations with type=video_edit. The /v1/videos/edits endpoints below remain supported for compatibility.

curl -X POST https://api.anycap.io/v1/generations \  -H "Authorization: Bearer $ANYCAP_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "type": "video_edit",    "model": "<model from GET /v1/generations/models?type=video_edit>",    "input": {      "video_file_id": "<owned source video id>",      "prompt": "replace the product on the table, keep the camera move"    },    "parameters": { "resolution": "480P", "ratio": "adaptive" }  }'

1. Setup

• Create a connection key in the console under Agent Access and authorize the editing capability.
• Upload the source video, reference videos, reference audio and reference images to POST /v1/video-materials?kind=video|audio|image with a multipart file field. The upload is retained for 72 hours. The source video must be an Anycap-owned upload no longer than 15 seconds; public URLs are not accepted for the source video. Use the returned id as video_file_id or a reference file id.
• Every request uses Authorization: Bearer <ANYCAP_API_KEY> and Content-Type: application/json. Never send Cookie or Origin, and never reuse a browser session.
• There is one discovery surface: query GET /v1/videos/models?capability=video.edit. It returns the editing models with their own prices and limits; create with one of those model values. Never invent model names or prices.

curl -X POST "https://api.anycap.io/v1/video-materials?kind=video" \  -H "Authorization: Bearer $ANYCAP_API_KEY" \  -F "[email protected]"

2. Endpoints

prompt is the editing instruction: describe what to replace, restyle or keep in the source video.

3. Create a task

Example:

curl -X POST https://api.anycap.io/v1/videos/edits \  -H "Authorization: Bearer $ANYCAP_API_KEY" \  -H "Content-Type: application/json" \  -H "Idempotency-Key: remake-7f4c2b1a" \  -d '{    "model": "doubao-seedance-2-0-mini-260615",    "video_file_id": "<source video file id>",    "prompt": "replace the product on the table with the target product, keep the camera move",    "resolution": "720P",    "ratio": "original",    "reference_image_urls": ["https://cdn.example.com/target-product.png"]  }'

Every model entry publishes input_types plus max_reference_images, max_reference_videos, max_reference_audios, audio_min_seconds, audio_max_seconds, max_total_video_seconds and max_total_audio_seconds; a request outside the chosen model's limits is rejected with 400 before submission.

• The source video is the edit input and counts toward max_total_video_seconds; additional reference videos are capped separately by max_reference_videos.
• Reference videos must each be at least 2 seconds and are measured with the source video before pricing.
• Each reference audio must be between audio_min_seconds and audio_max_seconds; all audio is summed against max_total_audio_seconds.
• Reference videos and audio must be Anycap-owned uploads from POST /v1/video-materials?kind=video|audio, unexpired: only their measured seconds can be billed. Owned reference images must be JPG, WebP or BMP (PNG is not accepted); public HTTPS image URLs are also accepted.

4. Task state and result

• The create response is 202 and returns the durable job with state and billing_status. 202 does not prove upstream success or settled billing.
• Poll GET /v1/videos/edits/{id}. A task moves through queued, submitting, submitted, processing and finalizing to completed, failed or pending.
• Send ?result=true only when you need the output URL. It re-queries the provider and never recharges or regenerates. The URL is temporary and provider-hosted; download and store it yourself if you need it long-term.
• DELETE cancels only a task still queued before any billable upstream call and releases its reservation exactly once. The editing operator publishes no cancellation, so a job already in flight returns 409 and keeps its reservation for reconciliation.

5. Errors