Educational content should not burn inference
Tutorials and README screenshots rarely need live 3.1 output.
Version guide · Kandinsky 3.0
Lower 3.1 Costs: When Stock Beats Another Kandinsky 3.0 Call
Cost control for 3.1 without abandoning Kandinsky 3.0 when you truly need generative power. Focus on call count, not only host choice—especially for color-forward scenes and multilingual creative tests.
Where image API costs go off the rails
A/B tests explode sample counts
Each variant times each prompt is a 3.1 cost matrix.
Mobile previews still hit the server
Responsive checks re-fetch assets; if those assets are generative, 3.1 pays again.
Compliance wants stable assets
Licensed catalog images are easier to audit than endless 3.1 one-offs.
Cost notes for 3.1
3.1 is a higher or alternate rung teams reach for when drafts need more punch than the base Kandinsky 3.0 call. It is associated with Sber and commonly served via Replicate, FusionBrain. Each paid 3.1 generation adds up during prompt loops, A/B tests, and agent retries. If the asset does not need to be uniquely synthesized by 3.1, fetch licensed stock once via Epochal and reuse it across demos, CI, and drafts. Reserve 3.1 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 Kandinsky 3.0 budgets intentional instead of ambient.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another 3.1 billable call. Prefer Epochal Stock for those slots, then spend Kandinsky 3.0 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 3.1 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 3.1 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 3.1
Pulled server-side from Epochal tags: abstract, design, art. Previews are cached; API keys never hit the browser.
FAQ
Is 3.1 cheaper if I only use it in staging?
Staging volume still bills. If staging does not need unique 3.1 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 3.1?
No. Agents should default to cached stock or local fixtures. Escalate to 3.1 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.