Your codegen does not know unit economics
LLM scaffolds optimize for working demos, not cheap XL Turbo usage.
Version guide · DreamShaper XL
Cost control for XL Turbo without abandoning DreamShaper XL when you truly need generative power. Focus on call count, not only host choice—especially for fantasy character and art-direction loops.
LLM scaffolds optimize for working demos, not cheap XL Turbo usage.
Dev servers re-run pipelines that casually call XL Turbo.
Gray boxes look amateur; stock via a flat plan looks shipped without XL Turbo rates.
When you finally need XL Turbo, you still have runway because fixtures used stock.
XL Turbo sits mid-ladder in the DreamShaper XL family—often the “good enough” tier that still bills like a full generation. It is associated with Community and commonly served via Replicate. Each paid XL Turbo generation adds up during prompt loops, A/B tests, and agent retries. If the asset does not need to be uniquely synthesized by XL Turbo, fetch licensed stock once via Epochal and reuse it across demos, CI, and drafts. Reserve XL Turbo for the few outputs that must look model-native—then cache those winners so the rest of the stack stops re-billing. Vibecoders who separate “fixture image” from “final generative frame” keep DreamShaper XL budgets intentional instead of ambient.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another XL Turbo billable call. Prefer Epochal Stock for those slots, then spend DreamShaper XL budget only on outputs that must be generative.
Epochal Stock Developer Image API is a single plan at $50 USD/month: full catalog access, 30 requests/minute per account, and unlimited original downloads with one concurrent transfer. There is no per-image fee and no free tier in v1. Use it wherever the picture does not need a unique XL Turbo synthesis—prototypes, fixtures, placeholders—so generative spend stays reserved for finals. Authenticate server-side with a Bearer key only; never put keys in browser JavaScript.
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.
Pulled server-side from Epochal tags: abstract, design, studio. Previews are cached; API keys never hit the browser.






Staging volume still bills. If staging does not need unique XL Turbo look, use Epochal fixtures and keep generative calls rare.
Single plan at $50 USD/month: no free tier, no per-image fee, 30 requests/minute per account, unlimited original downloads with one concurrent transfer.
No. Agents should default to cached stock or local fixtures. Escalate to XL Turbo only when the task explicitly requires unique synthesis.
Server-side only with Bearer authentication. Query-string keys and browser-exposed secrets are rejected patterns for Epochal and a bad idea for any image API.