AI-agent-first HTML deploys

Upload HTML. Keep it private.

Deploy a self-contained artifact, keep it off the public web, then hand access to a human reviewer or another agent when you mean to.

~/artifact

CLI AI agent

$ uphtml some-html-plan.html
Deployed.
URL: https://r7kq4.upload-html.com
Slug: some-html-plan

$ uphtml share --slug some-html-plan
Share URL: https://r7kq4.upload-html.com
Token: shown once, stored by hash

Use uphtml CLI for private static HTML previews.

Deploy:
npx uphtml <file.html> --json

Share:
npx uphtml share --slug <slug> --json
npx uphtml share --slug <slug> --kind agent --json
npx uphtml share --slug <slug> --link-type jwt --json

Return the protected URL and keep the token secret.

Deploy path

One command owns the boring parts.

uphtml is built for the moment after an agent writes an HTML file: resolve the target, upload it, return a protected URL, and show the next share command.

Generate a CLI code

Deploy the artifact

Point the CLI at one HTML file. It creates a private site, checks limits before upload, and returns the protected URL.

Share intentionally

Create a human magic link or an agent bearer token. Shares are scoped, time-boxed, revocable, and shown once.

Privacy contract

Private is the default shape, not a checkbox.

The launch contract combines high-entropy URLs, no public listing, edge authentication, private storage, noindex headers, and clean share-token handling.

No directory. No sitemap, gallery, trending page, or first-party discovery surface.
Credential-aware edge. Owner JWTs, human magic links, and agent tokens fail closed.
Secrets shown once. API keys, setup codes, and share tokens are persisted as hashes.
Honest caveat. Owner HTML and recipients can still leak content outside the platform.

Start from the dashboard

Login, generate a setup code, then let the CLI deploy.

Open app.upload-html.com