On What an API Is Actually For

A proof of concept. A cover and nine pages, built in a weekend. On Friday, BudgetPixel shipped an API. I jumped on it fast — maybe too fast — and within a day I'd gotten the same question more than once, from people I respect: okay… but what's an API actually good for? It's a fair question. "API" sounds like a developer word. It sounds like the website with all the buttons taken away — a worse version of the thing you already like. If you type a prompt, press a button, and get a beautiful image, why would you want a version with no button? So I'm not going to define it for you. Let me just show you what I did with it. A whole book, one weekend I made Act One of a graphic novel. Nine pages. Thirty-seven panels. One woman who has to look like herself in every single one of them, across two completely different visual styles, with a caption box or a speech balloon on nearly every panel. Here's the part that matters: not one of those pages is a single generated image. Every page is assembled. Page one. Four separate panels, framed and lettered into one page. That's the whole trick, and it's the whole answer to "what's an API good for." Let me walk you through how it actually happened. The loop you already run You type a prompt, press the button, and look. You don't love it, so you tweak a word and press again. You do that a few times, keep the best one, and then start over for the next image. That's a loop. You run it by hand, every time. An API is just that loop, written down once so it runs itself — the same way every time, without ever getting tired, distracted, or sloppy. That's it. That's the whole idea. The website makes you the operator — the one pressing the button. The API lets you be the director — the one who decides what the button does, and then lets something else press it a hundred times exactly the way you said. Once I had that, four things became possible that the website simply can't do. 1. She stays herself — 37 times It's a move you've probably made yourself: you find a face you love, and feed it back in as a reference so the next image is the same person. Now picture not doing that by hand at all. I locked one picture of my lead — her face, early forties, mostly-dark hair — and handed it over once . A turnaround, generated first — then one clean front reference, locked and fed into every panel automatically. Then the loop did what you'd do, thirty-seven times, and never got lazy: every panel, it fed her face back in before pressing the button. That's why she's still recognizably her on page nine. I didn't have thirty-seven disciplined moments. I had one rule, applied thirty-seven times. And here's what most people assume about APIs: that the point is speed . It isn't. The point is consistency . Speed is nice. Consistency is the thing you literally cannot hand-click your way to. 2. Rules I couldn't break even if I wanted to A comic has hard rules. One image per panel — never a whole page in one shot. Never bake the words into the art; lettering goes on top, by hand, later. On the website, I'd break those rules constantly, because the website is happy to let me. It's built to give me one beautiful image, and a beautiful cheat is still a cheat. Written into the loop, those rules just… held. The pipeline didn't get tempted. That sounds small. Over thirty-seven panels, it's the difference between a book and a pile of nice pictures. 3. The thing the website can't do at all Here's the one peek behind the curtain. These four images came out of the generator separately — no borders, no words, just pictures: And this is what the loop did with them — framed each one, arranged them into a page with its own rhythm, and placed every caption and balloon: Four raw images in. One finished, lettered page out. The website makes pictures; it doesn't make pages. There is no button on any image site for that . Composing separate images into a laid-out, lettered page is not a thing you make — it's a thing you build . The API is what let me build it. 4. I only had to figure it out once The same recipe that made page eight made page nine. And page two. And it'll make page ten, and Book Two, whenever I want. That's the quiet superpower. When your work is a loop instead of a session, you don't redo — you re-run . The second page is nearly free. The hundredth page is the same recipe. Who actually made this I should be straight with you, because it's the most interesting part: I didn't draw a single line of this. Two different AIs did the heavy lifting. The image model — through the new API — drew the panels; you already know that one. But the real surprise is the second one: an AI coding assistant wrote the scripts that drove the API, assembled the pages, placed the lettering, and at one point even caught a continuity slip I'd missed, where my lead had drifted too grey from one page to the next. So did I make this, or did the machines? I made it. Here's why I can say that with a straight face: steering is the work. The story is mine. The look is mine. Every call — what's on the page and what's cut, when she's right and when a panel is wrong, what each page is for — that was me, the whole way down. What changed is that my steering was enough . I didn't have to operate anything. That's the shift, taken to its end: you don't even have to write the code that uses the API. You can direct an AI that writes it. Operator to director, all the way up. What it cost This was a proof of concept — a weekend, one person, no studio. It cost somewhere between 5,000 and 6,000 credits . I generated around 137 images and kept 37 — roughly one in four. That's the exact "fire a few, keep the best" loop you already run; the only difference is I ran it like a production line instead of by hand, and the recipe counted the receipts for me. And notice what cost nothing : no studio, no separate letterer, no Photoshop or Illustrator license — the layout tool is free and open-source. One person. One weekend. A cover and nine finished pages. And again — this was just a proof of concept. Both, not either None of this means the website is the lesser thing. The website is where I play — single hero images, chasing a look, getting surprised. It's where I build my styles and argue about how to order a prompt . I'm not giving any of that up. The API isn't better . It's for a different moment — the moment you stop making an image and start making something out of images. There's room for both. I need both. Go look Here's the thing itself — Act One, the actual book, in your browser: → Read The Recollectors, Act One The pages up top are three of nine. Page nine. The last beat of Act One. The whole reason I jumped on this API so fast is that it changed my unit of work — from the image to the book. BudgetPixel just handed you the same loop I used. So: what's the first thing you'd point it at?