02 · Stay in control
It is your page after it is live. Change it, hide it, find it, name it.
Send a new version to the same link. Nothing you published is ever overwritten.
- The link you gave out never changes
- Every earlier version is kept, never overwritten
- A retry never creates a duplicate
or
emit update pg_abc123 ./index.htmlhandbook.emits.page
12 pages · 3 versions
v3Live nowv2Kept · 6 days agov1Kept · 3 weeks ago
You decide who gets in. Change your mind without republishing.
handbook.emits.pageAnyone can open it, and it can be found
or
emit visibility pg_abc123 publicTag them now, find them in a second.
5 pages match
LinkTagsVersion
- handbook.emits.pageclientq3v3
- launch-notes.emits.pagelaunchv2
- q3-teardown.emits.pageq3clientv1
- pricing-draft.emits.pagedraftv5
- changelog.emits.pagelaunchv9
or
emit find --tag launch --q handbookAdd your domain once. Everything you host answers there.
- One domain for the whole account, not one per page
- Every page also serves at your-domain/name
- HTTPS is set up for you
or
emit bind-domain pages.mzed.studiopages.mzed.studio
Active
pages.mzed.studio/handbook
pages.mzed.studio/changelog
pages.mzed.studio/q3-teardown
03 · Hand it to your agent
Your agent learns it in one command. Then it ships pages on its own.
Publish straight from the model. No file, no shell, no setup.
An MCP agent gets four tools: publish, update, list and unpublish. Publish takes the HTML itself, so a page the model just wrote goes live without touching a disk.
mcpremote, local, or a plugin
https://api.emits.app/mcp
# nothing to install: paste it into any MCP client, approve once in the browser
# local: emit mcp
# Claude Code: claude plugin install emits@mzedGot a shell? Use the CLI. Point it at a file and go.
No HTML to paste anywhere: the login already lives on the machine, and a whole folder publishes with one flag.
terminalone file, or a whole folder
emit publish ./index.html --tag draft --visibility unlisted
→
or teach it
emit skill --out SKILL.mdNo shell? Five verbs. That is the whole API.
Anything that can make a web request can publish. Hosted agents, tool calls and browser agents all use the same five.
- publishSend HTML, get the link backPOST /v1/pages
- updateNew version, same linkPATCH /v1/pages/{id}
- findSearch and filter by tagGET /v1/pages
- visibilityPublic, unlisted or privatePATCH /v1/pages/{id}/visibility
- deleteThe link goes dark, nothing erasedDELETE /v1/pages/{id}
A failed call is safe to send again. A retry never publishes twice.
You stay in control
- Reading pages and writing them are separate permissions
- Pointing a domain at pages always asks a human first
- Any connected agent can be revoked in one click
- The activity feed records what changed, and who changed it