Why Agents? - SimpleHost

The problem

AI agents are getting better at building things. Claude writes a full React app. Cursor generates a landing page. Copilot scaffolds a dashboard. But then what? The agent builds it. You review it. And then you spend 20 minutes setting up hosting, configuring deploys, pushing to a repo, waiting for CI. The agent did the hard part. Hosting shouldn’t be harder.

The solution

SimpleHost gives agents a single capability: publish anything to the web instantly.

You: "Build me a landing page for my product"

Agent: [builds the page]
       "Done! Here's the live URL: https://cool-page-x9f3.simplehost.dev/"

No deploy scripts. No CI pipeline. No hosting config. The agent handles everything end-to-end.

How agents use SimpleHost

Discovery

Agents find SimpleHost automatically through standard protocols:

Protocol	URL	Purpose
llms.txt	simplehost.dev/llms.txt	AI-readable docs index
OpenAPI	simplehost.dev/openapi.json	Machine-readable API spec
Agent Skill	`npx skills add sk-code-01/simplehost-skill -g`	One-command install

Publishing

The agent uses a simple 3-call flow:

POST /api/v1/publish     → Create site, get upload URLs
PUT  <presigned-url>      → Upload each file (parallel)
POST /finalize            → Make it live

Or even simpler — the agent downloads publish.sh and runs it:

curl -fsSL https://simplehost.dev/publish.sh -o /tmp/simplehost-publish.sh
bash /tmp/simplehost-publish.sh ./dist

Updating

When the agent updates a site, SimpleHost compares file hashes and only uploads what changed. A 500-file site where 3 files changed? Only 3 uploads. The agent handles this automatically.

What makes SimpleHost agent-native

Feature	Why it matters for agents
No config files	Agents don’t need to generate netlify.toml, vercel.json, or any config
No git required	Agents can publish directly from any directory — no repo needed
No accounts required	Anonymous publishing works instantly (24-hour expiry)
Presigned uploads	Files go directly to storage — no streaming through a server
Hash dedup	Agents skip unchanged files automatically
JSON errors with fix hints	When something fails, the API tells the agent exactly how to fix it
Rate limit headers	Agents know exactly when to retry
Deterministic slugs	Same API shape every time — agents can rely on consistent responses

The agent workflow

This is the typical flow when a developer uses an AI agent with SimpleHost:

Developer gives a prompt

“Build me a dashboard for my sales data” or “Create a portfolio site” or “Make a documentation page for this API”

Agent builds it

The agent writes HTML, CSS, JS — whatever is needed. This is what agents are already great at.

Agent publishes it

The agent calls SimpleHost’s API (via the installed skill or directly). Files are uploaded, site goes live.

Developer gets a URL

https://sales-dash-k8m2.simplehost.dev/ — live, shareable, ready to use. The whole thing took 2 minutes.

Supported agents

The SimpleHost skill follows the open Agent Skills standard:

Claude Code — Full support
Cursor — Full support
Windsurf — Full support
GitHub Copilot — Via OpenAPI spec
Custom agents — Via REST API or OpenAPI spec

Any agent that can make HTTP requests can use SimpleHost.

​The problem

​The solution

​How agents use SimpleHost

​Discovery

​Publishing

​Updating

​What makes SimpleHost agent-native

​The agent workflow

​Supported agents