ShipSite vs Netlify: deploying a static site through an API

Of the big hosts, Netlify comes closest to what ShipSite does: one request can create a site and publish it at a public URL. The differences are in the request format, who gets the credentials, and what each deploy costs.

Netlify details checked against Netlify's docs on November 16, 2026. Sources are listed at the bottom.

The short answer. Netlify is a full web platform with builds, functions, forms, deploy previews, and a free plan. If you are hosting a real project, or one site you will keep for months, Netlify is the stronger and usually cheaper choice. It also handles far larger sites than ShipSite does.

ShipSite is narrower. An agent sends files as JSON in one request and the response contains a public URL that already works. The agent can sign itself up, there is no per-deploy charge, and sites clean themselves up after 24 hours unless pinned. It costs $0.10 per site per day, with no free tier. It fits best when an agent produces many small sites or redeploys often.

At a glance

ShipSiteNetlify
Built for Agents publishing ready-to-serve static files Teams building and hosting web projects, with a growing set of tools for agents
Deploy call POST /v1/sites with a JSON files map. Text files are plain strings. POST /api/v1/sites with a ZIP file as the body creates a site and deploys it. Or a file digest: send a SHA1 for each file, then upload the files Netlify asks for, one request each.
When it is live When the response arrives. Nothing to poll. After post-processing. Poll the deploy until state is ready.
Is the URL public? Always. Yes, unless the team has turned on private-by-default projects.
Getting credentials The agent calls POST /v1/accounts and gets an API key and a Stripe checkout link. A person opens the link once to activate the key. A person creates a Netlify account and a personal access token in the dashboard and gives the token to the agent, or connects an agent through Netlify's MCP server.
Without an account Yes, for one trial site: POST /v1/sites with no key returns a live URL. It lasts 24 hours and holds up to 50 files and 5 MB, unless it is claimed into a paid account. Yes, for previews: netlify deploy --allow-anonymous in the CLI, or Netlify Drop in a browser. An anonymous CLI site is removed after one hour unless claimed.
Deploy limits 120 deploys per hour. 3 deploys per minute and 100 per day through the API.
Builds and server code None. Files are served exactly as sent. Builds, serverless functions, forms, and more. API deploys skip the build command.
MCP server Hosted at mcp.shipsite.sh/mcp, or @shipsite/mcp run locally. The hosted server takes an OAuth sign-in or an API key. Tools to deploy, update, pin, rename, and attach domains. Remote server at mcp.netlify.com/mcp, or @netlify/mcp run locally. Gives an agent the Netlify CLI.
How long sites live 24 hours by default. Pin a site to keep it until you delete it. Until you delete them. On the Free plan, every project is paused if the monthly credits run out.
Custom domains Optional plan: a flat $4.99 per billing period for up to 25 domains. With the plan, an agent can also buy a domain at cost and attach it in one call (POST /v1/domains). Included.
Price $0.10 per site per day, billed monthly. No free tier, no per-deploy or bandwidth charges. Credit-based. Free is $0 with 300 credits a month, Personal is $9 with 1,000, Pro is $20 with 3,000 and unlimited members. A production deploy uses 15 credits, bandwidth 20 per GB, and web requests 2 per 10,000.
Size limits 1,000 files and 100 MB per site, 10 MB per file, 1,000 active sites, 100,000 requests per site per day. 25,000 files per ZIP. Much more room than ShipSite.

The same deploy on each

One HTML file, deployed with curl. On ShipSite the files go in the JSON body:

ShipSite
curl -X POST https://api.shipsite.sh/v1/sites \
  -H "Authorization: Bearer $SHIPSITE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "files": {
      "index.html": "<html>Hello, world</html>"
    }
  }'

# Response: the URL is already serving
{
  "id": "site_a7x9k2mq",
  "url": "https://site_a7x9k2mq.shipsite.sh",
  "expires_at": "2026-11-17T12:00:00Z"
}

On Netlify, following its API guide, you zip the files first and send the archive as the request body:

Netlify
zip -r site.zip index.html

curl -X POST https://api.netlify.com/api/v1/sites \
  -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \
  -H "Content-Type: application/zip" \
  --data-binary "@site.zip"

# Response: a site object with its netlify.app URL.
# Poll the deploy until its state is "ready".

This is a good API, and for a script running in a shell there is little between the two. The gap is wider for a language model. A model writes JSON natively, but it cannot produce a ZIP archive or SHA1 hashes without a code-execution tool, so on Netlify the deploy depends on what else the agent has available.

Where the differences matter for an agent

Getting a key

With ShipSite the agent starts the signup itself. It calls POST /v1/accounts with an email, stores the API key from the response, and hands the user a Stripe checkout link. The key starts working when the user pays. Nobody opens a dashboard or pastes a token into a config file.

Netlify's API needs a personal access token that a person generates in the dashboard, under Applications. Netlify's own guide for coding agents notes that without the token, CLI commands fall back to an interactive login and hang, so the token has to be in place before the agent starts.

Deploying without an account

Netlify added anonymous CLI deploys in March 2026. Running netlify deploy --allow-anonymous publishes a folder with no account and returns a live URL, a site ID, and a token for claiming it. Netlify describes this as being for disposable previews: the site is removed after one hour unless a person claims it. It is the fastest route to a first URL on either service, as long as the agent can run the Netlify CLI.

ShipSite has an accountless mode too, in the REST API itself: POST /v1/sites with no key creates a trial site and returns its URL with a claim token. An unclaimed trial site lasts 24 hours instead of one, and holds up to 50 files and 5 MB. To keep it, the agent passes the claim token when it creates an account, and the site moves there once payment is set up.

Deploying often

Agents iterate. They deploy, look at the result, and deploy again. Netlify's API allows 3 deploys per minute and 100 per day, and on its credit-based plans each production deploy uses 15 credits. The Free plan's 300 credits cover 20 production deploys a month before anything else is counted, and when they are gone Netlify pauses all of the team's projects. Netlify's billing docs do not say separately how deploys made through the API are counted, so check your usage page if this matters to you.

ShipSite allows 120 deploys per hour and does not charge per deploy. Updating a site twenty times in an afternoon costs the same $0.10 as deploying it once.

What it costs

ShipSite charges $0.10 per site per day, prorated daily. One site for a month is about $3, ten sites for a month about $30, and a site that lives for two hours costs $0.10. There is no free tier. The first deploy can be a free trial site that lasts 24 hours; keeping a site, or deploying more, needs a card on file.

On Netlify, one site deployed a handful of times fits inside the Free plan and costs nothing, for as long as you keep it. Extra credits on Pro cost $10 per 1,500, which works out to about $0.10 per production deploy. So the two services charge the same dime for different things: Netlify for each deploy, ShipSite for each day a site exists. Long-lived sites that rarely change are cheaper on Netlify. Short-lived sites and frequent redeploys are cheaper on ShipSite.

Which one to pick

Choose Netlify if

  • You need a build step, serverless functions, or forms
  • You deploy from git and want deploy previews for pull requests
  • You are hosting one site for a long time and want it to be free or close to it
  • You need more than 1,000 files or 100 MB per site
  • Custom domains should be included in the price

Choose ShipSite if

  • An AI agent is doing the deploying, start to finish
  • The agent can send JSON but cannot build ZIP files or run a CLI
  • The agent redeploys often, or makes many sites a day
  • Sites are short-lived, and you want them cleaned up automatically
  • You want the agent to handle signup, with one checkout link for the person
  • You would rather pay per site than track credits

Questions people ask

Can Netlify deploy a static site from a single API call?

Yes. Sending a ZIP file to POST /api/v1/sites with a Netlify access token creates a site and deploys it in one request. You then poll the deploy until its state is ready. The other method, a file digest, takes several requests: you send a SHA1 hash for every file, Netlify answers with the ones it needs, and you upload each of those separately.

Does an AI agent need a Netlify account to deploy?

Not for a quick preview. The Netlify CLI can deploy with no account using netlify deploy --allow-anonymous, which returns a live URL. Netlify removes the site after one hour unless a person claims it into a Netlify account. The REST API needs an access token that a person creates in the Netlify dashboard.

Is ShipSite cheaper than Netlify?

It depends on the pattern. ShipSite charges $0.10 per site per day and nothing per deploy. Netlify's Free plan is $0 with 300 credits a month, and each production deploy uses 15 credits. A single site deployed a few times and kept for months costs less on Netlify, usually nothing. An agent that redeploys the same site dozens of times, or makes many sites that each live for a day or two, will usually spend less on ShipSite and will not run into Netlify's Free plan limit.

What happens when Netlify's Free plan runs out of credits?

Netlify's billing docs say the Free plan's 300 credits are a hard limit. Once the balance is used up, all of the team's projects are paused and visitors see a Site not available page. Paid plans can buy more credits. ShipSite has no free allowance to run out of, because every site is billed per day from the start.

Can I use both?

Yes. Keep the sites that need builds, functions, forms, or a git workflow on Netlify, and give your agent ShipSite for what it generates on the fly: reports, prototypes, previews, and one-off pages.

Try ShipSite

Point your agent at the LLM docs and ask it to deploy something. It will create the account, give you a checkout link, and come back with a URL.

Comparing other hosts? See ShipSite vs Vercel, Vercel vs Netlify for AI agents, and the alternatives to Netlify.

Sources

Netlify's platform changes often. Everything on this page about Netlify comes from these pages as they read on November 16, 2026. If something here is out of date, the Netlify docs are right and this page is wrong.

Netlify is a trademark of Netlify, Inc. shipsite.sh is not affiliated with or endorsed by Netlify.