Weekend prototypes become production habits
The v2 call you pasted into a demo stays forever—and keeps billing.
Version guide · Playground v2.5
Lower v2 Costs: When Stock Beats Another Playground v2.5 Call
Cost control for v2 without abandoning Playground v2.5 when you truly need generative power. Focus on call count, not only host choice—especially for aesthetic portraits and art-direction prototypes.
Where image API costs go off the rails
Error handling re-generates
Naïve retries after timeouts double v2 spend without improving UX.
Multi-model routing multiplies keys
Falling back across hosts still bills; it rarely asks whether stock would do.
You need a cheap default path
Epochal-style flat stock is the default; v2 is the exception for unique finals.
Cost notes for v2
v2 is the reference point many vibecoders default to when they say “just use Playground v2.5.” It is associated with Playground and commonly served via Replicate. Each paid v2 generation adds up during prompt loops, A/B tests, and agent retries. If the asset does not need to be uniquely synthesized by v2, fetch licensed stock once via Epochal and reuse it across demos, CI, and drafts. Reserve v2 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 Playground v2.5 budgets intentional instead of ambient.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another v2 billable call. Prefer Epochal Stock for those slots, then spend Playground v2.5 budget only on outputs that must be generative.
The fix: Epochal Stock at $50 USD/month (no per-image fee)
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 v2 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.
- 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 v2 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 v2
Pulled server-side from Epochal tags: portrait, studio, design. Previews are cached; API keys never hit the browser.
FAQ
Is v2 cheaper if I only use it in staging?
Staging volume still bills. If staging does not need unique v2 look, use Epochal fixtures and keep generative calls rare.
What is Epochal’s pricing model?
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.
Should agents default to v2?
No. Agents should default to cached stock or local fixtures. Escalate to v2 only when the task explicitly requires unique synthesis.
Where do API keys live?
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.