Consignment shop: cutout plus 3-second video for 12 items, $2.52

Twelve consignment items cost $2.52 to turn into 3-second videos on Sume: each item gets a background removal ($0.0225) and a 3-second Wan 3.0 clip at 480p ($0.1875), so $0.2100 per item. Wan 3.0 accepts 2 to 30 seconds, so 3 seconds is inside its range.

A consignment shop turns stock daily, so the workflow has to be repeatable per item, not per campaign. Each item is its own pair of jobs keyed by the tag number, and a failure on one item should never block the rest. Rates come from the Sume pricing code (read 2026-10-10).

What is the endpoint chain per item?

Two chained jobs, then store the URL against the tag.

• POST /v1/rmbg-1.0/remove on the item photo (a public HTTPS URL): returns a cutout PNG on media.sume.com.
• POST /v1/videos with wan-3.0, duration: 3, resolution: 480p, the cutout as the first_frame, and a prompt like 'slow turntable on a plain linen surface'.
• Use Idempotency-Key: tag-0417-video (your tag number) on both writes. A replay returns the original job, so a retry after a network error does not bill twice.
• Use callback_url (HTTPS) rather than polling twelve jobs; verify the signature headers before trusting the body.

What does it cost?

The cutout is a flat $0.0225 and the video is billed per second.

What are the limits?

Remove Background returns a transparent PNG for an input photo, which is different from generating a transparent image: Sume does not carry transparent-background generation as a model feature, so always cut out from a real photo. A 480p video is fine for a marketplace thumbnail and soft for a hero; check the result before the shop uses it.

A job that fails is refunded, but an upstream reference that cannot be fetched fails the request, so make sure item photo URLs are public HTTPS and not private signed links. See Errors and rate limits for the retry rules and Webhooks for signature checks.

Do not run all twelve at once if you also have other work in the workspace; Sume enforces concurrency seats, and a queue with your own limit of four at a time is more predictable than a burst.

Is there a cheaper route for a larger intake?

If you have 100 items a week, the cutout is the part that scales worst because every call is a separate charge. Compare a still-only card ($0.10 each at 1K) with a clip; the 12-days queue note shows a concurrency-limited queue, and the still-to-clip post explains first frames.

Running it as a queue

Keep a small table of tag, cutout URL, video job id and status in your own system. Sume returns durable URLs, but it does not know your tag numbers; your idempotency key is how you map a retry back to one.

Check results before the shop prints anything. A 480p clip is for screens; a window poster needs a different source.

• Concurrency of four is a safe default for a twelve-item batch.
• Retry only failed items; the finished ones are already paid for.
• Store the final MP4 URL against the tag and retire it when the item sells.