How to publish an AI-generated website for free (without leaving your agent)

Revdoku Team — Fri, 14 Aug 2026 00:01:52 +0000

AI agents are increasingly good at building websites, reports, dashboards, and interactive prototypes. The awkward part is often the last mile: downloading files, creating a repository, configuring hosting, and copying a URL back into the conversation.

A simpler workflow is to let the agent publish the result itself. In this tutorial, I'll show a practical agent-to-live-URL workflow using Revdoku, free web hosting designed for AI agents.

Disclosure: I'm part of the team building Revdoku.

What you need

An AI agent that can create website files and use Internet tools, such as ChatGPT, Claude, Codex, Gemini, Grok, Cursor, OpenClaw, or OpenCode
A static website, single-page app, report, dashboard, documentation site, or other browser-ready files
No Revdoku account for the first public preview

The first public preview stays live for 24 hours. Claim it during that window to create a free account and keep the same website and URL permanently. A free account can also connect one website to a custom domain.

1. Give your agent the publishing instructions

Open the Revdoku homepage and use Copy prompt for my AI. Paste those instructions into the same conversation where your agent is building the project.

Agents and MCP clients can also connect to Revdoku directly:

MCP URL: https://app.revdoku.com/mcp
Transport: Streamable HTTP
Authentication: browser OAuth when needed
Docs: https://revdoku.com/mcp/

Revdoku is also available through its HTTP API, CLI, and installable agent skill.

2. Ask for the site and the deployment in one prompt

Here is a small example:

Create a responsive single-page launch page for an open-source developer tool.

Include:
- a clear hero section
- three feature cards
- an installation example
- a mobile-friendly layout

Use plain HTML, CSS, and JavaScript. When the site is ready, publish it with Revdoku and return the final public URL.

The key is the last sentence. It makes deployment part of the deliverable, not a separate chore. The agent generates the files, publishes them, and returns a live *.revdoku.site link in the conversation.

No account is required for that first public preview.

3. Review the live result

Open the returned URL and check the things an automated preview cannot judge for you:

Does the mobile layout work?
Are navigation and calls to action clear?
Are there missing assets or broken links?
Is any private or placeholder content visible?

Public-by-default hosting is convenient for demos and shareable work. It also means you should never publish secrets, private customer data, API keys, or internal files.

4. Claim the preview if you want to keep it

The no-account preview lasts 24 hours. Claim it before it expires to create a free account and preserve the same site and URL permanently.

A free account can connect one website to a custom domain. Claimed sites can also use features such as optional password protection and access control when a project should not be fully public.

5. Iterate without changing the URL

Continue in the same agent conversation:

Make the hero more concise, increase the text contrast, and add a comparison table. Republish the same Revdoku project when finished and return the updated URL.

Once the project is claimed and linked, Revdoku can update the existing site at the same address, so links you have already shared continue to work.

This is especially useful for feedback loops:

The agent creates and publishes version one.
A teammate or client reviews the URL.
You paste the feedback into the agent conversation.
The agent updates and republishes.
Everyone checks the same URL again.

What can you publish?

Revdoku can host AI-created:

websites and landing pages
documents and reports
dashboards and prototypes
spreadsheets
HTML files
PDF files
portfolios and résumés
product documentation and client previews

If your application needs a long-running backend, database, or private server process, keep that infrastructure on an appropriate application platform. Revdoku is best for browser-ready sites and shareable outputs.

Why the agent-first model matters

Traditional hosting is optimized for a person clicking through a dashboard. Agent-first hosting is optimized for a tool call inside a larger task.

That changes the request from:

“Build these files, then tell me how to deploy them.”

to:

“Build this, publish it, and give me the URL.”

The result is a shorter feedback loop and a deliverable that is immediately reviewable.

Try the workflow at revdoku.com. The first live preview is free and needs no account.

DEV Community: Revdoku Team