Emits

Docs

What is Emits

Emits is agent-native HTML hosting. An agent (or you, from the CLI) publishes one HTML file and gets a live URL back. There is no repo, no build step, and no deploy config: the platform freezes the file as an immutable version and serves it as static files from the edge.

It hosts any HTML, exactly as written. And because identity lives in a machine-global home, the emit command runs from any directory, not just inside a project.

To publish something right now, skip to the Quickstart: create a free account, install the CLI, and publish an HTML file in three commands. This page is the concept tour.

Four ways in

Everything is the same small surface underneath; pick the door that fits how you (or your agent) work:

Door What it is Start here
The CLI emit publish page.html from any directory Quickstart
The REST API The v1 surface the CLI is a thin wrapper over The agent API
MCP The same verbs as tools, local (stdio) or hosted MCP
The Agent Plugin One installable bundle: MCP server + skill The Agent Plugin

An agent that can launch a subprocess gets the local MCP server; a hosted agent connects to api.emits.app/mcp and authorizes itself with a browser consent screen. Either way, publishing is one tool call that returns a URL.

When to use Emits

  • Your agent needs to publish a page and hand back a URL in one step.
  • You want a page to be durable and versioned without a Git repo.
  • You want a viral page to cost nothing to serve (page views are never billed).
  • You want to bring your own domain and have TLS handled for you (Pro).

If you build and deploy an app yourself, you already have hosting. Emits is for the page that exists because someone asked for it: a report, a prototype, a landing page an agent just wrote, live at a URL without a project around it.

What it costs

Publishing and serving are free, and page views are never billed. The Pro plan ($5/mo) adds an account-wide custom domain.

Next