Gemini Imagen Shutdown: Migrate Image Tools Before August 17
Google is shutting three Imagen 4 API model IDs on August 17, 2026. Migrate production image workflows to Gemini image generation with a measured cutover and rollback.
From this desk
Start with the most useful page
The featured page offers a strong introduction. The remaining cards help readers move through this editorial section without turning the archive into a service menu.
Read the featured method
Keep the method with the result
A useful workflow story records the account state, request, expected output, retained evidence, and stop condition beside the result.
API behavior
Compare API behavior
Record method, parameters, filters, cache behavior, timestamps, and response differences before choosing an integration.
Index freshness
Make synchronization observable
Keep job IDs, changed-file evidence, retries, cancellation, and sentinel retrieval visible when CI triggers an index update.
Citation checks
Audit the answer against its sources
Preserve the response, map citations to claims, and separate retrieval quality from the final wording.
Privacy controls
Keep location and storage boundaries separate
Verify processing location, stored data, logs, provider settings, and regional limits as distinct controls.
Latest stories
Latest Tools & Workflows articles
Read the archive in publication order. Each story focuses on one implementation question and keeps its inputs, failures, evidence, and limits visible.
-
-
OpenAI API Usage by Key: Reconcile Research Spend Without Exposing Secrets
Group OpenAI usage by API key ID, reconcile billed cost at the project level, and record the boundary with a 24-field privacy-safe ledger.
-
Claude Managed Agents Budgets: A Research Run-Control Method
Control Claude Managed Agents research with session budgets, authoritative event records, unfinished-work manifests, observable advisor interventions and versioned resume decisions.
-
Claude Inference Hooks: A Shadow-to-Enforce Release Gate
Deploy Claude inference hooks with signed-request verification, shadow review, explicit verdicts, tested failure modes, latency thresholds, incident ownership and rollback.
-
Gemini API Key Migration: Build a 30-Field Cutover Register
Migrate Gemini API Standard keys with a 30-field register, a current September cutover decision, production-path testing, telemetry and rollback.
-
Gemini Grounding: Trace Citations and Missing Source Evidence
Trace Gemini Search calls, source records and support mappings across two API surfaces, then stop structured output when provenance evidence is missing.
-
Gemini Business Profile Changes: An Approval and Audit Workflow
Use Gemini with one eligible Google Business Profile through read, draft and change tiers, source-of-truth checks, approval records, public verification and rollback.
-
Perplexity MCP: Hosted Server, OAuth and Custom Connectors
Compare the two Perplexity MCP directions, where credentials live, which system calls the tools, and what a private connector cannot prove about public visibility.
-
Kagi Search API Migration: Test Related Searches and Preserved Links
Migrate Kagi Search API collectors by preserving raw responses, separating related queries from results, retaining original and normalized links, testing unknown types and canarying the parser.
A useful standard
What makes a workflow trustworthy
A workflow is useful when another person can inspect what went in, what happened, what failed, and why the result changed a decision.
Inputs before outputs
Preserve the request, configuration, account state, environment, and relevant versions before interpreting the response.
Failures remain in the record
Keep timeouts, empty results, parser errors, retries, and zero-result runs. Removing them hides how the real system behaves.
Secrets stay out of evidence
Use stable internal labels for credentials and redact tokens, personal data, and licensed content that should not enter a report.
References and next steps