A place to publish the files AI generates — HTML sites, PDFs, markdown, CSV, images, video — as clean, access-controlled links like acme-proposal.quickhost.ing, with per-recipient open tracking and client comments your agent can read and act on.

How do I share a Claude artifact or a ChatGPT page with a client?

Download it as a file and drag it onto the dashboard, or let your agent publish it directly over MCP. Either way it is live on its own subdomain in seconds, gated however you choose, and your client needs no account to open it.

What file types can I publish?

Multi-file HTML sites as a zip or a folder, single HTML files, PDFs, markdown, plain text, CSV, TSV, JSON, images, and video. Each one gets a viewer built for it, and sites are served exactly as uploaded.

Can I password-protect a link, or make it expire?

Yes, on every plan. A project can be public, password-protected with a doorcode you can read back and re-send, or private behind named signed links you revoke individually. Any project can carry an expiry date.

How do I know if the client opened it?

Give each recipient their own named link. The dashboard then shows opens per person — count, first opened, last opened — and an email arrives the first time each link is opened.

Can clients comment without creating an account?

Yes. They highlight text, drop a pin, or mark a PDF page or a video timestamp, add a name, and comment. No sign-up. You see the thread in the dashboard and your agent sees it over MCP or qh comments --json.

Can my AI agent use this without me?

That is the intended shape. There is an MCP server with 17 tools, a CLI with --json on every command, a REST API with stable machine-readable error codes, and agent documentation at /mcp.md (how to connect Claude Code, Codex, Gemini CLI, Cursor and VS Code), /llms.txt, /docs.md and /.well-known/agent.md.

Does it run backend code or build my project?

No. Static files only, served exactly as uploaded — no functions, no build pipeline. That is deliberate: nothing compiles, so nothing can break after you have sent the link.

Is there a free plan?

No, and there will not be. Plans start at $8 a month with a 7-day trial of Studio. That is why there are no upsell banners on your deliverables, no branding badge on your client’s page, and no link that dies because you forgot to log in. Access is invite-only while billing is being finished.

Are viewers tracked with cookies or scripts?

No. Engagement is measured from server access logs: no analytics script is added to your work, no cookies are set on viewers, and unique-visitor counts use salted hashes that rotate daily. Every project is noindex by default.

Docs

Drive QuickHost without opening it

Everything the app does is reachable three other ways — an MCP server your agent connects to, a qh command in your terminal, and a REST API for your own code. They are the same operations behind the same account, so you can publish from one and manage from another.

Start here

Which way in do I want?

It follows from what is doing the work, not from which is most capable — all three can publish, gate a link and read comments back.

If an agent is doing the work

MCP server

Connect Claude, ChatGPT, Cursor or Codex once, and it can publish, gate a link and read the comments back without you opening a browser.

Set it up →

If you are writing the code

REST API

Interactive reference, generated from the running service — so it cannot describe an endpoint that no longer exists.

Open reference ↗

If you live in a terminal

qh CLI

One command to publish a folder, --json on everything, and real exit codes. Quickstart is in the API reference file until it has a page of its own.

Open reference ↗

Reference

Where is the full API reference?

At https://api.quickhost.ing/docs, generated from the running service rather than maintained alongside it — so it cannot document an endpoint that no longer exists. /redoc is the same content laid out for reading, and /openapi.json is the schema, if you would rather generate a client than write one.

Authentication

A token from Settings → API tokens, sent as Authorization: Bearer qh_…. The CLI uses a device flow instead, so a token never has to be pasted into a shell history.

Errors are a fixed shape

Every failure is {"error": {"code", "message", "field"}}. Branch on code — it is a stable string like slug_taken or quota_exceeded, not prose that may be reworded.

For agents

What is published for machines to read?

Four plain-text files, all reachable without a login, JavaScript or a rendered page. An agent pointed at any one of them can find the rest.

/mcp.md: Per-client connection instructions
/llms.txt: What QuickHost is, for a model reading about it
/docs.md: The full API surface in one file
/.well-known/agent.md: Discovery entry point