compare
Frenchie vs Replicate.
Replicate is a model-hosting platform. Frenchie is an MCP tool your agent calls.
Replicate hosts thousands of open-source models — image generation, upscalers, video, audio, and everything else — behind a REST API. It's a platform: you pick a model, read its schema, write the integration code, and handle the pipeline. Frenchie is a single MCP tool your agent already knows how to call — `generate_image` — backed by one curated image model. If you want model diversity and are willing to wire it up yourself, Replicate wins. If you want your agent to generate an image mid-conversation with zero integration code, that's us.
side by side
The shape of each tool.
| Dimension | Replicate | Frenchie |
|---|---|---|
| Integration surface | REST API, Python/Node SDK, model-specific schemas | MCP tool — `generate_image` appears natively in Claude Code, Cursor, Codex, and every MCP client |
| Agent workflow fit | You write the glue code: auth, polling, image download, file management | Your agent calls one tool; the image lands in your working directory, auto-saved |
| Model choice | Thousands of open-source models — you pick, switch, compare | One curated production image model — we handle upgrades behind the scenes |
| Pricing model | Per-second compute pricing; varies by model, GPU, and runtime | Flat 20 credits per image = $0.20, same rate regardless of prompt |
pick Replicate
When Replicate is the right call
- You want to test and compare multiple image models, or run niche models (ControlNet, upscalers, domain-tuned finetunes).
- You're building an image-heavy product where model selection is a core feature and you'll invest in the integration.
- Your workload includes video, audio, or other modalities Replicate supports that Frenchie doesn't.
pick frenchie
When Frenchie is the right call
- You want your AI agent to generate an image as part of a conversation — mid-chat, next to the work it's already doing — without switching tools.
- You'd rather not write polling loops, download handlers, or file-management code for every image your agent creates.
- You want flat, predictable per-image pricing and zero infrastructure to run.
together
Can you use both?
Reasonable split: Replicate for your production image pipeline where you control the model and squeeze the unit economics. Frenchie for the ad-hoc image your agent generates in a Claude Code or Cursor session — where speed to the image matters more than per-image cost.
questions
The ones that come up.
Can my agent call Replicate through Frenchie?
No. Frenchie is its own MCP tool — call `generate_image` and you get an image back. If you want Replicate-specific models, use Replicate's API directly (or wrap it in your own MCP server).
Is Frenchie cheaper than Replicate?
Frenchie is flat: $0.20 per image. Replicate varies by model and GPU-seconds. For a fast model on a cheap GPU, Replicate can be cheaper per image; for a premium model on an H100, Frenchie is often cheaper and simpler.
Can I pick the image model on Frenchie?
No. Frenchie ships one production image model and handles upgrades behind the scenes. If model choice is the feature you're building on, Replicate is the better fit.
Why not just use Replicate?
Use Replicate when model variety is a feature of your product and you have engineering time to integrate. Use Frenchie when you want your agent to generate an image as a single MCP tool call with zero setup.
See if Frenchie fits.
100 free credits on signup. No card. Give your agent a real image brief from your workflow — compare the generated images side by side.