Runway gemini_image3_pro: 20 credits at 1K/2K, 40 at 4K

Runway lists gemini_image3_pro at 20 credits per 1K or 2K image and 40 credits per 4K image. At Runway's $0.01 per credit, that is $0.20 for 1K or 2K and $0.40 for 4K.

The Sume catalog id to compare is nano-banana-pro ("Banana Pro" in the image docs); confirm the mapping against GET /v1/images/models before relying on it. Figures read 2026-10-01.

How does Runway's price change with resolution?

It is a two-step tier: 1K and 2K cost the same, and 4K doubles the price.

What does Sume list for nano-banana-pro?

Sume's pricing table has one per-image entry for nano-banana-pro, with no separate tiers by resolution, and bills list × 1.25. The estimate for one default image is below. The Image API docs still accept resolution tiers of 512, 1K, 2K and 4K as request input, so check the endpoint's pricing line for your request rather than assuming a tier changes the number.

Where do I see the price before I generate?

Paid generation uses public Sume USD estimates, reserved when the request is accepted. The margin rule is explained in why an image costs list × 1.25, and the Image API docs cover the request fields.

Which should I compare on?

Compare the price for the tier you will actually request. If you generate at 4K, Runway's step to 40 credits is a real change; on Sume read the endpoint price for that exact request.