Recraft V4.1 API on Sume: check the catalog for the id

Sume does not list a Recraft V4.1 id. The Recraft entry in its image catalog is recraft/recraft-v4, which takes a text prompt only, returns webp, and shows $0.05 per image on its price line. If a V4.1 arrives, it will show up as a new id in the model list, so check that list instead of guessing a name.

Sume facts here come from the Image API docs and catalog code, read 2026-09-29. Nothing is claimed about what Recraft's own V4.1 does.

How do I check whether Sume lists a newer Recraft?

The docs point to GET /v1/images/models for discovery, with pricing beside each model. Filter the output for Recraft and read the ids you get back.

curl -s "https://api.sume.com/v1/images/models" \
  -H "Authorization: Bearer $SUME_API_KEY" | grep -io 'recraft[a-z0-9./-]*' | sort -u

What does the listed Recraft model accept?

It is text-to-image only: the catalog constraint reads "text-to-image only; image_urls not accepted". Its advertised output format is webp. Aspect ratios are the five named ones (1:1, 16:9, 9:16, 4:3, 3:4) plus the custom-pixel ratios Sume shares across its Fal-routed models.

Can I ask for SVG?

The Image API's output_format lists png, jpeg, webp and svg, but each model advertises its own subset, and this Recraft entry advertises webp. A format a model does not list is refused as 400 unsupported_parameter. The SVG question in full is in Recraft V4 SVG: can you get vector output through Sume?.

How do I call the listed Recraft model?

Send the catalog id and a prompt. Leave output_format off so the model's own format applies.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "recraft/recraft-v4",
    "prompt": "A flat icon of a paper plane, two colors",
    "aspect_ratio": "1:1"
  }'

What should I do if I need image-to-image with Recraft?

Nothing in the listed entry supports it, because reference images are refused for this model. If your workflow starts from an existing picture, use a catalog model that accepts input_references, such as the ones marked as edit-capable in the model list, and read the supported_parameters on its endpoint record before you send the call. Keeping the Recraft call for text-only work and switching model per job is a normal pattern, since every model is selected by its model field on the same POST /v1/images route.

When a newer Recraft version is added, the same checks apply: read its endpoint record, note the formats it advertises, and compare the price line against the table above before you switch a batch over.

What does one image cost?

The price table holds $0.04 list for recraft-v4. Sume's 1.25 margin makes the endpoint price line $0.05, and the catalog's billing formula is "list × 1.25 → ceil usd cents", so one image reserves $0.05. Failed or cancelled generations are not billed. See how Sume prices image API calls for the model-by-model math.