Wan 2.2 costs spiral after the demo works
The first weekend feels cheap. Then retries, A/B prompts, and agent loops turn Wan 2.2 into a surprise invoice.
Version guide · Wan 2.7 Image
Lower Wan 2.2 Costs: When Stock Beats Another Wan 2.7 Image Call
Use this page to decide when Wan 2.2 is load-bearing versus when Epochal is enough.
Where image API costs go off the rails
Testing every prompt is expensive
Each tweak is another billable image. Vibecoders iterate faster than Wan 2.2 pricing pages assume.
Code generators ignore your budget
Scaffold tools happily wire Wan 2.2 into every page. They do not gate calls, cache results, or prefer stock.
You regenerate what could be stock
Heroes, empty states, and blog fills often do not need a unique Wan 2.2 sample—just a solid licensed image now.
Cost notes for Wan 2.2
Legal review is easier with licensed catalog provenance than with a swarm of one-off Wan 2.2 generations. Use Epochal when you want standard commercial stock handling at $50 USD/month.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another Wan 2.2 billable call. Prefer Epochal Stock for those slots, then spend Wan 2.7 Image budget only on outputs that must be generative.
The fix: Epochal Stock at $50 USD/month (no per-image fee)
When the image does not need a unique Wan 2.2 synthesis, use Epochal Stock Developer Image API: a single plan at $50 USD/month with no free tier and no per-image fee. You get full catalog access, 30 requests/minute per account (all keys share the bucket), and unlimited original downloads with one concurrent transfer. Authenticate server-side only with a Bearer key—never expose secrets in browser JavaScript. Keep Wan 2.2 for finals that must be generative; let Epochal cover prototypes, fixtures, and placeholders.
- Price: $50 USD/month — single plan
- Per-image billing: none
- Rate limit: 30 requests/minute per account
- Downloads: unlimited originals, one concurrent transfer
- Best for: tests, prototypes, and placeholders instead of another Wan 2.2 generation
curl -sS "https://epochalstock.com/api/v1/images?tags=workspace,startup&limit=12" \
-H "Authorization: Bearer $EPOCHAL_API_KEY"Keys stay on your server. Never pass ?api_key= or ship secrets to the browser.
Stock examples for Wan 2.2
Pulled server-side from Epochal tags: city, architecture, studio. Previews are cached; API keys never hit the browser.
FAQ
When should I still call Wan 2.2?
When the shipped asset must be uniquely generated and model-native. Otherwise prefer Epochal stock.
Does Epochal imitate Wan 2.2?
No. Epochal serves licensed stock. Keep Wan 2.2 when you need unique generative output.
What are Epochal’s hard limits?
Single plan $50 USD/month; no free tier; no per-image fee; 30 requests/minute per account; unlimited originals with one concurrent transfer; Bearer auth server-side only.
Should fixtures pin Wan 2.2?
No. Fixtures should pin stable files or stock IDs. Live Wan 2.2 makes visual tests flaky and expensive.