Latency budgets become money budgets
Slow v0.2 retries encourage parallel calls—and parallel charges.
Version guide · Proteus v0.3
Lower v0.2 Costs: When Stock Beats Another Proteus v0.3 Call
Cost control for v0.2 without abandoning Proteus v0.3 when you truly need generative power. Focus on call count, not only host choice—especially for style-flexible anime art boards.
Where image API costs go off the rails
Quality tiers tempt overspend
Defaulting to the highest v0.2 tier for every draft wastes premium capacity.
No cache means no ceiling
Without a stock layer, every page view path can re-trigger v0.2.
Investors notice messy COGS
Unpredictable v0.2 lines make early unit economics look worse than they need to.
Cost notes for v0.2
v0.2 is the reference point many vibecoders default to when they say “just use Proteus v0.3.” It is associated with Community and commonly served via Replicate. Each paid v0.2 generation adds up during prompt loops, A/B tests, and agent retries. If the asset does not need to be uniquely synthesized by v0.2, fetch licensed stock once via Epochal and reuse it across demos, CI, and drafts. Reserve v0.2 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 Proteus v0.3 budgets intentional instead of ambient.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another v0.2 billable call. Prefer Epochal Stock for those slots, then spend Proteus v0.3 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 v0.2 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 v0.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 v0.2
Pulled server-side from Epochal tags: design, abstract, studio. Previews are cached; API keys never hit the browser.
FAQ
Is v0.2 cheaper if I only use it in staging?
Staging volume still bills. If staging does not need unique v0.2 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 v0.2?
No. Agents should default to cached stock or local fixtures. Escalate to v0.2 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.