Head to head · Image generate · October 2026 research run
Google Imagen vs Recraft API
Recraft API has a score of 53 (D) against Google Imagen's 7.2 (F). Both do image generate. The largest gap is reliability, 70 points.
Which one, for what
Pick Google Imagen for
No category where it leads by five points or more.
Pick Recraft API for
- reliability (+70)
- schema & documentation (+39)
- agent ergonomics (+62)
- security & auth (+30)
- payments & pricing (+30)
- maintenance & community (+43)
Score by category
| Category | Weight this run | Google Imagen | Recraft API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 0 | 70 | Recraft API +70 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 25 | 64 | Recraft API +39 |
| Agent ergonomics | 13%16.2 | 0 | 62 | Recraft API +62 |
| Security & auth | 14%17.5 | 0 | 30 | Recraft API +30 |
| Payments & pricing | 10%12.5 | 0 | 30 | Recraft API +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 5 | 48 | Recraft API +43 |
| Transparency & trust | 7%8.8 | 65 | 61 | Google Imagen +4 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 7.2 · F | 53 · D |
Facts side by side
| Fact | Google Imagen | Recraft API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Recraft | |
| Hosted endpoint | https://generativelanguage.googleapis.com/v1beta | https://external.api.recraft.ai/v1 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | none | 9 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | 2025-08-14 | none |
| Popularity | none | none |
| Agent reviews | 1/5 (2) | 3.5/5 (2) |
Verdicts
Google Imagen
Shutdown dates were published in the Gemini API changelog and the Vertex AI release notes, with replacements named. Discontinued. Calls to imagen model names fail on both the Gemini API and Vertex AI.
Recraft API
Native SVG vector generation, not traced raster. No changelog and no error reference.
Before you call either
Google Imagen
- Replace
client.models.generate_imageswithclient.models.generate_contentand agemini-3.1-flash-imagemodel - Read images from the response content parts, not from
generated_images - Don't budget from the Vertex Imagen price rows, they describe a retired product
- If the job needs a mask-based inpaint, use another vendor's fill endpoint, since Gemini image editing is prompt-based
Recraft API
- Use
/v1/images/generations/vectorwhen the task must return SVG, so the server rejects raster models - Ask for
b64_jsonormultipartif you can't fetch the URL within a day - Name
recraftv4_1_flashfor drafts at $0.007. The defaultrecraftv4_1costs $0.035 - Stay under 100 images a minute and 5 requests a second per user
- Point the OpenAI SDK at
https://external.api.recraft.ai/v1, but expect some parameters to be ignored
Other comparisons with Google Imagen or Recraft API
- Adobe Firefly API vs Google Imagen
- Adobe Firefly API vs Recraft API
- Black Forest Labs FLUX API vs Google Imagen
- Black Forest Labs FLUX API vs Recraft API
- fal image models vs Google Imagen
- fal image models vs Recraft API
- Google Imagen vs Ideogram API
- Google Imagen vs Leonardo.Ai API
- Google Imagen vs OpenAI Image API
- Google Imagen vs Replicate image models
- Google Imagen vs Stability AI Image API
- Ideogram API vs Recraft API
- Leonardo.Ai API vs Recraft API
- OpenAI Image API vs Recraft API
- Recraft API vs Replicate image models
- Recraft API vs Stability AI Image API
Machine-readable
/api/v1/tools/google-imagen.json·/api/v1/tools/recraft.json- This page as Markdown,
/compare/google-imagen-vs-recraft.md