Latency budgets become money budgets
Slow SSD-1B retries encourage parallel calls—and parallel charges.
Content placeholders · SSD-1B
Content Placeholders Without Burning SSD-1B
Content drafts change faster than art direction. Using SSD-1B for every placeholder turn burns budget on words that will rewrite tomorrow—especially when the theme is fast mobile and app chrome drafts.
Where image API costs go off the rails
Quality tiers tempt overspend
Defaulting to the highest SSD-1B tier for every draft wastes premium capacity.
No cache means no ceiling
Without a stock layer, every page view path can re-trigger SSD-1B.
Investors notice messy COGS
Unpredictable SSD-1B lines make early unit economics look worse than they need to.
Scenario: Content placeholders with SSD-1B
A marketing site, docs portal, or newsletter uses SSD-1B to fill hero and card slots while copy is still fluid. Each editorial pass regenerates images “just in case.” Stakeholders review layout, not generative novelty—so unique synthesis is wasted. Swap non-final slots to Epochal catalog images: real, licensed, searchable, and flat-priced. When the headline freezes and the brand needs a one-of-a-kind frame, run SSD-1B once, cache the winner, and stop the churn. Editors move faster because nobody is waiting on inference or arguing about credit burn mid-draft.
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 SSD-1B 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 SSD-1B 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 Content placeholders
Pulled server-side from Epochal tags: marketing, design, technology. Previews are cached; API keys never hit the browser.
FAQ
Are stock placeholders good enough before SSD-1B finals?
For most drafts, yes. Stakeholders evaluate hierarchy and message first. Save SSD-1B for the locked creative that must look model-native.
Is there a free Epochal tier for drafts?
No. v1 is a single paid plan at $50 USD/month with no free tier and no per-image credits.
How do downloads work for CMS pipelines?
Create a five-minute single-use download URL with your server Bearer key, then fetch the binary without the key. Unlimited originals serially; one concurrent transfer.
What if legal needs provenance for images near SSD-1B experiments?
Catalog stock is easier to license and audit than endless one-off generations. Keep generative finals documented separately when you do use SSD-1B.