Latency budgets become money budgets
Slow Full retries encourage parallel calls—and parallel charges.
Version guide · HiDream L1
Latency and cost both drop when non-unique Full traffic moves to catalog fetch.
Slow Full retries encourage parallel calls—and parallel charges.
Defaulting to the highest Full tier for every draft wastes premium capacity.
Without a stock layer, every page view path can re-trigger Full.
Unpredictable Full lines make early unit economics look worse than they need to.
Download strategy: resolve image IDs in Epochal, create single-use download URLs, and store binaries. Avoid parallel original transfers; the account allows one concurrent download.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another Full billable call. Prefer Epochal Stock for those slots, then spend HiDream L1 budget only on outputs that must be generative.
When the image does not need a unique Full 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 Full for finals that must be generative; let Epochal cover prototypes, fixtures, and placeholders.
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.






When the shipped asset must be uniquely generated and model-native. Otherwise prefer Epochal stock.
No. Epochal serves licensed stock. Keep Full when you need unique generative output.
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.
No. Fixtures should pin stable files or stock IDs. Live Full makes visual tests flaky and expensive.