Sber · generative image API cost guide

Curb Kandinsky 2.2 API Costs for Vibecoders

If your Cursor, Claude, or agent stack keeps calling Kandinsky 2.2 for painterly multilingual storyboards, bills climb faster than the demo justifies. This page maps where Kandinsky 2.2 costs explode for vibecoders—and when licensed stock on a flat plan is the smarter default. Keep generative power for finals; stop paying unique synthesis rates for chrome you could catalog once.

Prototyping CI & fixtures Content placeholders 2.1 2.2

Stock examples for Kandinsky 2.2 cost control

Pulled server-side from Epochal tags: abstract, design, studio. Previews are cached; API keys never hit the browser.

Cozy Luxury Den With Walnut Paneling and Warm Lighting in Evening — stock example for Kandinsky 2.2 cost control — Cozy Luxury Den With Walnut Paneling and Warm Lighting in Evening

Sustainability Team at Workshop Repairing Electronics With Smiles — stock example for Kandinsky 2.2 cost control — Sustainability Team at Workshop Repairing Electronics With Smiles

Romantic Bedroom With Canopy Bed and Warm Lighting — stock example for Kandinsky 2.2 cost control — Romantic Bedroom With Canopy Bed and Warm Lighting

Where image API costs go off the rails

Codegen optimizes for demos, not COGS

LLM scaffolds wire Kandinsky 2.2 for working screenshots, not for cheap unit economics.

Hot reload re-runs cold image pipelines

Dev servers casually re-call Kandinsky 2.2 every save when fixtures are not pinned.

Placeholders deserve a real image API

Gray boxes look unfinished; stock via a flat plan looks shipped without Kandinsky 2.2 rates.

Protect generative budget for the wow moment

When you truly need Kandinsky 2.2, runway remains because fixtures used stock.

About Kandinsky 2.2 and why bills climb

Kandinsky 2.2 is associated with Sber and is commonly reached via Replicate. The version ladder around this page includes: 2.1, 2.2. Typical vibecoder tags here are multilingual, paint, scene. Hosted inference on Replicate (and similar) bills by runtime or per output, so agent loops and CI can still surprise you. Per-image, credit, or subscription burn all punish the retry-heavy loops codegen and agents produce—so cost control means fewer unique calls, not only a cheaper host.

Still use Kandinsky 2.2 when the asset must be model-native: brand-specific heroes, one-off product composites, prompt research you will actually ship, or style experiments that only this model nails. Do not burn Kandinsky 2.2 capacity on every empty state, CI snapshot, or blog filler that a licensed catalog image can cover.

Versions worth tracking

Version	Cost angle
2.1	Each paid call still stacks during vibecoder retries—prefer stock when uniqueness is optional.
2.2	Each paid call still stacks during vibecoder retries—prefer stock when uniqueness is optional.

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 Kandinsky 2.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 Kandinsky 2.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.

Get the Epochal developer API See pricing details

More licensed examples for non-unique Kandinsky 2.2 slots

Pulled server-side from Epochal tags: abstract, design, studio. Previews are cached; API keys never hit the browser.

Wellness Bathroom With Sauna and Candles in Modern Setting — stock example for Kandinsky 2.2 solution examples — Wellness Bathroom With Sauna and Candles in Modern Setting

Elegant Interior Space With Bookshelves and Sunset View — stock example for Kandinsky 2.2 solution examples — Elegant Interior Space With Bookshelves and Sunset View

Palatial Chef's Kitchen With Marble Waterfall and Evening Light — stock example for Kandinsky 2.2 solution examples — Palatial Chef's Kitchen With Marble Waterfall and Evening Light

Sustainability Team Working Together in a Workshop — stock example for Kandinsky 2.2 solution examples — Sustainability Team Working Together in a Workshop

Private Gym With Mirrored Walls by Lakefront in Sunny Daylight — stock example for Kandinsky 2.2 solution examples — Private Gym With Mirrored Walls by Lakefront in Sunny Daylight

Grimy Communal Bathroom With Rusty Pipes and Vintage Bathtub — stock example for Kandinsky 2.2 solution examples — Grimy Communal Bathroom With Rusty Pipes and Vintage Bathtub

Use-case playbooks

Prototyping

Ship local demos, Cursor/Claude scaffolds, and throwaway UIs without paying per generated image.

CI & fixtures

Stable test images, screenshot baselines, and design fixtures without regenerative API bills.

Content placeholders

Fill marketing and editorial slots with licensed stock while you save generative calls for final creatives.

FAQ

Is Epochal free if I already pay for Kandinsky 2.2?

No. Epochal Stock Developer Image API v1 is a single paid plan at $50 USD/month with no free tier and no per-image credits.

Does Epochal replace Kandinsky 2.2 entirely?

No. Keep Kandinsky 2.2 when you need unique generative output. Use Epochal when licensed stock is enough—tests, demos, and many content slots—so Kandinsky 2.2 bills stay controlled.

What is the Epochal API rate limit?

30 requests/minute per account. Extra API keys do not multiply the limit; they share the same account bucket.

How should vibecoders mix stock and Kandinsky 2.2?

Default fixtures and placeholders to Epochal (Bearer key server-side only). Reserve Kandinsky 2.2 for the few frames that must be uniquely synthesized, and cache anything that will be reused.