What is headless site hosting?

Headless site hosting is web hosting that your agent can operate from start to finish, without a dashboard, a git repository, or a build pipeline.

The agent sends files through an API, MCP, or CLI and receives a live URL. It can update the site, set how long it stays up, attach a domain, and delete it through the same interface. You approve payment and decide what gets published.

Here, headless describes how the host is operated. It does not refer to a headless CMS or a headless browser.

An illustrative case

Fictional example

A bakery owner asks an agent for a holiday menu page that customers can open from a link.

Your agent

  • Writes the page and its stylesheet
  • Checks that the files are ready to serve
Sends one deploy request

Produces the finished files and publishes them itself.

Headless host

POST /sites

2 files, 14 KB

Returns a live URL in the response.

Stores the files and serves them over HTTPS.

Live site

https://holiday-menu.example

Holiday menu

Order by December 20 for pickup on the 23rd or 24th.

Set to expire on January 2

The owner shares the link. The agent can update or remove the page later.

A person still sets up payment once. The host serves the files as sent. It does not check that the menu is correct.

What changes when hosting becomes headless?

In dashboard-led hosting, a person creates a project, connects a repository, configures a build, and adds DNS records by hand.

In headless hosting, an agent performs those steps through a software interface, inside the conversation where the site was made.

The host still matters. It stores the files, serves them, issues certificates, enforces limits, and bills for use.

A dashboard can remain available for the same product. The test is whether routine work requires it.

Part of the workDashboard-led hostingHeadless hosting
Set upA person signs up, creates a project, and copies a token into their tools.The agent requests an account and a key. The person completes a payment or approval step.
PublishA person pushes to a repository and waits for a build.The agent sends ready-to-serve files and receives a URL.
UpdateA person commits a change or edits settings in the dashboard.The agent sends the changed files to the same site.
Add a domainA person adds the domain in the dashboard and edits DNS records.The agent attaches the domain and relays any DNS step that remains.
Clean upOld previews remain until a person removes them.The agent sets an expiry or deletes the site when the work ends.

Static hosting serves prepared files such as HTML, CSS, JavaScript, and images. It runs no server-side code.

Most headless site hosts are static hosts. Headless describes the operating model, and static describes what is served.

A headless CMS stores content and delivers it through an API to a separate front end. It manages content. It does not necessarily host the site.

Git-based hosting platforms also offer APIs and command-line tools. Many of them still assume a repository, a build step, and a dashboard for setup.

Agents often reach a headless host through the Model Context Protocol, a standard for connecting AI applications to tools. MCP documentation

What headless does not mean

A headless host does not need to remove its dashboard. It needs to support the intended agent tasks without one.

Headless does not mean that a person has no role. The person sets the goal, approves charges, and decides what becomes public.

It does not mean that the host builds the site. Many headless hosts accept only finished files.

It does not mean that the agent can spend without limits. A good implementation lets the person restrict what a key can do.

Publishing a site does not bring visitors to it. Hosting and discovery are separate work.

shipsite.sh and headless site hosting

shipsite.sh builds static hosting for agents first, with the agent as the primary operator.

An agent sends files as JSON in one request and receives a live HTTPS URL. No repository, build step, or dashboard is involved.

The same work is available through a REST API, an MCP server, and a CLI. Error messages state what went wrong and how to fix it, so that an agent can correct itself.

Sites expire after 24 hours unless the agent sets a different lifetime or pins them. Hosting costs $0.10 per site per day. There is no free tier, and a person completes a Stripe checkout before the first deploy.

An optional plan lets the agent attach a domain that you own, or register a new one at cost with DNS and HTTPS set up automatically.

This site is hosted on shipsite.sh. An agent deployed it and registered its domain through the API.

After publishing: headless AEO

Hosting makes a site available. It does not help buyers find the business behind it.

Headless AEO applies the same operating model to AI search. An agent works with visibility data and tools to help more buyers discover a business through AI-generated answers.

Frontmost AI builds for headless AEO. What is headless AEO? defines the term.

Further reading

How headless site hosting works explains the parts, their roles, and where the work can stop.

Related concepts separates what is served, how the host is operated, and how an agent connects.

Evaluation criteria gives tests that apply to any implementation.