Image API
Keep the public image API narrow and intentional. Route users into GPT-Image-2 for broad creative coverage, and Nano Banana 2 when grounded reference workflows matter.
This page is intentionally framed as the public image API direction and model scope page. The codebase already has internal image generation routes, but it does not yet expose the same public API key surface that the video API does.
Public image models
Principles
Keep the external image API intentionally small so model choice stays obvious and support burden stays manageable.
Expose models that can cover both clean prompt-led generation and more grounded reference-based image work.
Send traffic from the capability page into model-specific pages when users need a deeper fit or stronger positioning.
Routing guide
When the goal is broad creative coverage, polished outputs, and a straightforward public-facing image API promise.
When grounded references, multi-reference flexibility, or web-aware creative workflows matter more.
Scope
Roadmap fit
Use this page to frame the public image lineup, qualify interest, and direct people into the model pages that already exist.
If you later expose public image API routes, this page can evolve from scope-setting into a true endpoint and onboarding page.
FAQ
Yes. The repo already contains internal image generation routes and model integrations. This page is careful not to overstate that as a public API surface yet.
Because the public contract is not identical yet. Video already has public API key routes, while image is still better described as a public model scope and onboarding direction page.
Promise the model lineup and the workflow direction. Avoid promising a fully exposed public image REST contract until that route actually exists in code.