Image edits
Live
Open in ChatGPT
(opens in new tab)Last verified: 2026-09-08Input forms
The endpoint accepts JSON and multipart form data. For the Wan 2.7 example, supply 1–9 images as uploads or supported references, plus a 1–5,000 character
prompt.bashcurl https://api.modelrush.ai/v1/images/edits \-H "Authorization: Bearer $MODELRUSH_API_KEY" \-F "model=modelrush/wan2.7-image-pro" \-F "prompt=Keep the character, replace the background with a clean developer studio" \-F "image=@source.png"
Output controls
For Wan 2.7, use
n for 1–4 outputs, size for the output dimensions, and watermark when required. Preserve the returned request identifiers.Spicy model API references
Open a model page for its request parameters and current prices. The four Wan 3 landing pages include a developer API section below the Playground. Read GET /v1/models for current schemas and key-specific access; GET /api/model-pricing exposes current customer prices.
| Model and API reference | Model ID | Endpoint |
|---|---|---|
| Qwen Image Edit Spicy | modelrush/qwen-image-edit-spicy | POST /v1/images/edits |
| Face Swap Spicy | modelrush/face-swap | POST /v1/images/edits |
| Head Swap Spicy | modelrush/head-swap | POST /v1/images/edits |
Qwen Image Edit Spicy, Face Swap Spicy and Head Swap Spicy use POST /v1/images/edits, not the image generation endpoint. Their result is asynchronous (HTTP 202): save poll_url and read outputs after status succeeded. Face and head swaps additionally require the account's portrait-rights attestation and per-request person_rights_confirmed; use each model's schema for image ordering and required fields.
All Spicy models require adult-access confirmation on the account. API keys must permit the selected model and capability. Keep keys server-side and reuse Idempotency-Key for retries of the same submission.
PreviousImage generation
NextVideo generation