Agent-native site builder · no UI included

Say the site. Watch it ship.

Zero-UI has no editor, no canvas and no drag-and-drop. An AI agent writes the code, Zero-UI versions it, tests it in an isolated browser and publishes it to Cloudflare's edge.

0buttons to learn
31MCP tools
1sentence in
∞sites out
Scroll to the build bay

001 / Build bay

Type a sentence. Get a website.

Describe the site you want. The agent drafts it, Zero-UI checks it in an isolated browser and publishes it to a real address you can open.

ZERO-UI · EDGE DISPLAY
Awaiting intent
Describe a site in the terminal →
Phase idleElapsed 00.0sRevision —
zero-ui — agent session REPLAY
0 / 600

002 / Pipeline

The interface is the agent.

Zero-UI exposes typed tools over the Model Context Protocol (MCP). Any capable agent can drive them. The page above runs exactly these steps.

  1. 001 / Intent

    One sentence in

    You describe the site in plain language. The model plans the structure, copy and interactions with no template picker.

    "build me a website that has…"
  2. 002 / Author

    Revision-checked source

    Every write is an atomic batch against an exact revision and file hash. No silent overwrites, and the full history is kept.

    apply_changes(expected_revision)
  3. 003 / Inspect

    An isolated browser looks first

    Generated code never runs on a host machine. A network-isolated Chromium renders it at desktop and mobile sizes and runs the declared checks.

    inspect_preview(steps, viewports)
  4. 004 / Publish

    Straight to the edge

    Release validation, Cloudflare Workers Static Assets hosting, a custom domain and live hash verification run as one durable call.

    publish_revision → get_publication
  5. 005 / Iterate

    Edit by asking

    Ask for a change. The same project, destination and URL are updated, and earlier revisions stay available for rollback.

    rollback_deployment(target)

003 / Ledger

From sentence to live URL.

0s

Wall-clock time for the recorded build: the model writing the site through OpenRouter, then Zero-UI checking it and verifying live hashes on the public domain.

Build receipt#—


Total—
Model tokens (est.)—
Model cost (est.)—

Measured on 2026-11-06. Tokens and cost are what OpenRouter billed for this build; tool times are the measured Zero-UI MCP calls.

004 / Vibes

Dark mode, loud color.

Five palette directions for the showcase. Pick one and the whole page re-themes, including a hue shift on the generated hero image.

005 / Engine

A whole website for a quarter of a cent.

The recorded builds were written by GPT-6 Luna through OpenRouter, with Claude Haiku 5.5 and GLM 5.3 as fallbacks when a provider is busy. The hero art was made by a local FLUX model on Zero-UI's own GPU helper.

—

Per-build costs are what OpenRouter billed for test builds on 2026-11-06 using the Zero-UI system prompt (about 450–750 input and 4,000–8,000 output tokens). Six models were compared and all six outputs passed Zero-UI release validation. Prices change; the calculator uses the primary model's measured average.

006 / Signal

No UI.
All signal.

The builder is an API your agent already knows how to use. Connect Codex, Cursor or Claude Code to the Zero-UI MCP endpoint and start shipping.