Latency budgets become money budgets
Slow Dev retries encourage parallel calls—and parallel charges.
Version guide · HiDream L1
Document team norms: uniqueness required before any Dev request.
Slow Dev retries encourage parallel calls—and parallel charges.
Defaulting to the highest Dev tier for every draft wastes premium capacity.
Without a stock layer, every page view path can re-trigger Dev.
Unpredictable Dev lines make early unit economics look worse than they need to.
Rate strategy: metadata and search count against 30 requests/minute per account across keys. Design batch-friendly fixture warm-ups rather than chatty per-test Dev queries.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another Dev 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 Dev 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 Dev 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.






Care helps, but architecture helps more. Move non-unique work off Dev entirely with Epochal Stock at $50 USD/month.
No. Epochal serves licensed stock. Keep Dev 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 Dev makes visual tests flaky and expensive.