Kling Image 3.0 lists native 4K: Sume's image resolution tiers

Kling AI's home page lists Kling Image 3.0 with native 4K output. We found no Kling image row in Sume's image docs we read, but its image API does accept a resolution of 512, 1K, 2K or 4K, subject to each model. The catalog carries 4K pricing rules for nano-banana-2.1 and nano-banana-pro. Always read a model's supported_parameters before you ask for 4K, because the API rejects a parameter that the selected model does not list.

What each page says

The Kling page lists Kling Image 3.0 with native 4K output. It gives no price or API detail in the text we read.

Sume's image docs list the tier values for resolution and add that size is tier shorthand only and rejects WxH; custom pixels go on image_size for models that support it. higgsfield/soul is the exception, using 720p or 1080p.

Ask for 4K without a surprise

The cheapest habit is a catalog read. Call the images models endpoint, find your row, and confirm that resolution is in its supported parameters. Then price one image before you queue a hundred.

Steps:

• Request the Sume model list and filter to rows whose parameters include resolution.
• Submit one 4K image and read its cost.
• Scale the number up only after you like the output.
• Use n for series work, within the per-model cap.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"nano-banana-pro","prompt":"A ceramic teapot on linen, soft window light","resolution":"4K"}'

Why the tier name is not the whole story

A tier such as 4K is a label for the output size, not a promise about how the pixels were made. Some rows render natively at that size and some scale up, and Sume's docs describe the 4K price on two Nano Banana rows as scaled from a 1K list rate. When fine texture matters, such as fabric, small print or skin, zoom to 100 percent on a sample before you approve a batch.

Also keep the aspect ratio and the resolution separate in your head: the first sets the shape, the second sets the size tier, and a row can support one and not the other.

Budget a test first

Generate one image at the default tier and one at 4K from the same prompt, then compare the cost and the detail side by side. The difference tells you whether the extra tier earns its place in your workflow, and it takes two requests.

What Sume does not do

Sume does not list Kling Image 3.0 and does not promise native 4K on every image row: some are fixed at a lower tier, and a row that does not list resolution will reject the field. It also does not guarantee that a 4K tier is natively rendered rather than upscaled for each provider, so inspect the output when fine detail matters.