Headless site hosting concepts

These terms describe different parts of the same subject. What a host serves is different from how it is operated and from how an agent connects to it.

Static and dynamic describe what is served

Static hosting serves files exactly as stored: HTML, CSS, JavaScript, images, and fonts. A single-page app is static if it ships as files.

Dynamic hosting runs code on a server for each request. It suits sites that need a database, user accounts, or server-side rendering.

Most headless site hosts are static. An agent can produce a complete static site in one conversation.

Headless and agent-first describe operation

Headless site hosting lets an agent publish and manage a site through software interfaces, without routine dashboard use.

Agent-first hosting treats the agent as the primary operator when the host designs setup, errors, and pricing.

Headless describes access and operation. Agent-first describes which operator the experience prioritizes.

Git-based hosting deploys from a repository, usually after a build. It suits teams with a codebase and a review process.

A headless CMS manages content and delivers it through an API. It is not a host, although a site built from it needs one.

MCP, API, and CLI describe access

Model Context Protocol (MCP) is a standard for connecting AI applications with external data and tools. A host's MCP server exposes deploys as tools that an agent can call. MCP documentation

An application programming interface (API) lets software request data or actions in a defined format. Any agent that can make an HTTP request can use one.

A command-line interface (CLI) exposes commands through a terminal. It suits files that already exist on disk, and continuous integration.

These are access methods. The host defines which actions exist, what they cost, and what a given key may do.

Lifecycle terms

Deploy
A request that sends files to the host and makes them available at a URL.
Expiry or TTL
The time after which the host stops serving a site. TTL means time to live. Expiry keeps short-lived work from accumulating.
Pin
An instruction to keep a site until someone deletes it. Some hosts use other names for the same idea.
Custom domain
A domain that the person controls, attached to a site in place of the host's own address.
Scoped key
A credential limited to certain actions, such as deploying sites without the ability to make purchases.
Site-day
A billing unit for usage-based hosts: one site that exists for any part of one day.

One implementation

shipsite.sh is a static, agent-first host. It offers an API, an MCP server, and a CLI. Sites expire after 24 hours unless given a different TTL or pinned, and it bills per site-day.