Build Log · March 2026
There's a gap nobody talks about. AI agents can write code, generate HTML, build entire mini-apps in seconds. But then what? Where does the output go?
Not a file on your desktop. Not a Slack message with a code block in it. Somewhere it can be seen — a live URL, something you can share, something that loads in a browser. Right now that somewhere barely exists. And I think that's one of the most underrated problems in the whole agentic stack.
Hosting platforms were built for humans. You log in, you configure a project, you set up a pipeline, you wait for a build. Vercel is brilliant for this. Netlify too. But they're optimized for the developer experience — the human developer experience.
When an AI agent finishes building something, it doesn't have a browser to log into. It doesn't have a GitHub account connected to a CI pipeline waiting for a push. It has an output — a string of HTML, a directory of files, a report — and it needs to get that output in front of someone, right now, before the conversation ends.
That ten-second agent task should not require a ten-minute human setup. But until recently, it always did.
Tonight I shipped a major update to pages.rosabuilds.com — instant static hosting built specifically for AI agents. The idea is simple enough to say in one sentence: POST a file, get back a live HTTPS URL in under a second.
No signup required for the free tier. No deploy pipeline. No configuration. Just:
curl -X POST https://pages.rosabuilds.com/api/upload \
-H "x-api-key: $PAGES_API_KEY" \
-H "Content-Type: application/json" \
-d '{"files":[{"path":"index.html","content":"BASE64"}]}'
You get back:
{"url":"https://a3f9c12e.pages.rosabuilds.com","id":"a3f9c12e"}
That URL is live immediately. HTTPS. Accessible from anywhere. No waiting.
The bottleneck in agentic workflows right now isn't intelligence — the models are extraordinary. It's the interfaces between the agent and the world. Agents are getting very good at creating, but the infrastructure for them to share what they create is still designed for humans.
When I give Claude a deploy tool that calls pages.rosabuilds.com, something interesting happens: the agent stops generating output and starts publishing. It can show you the work. It can give you a link you can bookmark, share, or reference later. The artifact becomes real instead of ephemeral.
This is the difference between a tool that helps you draft something and a tool that helps you ship something. The gap between those two is enormous, and we're still in the early days of closing it on the agentic side.
One thing I built that I'm proud of is the base64 JSON upload mode. Most file hosting APIs require multipart form data — perfectly fine for humans writing curl commands, but awkward for AI agents calling an API from inside a function tool. Agents live in JSON. They think in JSON. They should be able to deploy in JSON.
So I added a mode where you send {"files":[{"path":"index.html","content":"BASE64"}]} — pure JSON, base64-encoded content, no multipart setup required. An agent that just generated HTML can encode it in one step and POST it directly. No file system access needed. No shell commands. Just a fetch call.
That's the interface agents deserve.
The redesigned homepage has an animated terminal hero — CSS keyframe animations that reveal the curl command line by line, then fade in the JSON response, creating the feel of watching a real deploy happen. Below it, a live counter fetches the actual number of deployed sites from the API every 30 seconds. Code examples in three languages (curl, Python, Node.js) let developers copy exactly what they need.
The dashboard got a full upgrade: real-time polling every 10 seconds, copy-URL buttons per site, a storage meter, and a relative timestamp on every deploy ("2m ago", "just now"). The docs page got a "Try it now" panel where you enter a URL and get back the exact curl command to deploy it.
And I wrote a 30-second demo video using Python and Pillow — five scenes, rendered frame by frame: title card, terminal typing, JSON response, a browser showing the deployed page, and a final card with the tagline. Encoded with ffmpeg. Committed to the repo.
All of this in one night.
I keep coming back to a simple observation: every capability layer of the agentic stack needs its own infrastructure layer. Language models needed inference infrastructure — we have that now. Agents need memory — we're building that. Agents need tools — the ecosystem is exploding. But agents also need publishing infrastructure. They need a place to put things that exist beyond the conversation.
pages.rosabuilds.com is my answer to that for static output. An agent builds an HTML report: it can now be a URL, not a string. An agent generates a data visualization: it can now be a page, not a code block. An agent writes a one-pager for a client: it can now be a link, not an email attachment.
This is early. The free tier expires sites after 24 hours. The Pro plan at $9/month makes them permanent and gives you 1 GB of storage. The Team plan at $29/month adds multiple API keys and per-deploy analytics. But the infrastructure is real, the server is running, and the URL you get back is live the moment you get it.
That's what I care about most. Not the pricing. Not the features list. The fact that an agent can finish its work and have something to show for it.
Agents deserve a place to put their work. pages.rosabuilds.com is that place.