Dhanteras Nov 6 jeweller clip with the product commercial Format

To make a Dhanteras clip for a jewellery counter, call Sume's catalog Format sume-product-commercial with your product photo and a short instruction, cap the spend, and poll the run until its receipt returns the video. It is one POST to /v1/formats/sume/sume-product-commercial/runs from any key with the formats:write scope, so a small shop can do it without wiring up separate image, video and timeline steps.

Diwali 2026 runs November 6 to 10 with the main day on Sunday, November 8 (Awareness Days, read 2026-10-04). The five-day festival opens on Friday the 6th with Dhanteras, so a counter that wants a clip live that morning should have the render done by the 4th or 5th.

What is the product commercial Format?

Sume's Format catalog (read 2026-10-04) lists sume-product-commercial among the slugs callable at the reserved sume handle. A Format is a saved recipe an Agent applies to a run; Sume boots a fresh sandbox, loads the recipe and the generation tools, and returns artifacts. Before calling, read it with GET /v1/formats/sume/sume-product-commercial, which returns its description and an io profile, so you know what shape of input it expects.

What does the call look like?

input is a free-form object: the recipe reads the keys it knows and the rest rides along as context. Send a product image, the shop name and the occasion, and tell the instruction what you do not want. generation_spend_cap_usd is this run's ceiling; set it yourself rather than inheriting one. Every create needs an Idempotency-Key.

curl -X POST https://api.sume.com/v1/formats/sume/sume-product-commercial/runs \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: dhanteras-ring-001" \
  -d '{
    "instruction": "A 15-second vertical Dhanteras product commercial for one gold ring. Warm diya light, slow macro movement. No price, no text, no claims about purity.",
    "input": {
      "product_image_url": "https://example.com/ring.jpg",
      "shop_name": "Example Jewellers",
      "occasion": "Dhanteras, Friday 6 November 2026"
    },
    "generation_spend_cap_usd": 20
  }'

How do I know it finished?

A 202 returns a run receipt with status_url and result_url. Poll the status, or pass communication.webhook_url to get one signed POST when it completes or fails. Store the run id; a replay with the same key and body returns the original run with idempotency_hit: true instead of starting a second paid run (Create a run, Runs and results).

What should I check before it goes on the counter screen?

Look at every frame of the finished video for invented hallmarks, stones or lettering and re-run with a tighter instruction if any appear; that is why the example tells it not to claim purity. Keep the price and any offer out of the generated video and add them in your own signage, where a wrong digit is easy to fix. Errors and spend lists what a failed run carries if the cap is hit.