Bad Times AI: Lower Entry Price, One Photo, and Credit Refunds That Build Trust

How I shipped a one-photo → quarrel / lip-sync dance product on Cloudflare Workers — honest “not free” pricing, Stripe credits, Seedance via TryAllAPI.

badtimesai.cc takes 1 clear person or pet photo → ~15s 9:16 quarrel / lip-sync dance MP4 with original AI ambient audio. Browser + Stripe. Independent fan tool — not affiliated with song/artists/TikTok creators named in the meme. Person templates 18+ with likeness rights.

Angle: Stripe credits + accessible entry pricing (from $6.90), plus explicit “failed generations refund credits” next to the sell. Prices and model ids change; treat live site / console as source of truth.

Pricing honesty as UX

The hero says packs from $6.90 (one-time, no subscription) and repeats not free. That filters tire-kickers who only want infinite free GPU and sets expectations for a paid render.

Other tiers visible in page copy while writing include $9.90 and $16.90-style packs — verify live before quoting. Guest checkout path keeps friction low for “I just want one quarrel clip.”

One photo, multiple scene entries

Unlike strict two-face booths, Bad Times leans one reference with alternate scenes (person / pet / character messaging) and a “describe any idea” adjacent path on the page. The credit system still has to:

1. Grant credits after Stripe.
2. Debit before upstream create.
3. Refund on failure / safety block.

Why refunds are marketing: face video fails for boring reasons — supply, safety, blurry input. If credits vanish silently, you get chargebacks. If credits restore automatically, the $6.90 experiment feels safe.

Stack overview

1 photo (+ scene choice) → quarrel / lip-sync 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 (badtimes-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 for one-photo quarrel clips

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.

Keep TryAllAPI USD as COGS; site credits as the customer meter. Rehost signed MP4 URLs. Lower entry pricing only survives if you measure real runs including refunds.

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://badtimesai.cc. Isolate webhook metadata if Bad Times shares a Stripe account with sister dance domains.

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 lower-entry one-photo site

1. Say not free out loud; then show the entry pack.
2. Put refund language next to the price.
3. One clear reference beats a confusing multi-upload for this meme.
4. Aggregator keeps the Worker thin.
5. Measure COGS before racing to the bottom on price.

Consumer: upload one clear authorized photo at badtimesai.cc. Builders: TryAllAPI, measure COGS, then set an entry pack that still survives refunds. Cheap only works when failure is refundable.