You pay for uniqueness you do not ship
Most Imagen 3 outputs never leave staging—yet still hit the invoice.
CI & fixtures · Imagen 3
CI and Fixtures: Keep Imagen 3 Out of the Pipeline
CI should be deterministic. Live Imagen 3 calls via Vertex AI in tests and Storybook make snapshots flaky and bills noisy—especially for forest green nature campaign frames where visual regression is the whole point.
Where image API costs go off the rails
Storybook and docs should not generate
Component libraries need stable pictures, not live Imagen 3 samples on every build.
Marketing drafts churn images too early
Copy changes five times; Imagen 3 should not bill five hero generations for that.
Team keys multiply chaos
Shared Imagen 3 keys without quotas turn weekend hacks into multi-seat burn.
Scenario: CI & fixtures with Imagen 3
A PR pipeline regenerates images through Imagen 3 for visual tests, email previews, or README builds. Network blips retry jobs; each retry can bill again on Vertex AI. Snapshots never stabilize because the model is non-deterministic. Instead, download licensed fixtures once from Epochal, commit or cache them, and assert against fixed bytes. Keep Imagen 3 experiments in a manual or nightly job with hard budgets—not on every push. Your teammates get green checks; finance gets a flat image line instead of a surprise inference spike.
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 Imagen 3 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 Imagen 3 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 CI & fixtures
Pulled server-side from Epochal tags: server, technology, nature. Previews are cached; API keys never hit the browser.
FAQ
Why is Imagen 3 a bad fit for CI?
Generative outputs are non-deterministic and often metered. CI needs stable fixtures; Imagen 3 is for intentional creative runs.
How many Epochal downloads can CI use?
Original downloads are unlimited serially with one concurrent transfer per account. Plan parallel jobs so they do not fight the single-transfer limit.
What is the request rate limit?
30 requests/minute per account across all keys. Batch metadata where possible; do not fan out one key per micro-job without backoff.