Recraft API has 15 endpoints: which does the Sume image API cover?
Recraft lists 15 API endpoints, from vectorize to erase region. Sume's image API covers generate and reference edit with recraft/recraft-v4, not the rest.
Recraft's API getting-started page lists 15 endpoints, among them generate image, image to image, inpainting, outpainting, vectorize, remove background, two upscalers and erase region. Sume's image API exposes Recraft as one model id, recraft/recraft-v4, through the generate-and-reference-edit shape of POST /v1/images, so most of Recraft's tool endpoints have no one-to-one Sume route.
The Recraft list is from its API getting started page, read 2026-10-02. Sume's side is from the Image API.
Which 15 endpoints does Recraft list?
The page names: Generate image, Create style, Image to image, Image inpainting, Image outpainting, Replace background, Generate background, Vectorize image, Remove background, Crisp upscale, Creative upscale, Refine details, Erase region, Remix image, Enhance prompt, and Get user information. It points to a Swagger document for the schemas.
How do those map onto Sume?
Sume's image endpoint is one route with a model id and a prompt, plus optional input_references and, for some models, a mask. That covers text to image and reference-guided editing. It does not give you a named route per Recraft tool.
| Recraft endpoint | On Sume's image API |
|---|---|
| Generate image | POST /v1/images with model recraft/recraft-v4 |
| Image to image, Remix image | Same route with input_references and an edit-style prompt |
| Inpainting, Erase region | Mask support is documented for ChatGPT Image 2.5 only on the Image API page |
| Vectorize image, Create style | No equivalent in the image request table |
| Remove background, Replace background | Not a named route; transparency is documented for ChatGPT Image 2.5 via the background field |
| Crisp and Creative upscale | See the separate upscale tool, not the image route |
| Enhance prompt | Not listed; write the prompt yourself |
What does recraft/recraft-v4 give you on Sume?
The model slug is in the repo's catalog list, and its aspect ratios use the custom-pixel catalog that Flux, Qwen and Seedream share. The Image API page says image_size accepts named presets or custom pixels on models that take custom pixels, listing GPT, Seedream, Flux, Qwen and Recraft. Output format is model-specific; an earlier post found that the Recraft V4 row advertises webp, so check the descriptor, as in Recraft V4 SVG.
Recraft's page also says the V4.1 Pro and V4 Pro models reach 4 megapixels for print, standard versions 1 megapixel, and the Flash model is raster only. Those are Recraft model tiers; Sume's catalog lists recraft/recraft-v4 only.
When should you call Recraft directly?
If you need vectorization, a custom style, or any of the editing tools by name, call Recraft's API for those steps. If you want one wallet, one job envelope and Sume-hosted URLs for plain generation and reference edits, use the Sume route. Mixing is fine: generate on Sume, download the result, and send that file to Recraft's vectorize endpoint. For upscaling inside Sume see Recraft crisp and creative upscale versus Sume's upscale factor.
A routing cheat sheet
Sume does not claim parity with Recraft's tool surface, and nothing here implies it. The image route is deliberately small: one request shape across many model families, which is why a Recraft tool without a generic equivalent stays on Recraft.
- Plain generation and reference edits: Sume, model recraft/recraft-v4.
- Vector output, style creation, vectorize: Recraft directly, then bring the file back as a reference if you need more edits.
- Upscaling: Sume's separate upscale tool, covered in the linked upscale post.
- Prompt enhancement: do it yourself in an agent step before submitting.
Sources
Related posts
More in Comparisons
- Replicate output files deleted after an hour: what Sume's URLs do
On Replicate, files from API predictions are deleted after an hour. Sume's Format run docs call media URLs durable, but check expires_at when a URL is signed.
- Replicate Cancel-After header: 5 s to 24 h. Is there a Sume deadline?
Replicate's Cancel-After header sets a prediction deadline from 5 seconds to 24 hours. I found no deadline field in Sume's OpenAPI, so cancel it yourself.
- Replicate predictions time out at 30 minutes: Sume's deadline
Replicate stops a prediction after 30 minutes unless support raises it. Sume documents no such field: the deadline is client-side and a timeout does not cancel.
- Replicate Prefer: wait holds 60 s by default; Sume's sync cap is 30 s
Replicate's Prefer: wait header holds the request up to 60 seconds by default; Sume's sync mode waits at most 30 seconds, then returns a job to poll.
Written by Sume