Rumpelstiltskin Dance AI: Locking a Tip-Toe Barn Meme Template

How I shipped a 1–2 photo → tip-toe barn meme dance on Cloudflare Workers — template lock, guest Stripe, Seedance via TryAllAPI.

rumpelstiltskindance.video turns 1–2 adult photos into a tip-toe / “Wing In My Jawwdinz”-adjacent meme dance short with sound. Independent fan tool (2026), 18+. The homepage does not ask users to storyboard; it locks the motion template and sells the render.

Angle for this post: template lock done with an optional second dancer — similar family to party sites, different farm/barn beat. Prices and model ids change; treat live site / console as source of truth.

Locked motion, optional friend

Create panel pattern:

1. Photo 1 · Lead — required, clear front face.
2. Photo 2 · Friend — optional, only with permission.
3. Fixed tip-toe dance motion template.
4. 720p default messaging; pay once.

Copy on-site refuses celebrity / MV stills. That is load-bearing product policy for face tools — not a legal afterthought.

Live pricing verified: 500 credits · $8.88 · 720p, with multi-packs (e.g. $16.99, larger tiers). Guest Stripe. Always re-check the create button.

Why template lock wins on meme dances

Meme dances are recognizable moves. If you let users rewrite the choreography prompt, you get mush that does not match the sample. Locking the motion:

• Makes demos honest.
• Stabilizes Seedance payloads.
• Shrinks the UX to “good photos + pay.”
• Cuts support threads that start with “why doesn’t it look like the viral clip?”

Stack overview

Layer	Choice	Role
Front / SSR	TanStack Start (Vite)	Landing, upload panel, generation status
Runtime	Cloudflare Workers	Edge deploy, secrets, API routes
DB	Cloudflare D1	Credits, orders, task rows (table prefixes if DBs are shared)
Payments	Stripe Checkout	One-time packs + optional larger packs; guest checkout
Video upstream	TryAllAPI → Seedance	Async create + poll
Analytics	GA	Funnel sanity check

lead (+ optional friend) → tip-toe template
→ check credits (else Stripe)
→ Worker creates Seedance task via TryAllAPI
→ poll until MP4 URL → store / show
→ on failure: refund credits

Why a video API aggregator

Operational checklist after register / top-up:

1. Confirm available USD balance in the console (not only the checkout success page).
2. Create a token in pay-as-you-go style billing.
3. Enable the video / Seedance-related channel group on that token. Wrong group → “no available channel” even when the model id looks right.
4. Prefer separate keys per product (rumpel-prod vs sandbox).
5. Put the key only in Workers Secrets (for example TRYALLAPI_API_KEY). Never in the frontend bundle or a blog post.

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}

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.

Seedance parameters that matter for tip-toe templates

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

• Pass duration as an explicit integer. Some models default to “smart length.” Omitting duration can silently lengthen the clip and the bill.
• resolution and ratio. Cost tracks resolution tier and duration more than portrait vs landscape. Match whatever the create UI offers (often 480p/720p and 9:16 for Shorts).
• generate_audio. When the product ships “finished” downloads, leave audio on; creators who want a trending sound can mute later.
• Status machine. Expect something like queued → running → succeeded / failed. Success URLs are often short-lived signed links — download/rehost on your side before handing the file to the user.
• Decent failure. On supply_unavailable or hard failures: refund credits, show a short human message, log the detailed upstream error server-side, optionally fall back to another Seedance tier.

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

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.

Map lead vs friend roles consistently. Rehost short-lived result URLs. Separate keys if you operate a matrix of dance domains.

Credits, Stripe, and the “can charge money” line

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

1. User hits Create → check credit balance.
2. If short → Stripe Checkout Session (guest allowed).
3. Webhook (plus a return-URL sync check) grants credits.
4. Pre-debit / lock credits, create upstream task, persist task_id in D1.
5. Poll until done; succeed → show MP4; fail → refund credits.

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.

Deploy notes (Workers + D1)

Typical loop on this template family:

pnpm install
# wire D1 database_id, production env, custom domain in wrangler
pnpm cf:deploy

Before calling a deploy “done”:

• D1 binding is correct; shared DBs use table prefixes, not a new database per micro-idea (free-tier DB counts are limited).
• AUTH_TRUSTED_ORIGINS and Stripe return / webhook URLs match the production HTTPS origin.
• GA id is set for a coarse funnel (land → upload → pay → wait → download).
• One real end-to-end path on production or a staging Worker: upload → pay → render → download.

Production origin: https://rumpelstiltskindance.video.

Product rules that are not optional

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

• Require an explicit 18+ / rights-to-use confirmation on upload.
• Block minors and refuse celebrity / stranger misuse in copy and policy.
• Expect upstream safety refusals; refund and explain.
• Keep privacy policy honest about retention; do not train on user media by default.
• Market as an independent fan-style tool for a trend format — not as an official tie-in unless you actually have that deal.
• Use your own sample renders in marketing.

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

What I would reuse on the next tip-toe / barn meme site

1. Lock the recognizable move; do not open a choreography IDE.
2. Lead required + optional friend keeps the funnel simple.
3. Guest one-time pack from ~$8.88 beats subscribe-first.
4. Credits with automatic refund on failed generation.
5. Self-hosted samples sell faster than SEO adjectives.

Consumer: watch the sample on rumpelstiltskindance.video, upload authorized photos, pay once. Builders: TryAllAPI, prove create+poll, then wrap credits. Lock the tip-toe; meter the GPU.