Raindance AI: Clip-Length Pickers, Head-Swap vs Whole-Person, and Seedance via TryAllAPI

Posted on Oct 31 • Originally published at raindanceai.app

How I shipped a timeline-aware Raindance remake product on Cloudflare Workers — where duration knobs drive Seedance costs through TryAllAPI.

raindanceai.app is not “upload and hope.” Users pick solo (1 photo) or duet (2 photos), choose Head swap or Whole person, then select a 3–10s moment from the trend clip (including quick Part 1 / 2 / 3 for a full ~30s stitch later in CapCut). Output is an MP4 ready for Shorts/Reels.

This post focuses on the API + duration economics side: why an aggregator, which Seedance knobs matter, and how pricing from $5.99 maps to credits. Prices and model ids change; treat live site / console as source of truth.

Unlike one-shot 15s party templates, Raindance exposes length:

That means the Worker must pass explicit duration every time. Omitting duration and letting the model “pick a smart length” is how bills drift — and how a $5.99 entry pack silently loses money.

Live pricing seen on the homepage while writing: packs from $5.99, with other tiers such as $9.99 one-video credit messaging and multi-packs ( $23.99 / $14.99 / $36.99 variants appear in copy). No subscription required for the core path. Re-check the create CTA before you quote a friend.

solo/duet photos + length + mode → locked Raindance template prompt → check credits (else Stripe) → Worker creates Seedance task via TryAllAPI → poll until MP4 URL → store / show → on failure: refund credits Enter fullscreen mode Exit fullscreen mode

Demo clips / scene stills are self-hosted with the product. Do not scrape other CDNs for marketing.

Direct vendor onboarding for every video model means accounts, KYC, docs drift, and different async status machines. For a small indie product I wanted one API key in Workers Secrets, USD balance billed by usage, and a path to Seedance without rewriting the client each time the console UI changes.

That is what TryAllAPI is for on this project.

Operational checklist after register / top-up:

Conceptually the call shape looks like this (field names follow the aggregator’s v3 contents API; always re-check current docs):

POST /api/v3/contents/generations/tasks Authorization: Bearer <TRYALLAPI_API_KEY> Content-Type: application/json Accept-Encoding: identity GET /api/v3/contents/generations/tasks/{id} Enter fullscreen mode Exit fullscreen mode I send Accept-Encoding: identity from the Worker because some gateways behave badly with transparent decompression. Model ids used in production look like Seedance 2.x family strings — treat console ids as source of truth, not this paragraph.

A few details that bit me across this family of sites:

Rough mental model for upstream cost (illustrative only — use your own usage fields and invoices):

tokens ≈ duration_sec × width × height × fps / 1024 cost ≈ tokens × price_per_million_tokens Enter fullscreen mode Exit fullscreen mode Price the site after you measure a few real runs with retry margin, Stripe fees, and failed-job refunds — not from a spreadsheet fantasy of 0% failure.

Demo UIs are easy. The line between toy and product is:

Two books of account stay separate: USD balance at TryAllAPI (your cost) vs site credits (what you sold). Mixing them in one mental ledger is how you underprice or invent “mysterious” losses.

When several products share one Stripe account, isolate webhooks by endpoint or by metadata ( site / product ). Callbacks pointed at the wrong apex domain are a classic multi-site footgun.

Secrets stay in Workers: TRYALLAPI_API_KEY, STRIPE_SECRET_KEY, webhook secret, auth secrets. The browser only ever sees publishable Stripe keys if needed.

Raindance’s lower entry ( from $5.99 ) only works if short clips dominate, duration is explicit, and failure refunds are automatic. Measure COGS on 3s vs 10s before locking pack prices.

pnpm install # wire D1 database_id, production env, custom domain in wrangler pnpm cf:deploy Enter fullscreen mode Exit fullscreen mode Before calling a deploy “done”:

Production origin: https://raindanceai.app.

Face-based generation is not “just another SaaS CRUD app”:

Those constraints belong in the product, not in a footnote you add after the first dispute email.

Consumer: raindanceai.app. Builder: TryAllAPI, top up, prove create+poll, then wire credits. Pick the second, bill the second, poll until MP4.