Revdoku website publishing API

Create websites from your AI for FREE

Ask ChatGPT, Claude or other AI to publish to Revdoku.

Get a live *.localhost3000.love website in seconds.

Free account available.

Use Revdoku to turn generated files into a live static website, update the same URL, and connect compatible AI clients through hosted MCP.

Choose the right publishing path

  • Local client: sign in through the browser, save a private draft, and create a temporary 15-minute preview before publishing.
  • Free account: create one in the web UI; read current limits from the versioned pricing contract.
  • Hosted MCP: connect a compatible AI client to https://app.revdoku.com/mcp with OAuth.
  • API integration: use the HTTP API when you are building a custom service or automation.

For client-specific commands, OAuth setup, and local-file limitations, use the MCP website-publishing guide.

Quick local publish

From a static site’s output folder:

revdoku p .

Without credentials, the client opens browser sign-in. After authentication, publishing the same bound folder again updates the same URL.

Hosted MCP endpoint

Use this Streamable HTTP endpoint:

https://app.revdoku.com/mcp

OAuth-capable clients can discover Revdoku’s website and file tools after authorization. Remote MCP works best with text-based files. Use the local client when a project includes local images, fonts, archives, PDFs, or other binary assets that the remote server cannot read from your computer.

HTTP API reference

The complete machine-readable and human-readable API documentation is available at revdoku.com/api.md. It covers authentication, buckets, files, publishing, versions, access settings, and responses.

When building an integration:

  • Keep credentials out of prompts, logs, repositories, and published files.
  • Reuse the same bucket or local project binding for later updates.
  • Confirm the returned website ID and URL before saving them.
  • Treat Revdoku as static hosting; run any framework build before uploading its output.
  • Start with a small test site, then update one file and verify the original URL changes.

Minimal end-to-end test

  1. Create a folder with index.html.
  2. Publish it and save the returned website URL.
  3. Change the heading in index.html.
  4. Publish the same folder or update the same bucket.
  5. Reload the saved URL and verify the new heading appears.

That test confirms file upload, publishing, identity reuse, and same-URL updates without adding application-specific complexity.

Markdown version
↧
Loading PDF…