News from the prompt

A few quick wins on the Batches screen:

• Your own pipelines now sit at the top of the workflow dropdown, then curated pipelines, then single-step tools. The thing you actually built and want to run gets prime real estate.
• True/false parameters render as proper toggles instead of “true” / “false” text inputs.
• Parameter rows match the layout you already know from the API tester: description on the left, control on the right, room to type.
• Need a prompt in your batch? Prompts now show up as a proper text area (and click into the same focused editor used in the API tester).

The upload limit is now 50 MB, up from 20 MB. Anything over about 20 MB gets gently resized server-side before it goes on to the model — typically landing around 1–2 MB at 2048 px on the long edge. Quality stays great for almost every workflow, and you get a heads-up header back telling you what we did so you can tighten your client if you want.

Same image, same SKU filename, smoother turnaround. Particularly handy if your catalog photos come straight off a phone.

If something is too big to handle (over 50 MB), you now get a clear, friendly message that tells you the size limits in plain MB instead of a wall of bytes.

Big batches are sturdier now. If a single file in a run is corrupt or in an odd format, that one item is marked failed and the rest of your batch sails through. No more one bad apple holding up the whole job.

Downloads of finished batch results are a little quicker too.

Upload summer-dress-01.jpg and the result comes back as summer-dress-01, not a random ID. When you’re running hundreds of items through a pipeline, matching outputs back to your SKUs or source files is now effortless.

This applies across single requests and batch jobs.

We reworked how pricing is presented so it’s easier to see what a run costs and what your credits actually get you, with a refreshed pricing page to match.

Pipelines can now take named parameter inputs, so the same flow runs with different values per request instead of hardcoding them. Build one pipeline, reuse it everywhere with the knobs that matter exposed.

Video models now accept a wider range of image inputs, so feeding in a starting frame or reference image is more flexible. We also tidied up billing for video runs along the way.

Google’s Veo video model is now available through apiai.me. Generate video from text or an image with the same one-call simplicity as everything else.

We tuned our video generation for noticeably higher quality results. Same call, better frames.

The whole site and dashboard now come in both light and dark. Choose whichever suits you and we’ll remember it next time you’re back.

We launched AI KNOW, practical writing on AI pipelines, image and video generation, and shipping production AI features faster. You’ll find it linked in the footer under Resources.

Batch jobs now accept uploads up to 200MB and chunk large sets automatically. Push a much larger product catalog through in a single job instead of splitting it up yourself.

Pipelines and flows can now fire an evaluation automatically when they finish, so you get a quality read on your outputs without wiring up anything extra. Especially handy for catching regressions across large runs.

Our Canva app is live. Generate images, run pipelines, and pull in video without leaving your Canva project. Bring AI output straight into the designs you’re already working on.

We now run a public MCP server, so you can drive apiai.me straight from MCP-compatible tools and AI agents. Point your client at it and your pipelines show up as callable tools, no glue code required.

Built a pipeline that works? Share it with teammates so everyone runs the same flow instead of rebuilding it from scratch. Comes with a broader cleanup of team and organisation handling, including clearer member management.

You can now call OpenAI’s image models through the same single endpoint as everything else. Drop them into pipelines alongside Replicate, Gemini and the rest, no extra setup or separate keys to wrangle.