MCP or a REST API: how to call image and video generation
The tradeoffs when you wire generation into an agent versus into your own backend code.
Two paths to the same models
Whether you call over MCP or over a REST API, the model doing the work is the same. Figgshield runs Nano Banana 2 for images and Kling 3 for video, and both paths end at the same render. What changes is who makes the call and how much code you write around it.
A REST integration means your own code sends an HTTP request to a generation endpoint, reads the response, and moves on. An MCP integration means an AI agent sees a tool, fills in the arguments, and calls it for you. Figgshield is the MCP path, reachable at https://api.figgshield.ai/mcp.
Neither is better in the abstract. The right answer depends on whether an agent is in the loop or your code is running headless with nobody watching.
What changes when an agent is the caller
Over MCP, the agent reads the tool list on connect. It sees generate_image and generate_video with their parameters and can decide to call them mid-task, without you installing an SDK or hardcoding an endpoint URL.
The results come back as structured data the agent can act on. It can generate an image, take the returned id, and pass it to a video call to animate that exact frame, all inside one conversation. You describe the outcome, not the plumbing.
With a REST API you write that plumbing yourself. You build the request, parse the JSON, store the id, and call the next endpoint. It is entirely doable, it is just code you own and maintain.
Where a REST integration is the better fit
If you are running a headless pipeline with no agent in it, a REST integration is the natural choice. A nightly batch that renders a thousand product shots does not need a conversation. It needs a loop, a queue, and error handling you control line by line.
REST also travels anywhere. Any language with an HTTP client can call it, so it slots into a Go service, a Python worker, or a CI job with no MCP-capable host present. When the caller is a server rather than an assistant, that portability matters.
You get exact control over retries, timeouts, and concurrency too. For high-volume or latency-sensitive work, owning that loop is a feature, not a chore.
Where MCP pulls ahead
When a person and an agent are working together, MCP removes the glue. You stay in Claude Code, Cursor, Windsurf, or ChatGPT in Developer Mode, ask for the image or clip, and it appears in the same session. No tab switch, no download-and-drag.
The agent chains steps you would otherwise wire by hand. Video from Figgshield is queued rather than instant, and the agent polls get_generation until the clip is ready without you writing a poll loop. Image calls return in the same response.
For prototyping, iteration, and any workflow where the agent already lives, this is less code and less context switching. The model output arrives as part of the work you were already doing.
Auth and who holds the keys
A REST integration means you manage credentials. You store an API key, keep it out of version control, rotate it, and scope it. That is standard practice, and it is one more secret to look after.
Over MCP you connect the server through your client once and sign in there. Your agent gains the tools without a key sitting in your code or your environment. For a shared editor or a quick experiment, that is one less thing to leak.
Both models can be secured well. The difference is where the secret lives and who is responsible for it day to day.
The cost is the same on either path
The integration style does not change the price. Figgshield bills at cost with no markup on the models. An image at 1K or 2K is 8 credits and 4K is 16. A five second video clip is 35 credits. One balance covers both images and video.
We make money only on credits people buy and never spend, so our interest is that you actually use what you paid for. The credits page shows how far a balance goes.
There is no free tier. You can start on the $5 7 day Pro trial, which includes 150 credits. Cancel before it renews and you pay nothing more.