ShipSite vs Vercel: deploying a static site through an API

Both can take a handful of files from an API call and give you back a live URL. They are built for different jobs, and the differences show up when the caller is an AI agent.

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

The short answer. Vercel is a full application platform: framework builds, serverless functions, git-based previews, and a free Hobby plan. If you are shipping an app, or a site you will keep for months, Vercel is the stronger and usually cheaper choice.

ShipSite does one thing: an agent sends finished files in one request and the response contains a public URL that already works. There are no projects, builds, or protection settings to get right, and the agent can sign itself up. It costs $0.10 per site per day, with no free tier. It fits best when an agent produces lots of small, short-lived sites.

At a glance

ShipSiteVercel
Built for Agents publishing ready-to-serve static files Teams building and hosting full web applications
Deploy call POST /v1/sites with a files map. Nothing else is required. POST /v13/deployments with a project name and a files array, plus projectSettings on a project's first deployment. Small files can be inlined; larger ones are uploaded first with POST /v2/files and referenced by SHA.
When it is live When the response arrives. No build, nothing to poll. The deployment is queued and built. Poll readyState until it is READY.
Is the URL public? Always. Depends on the project's Deployment Protection. Under Standard Protection, production domains are public; preview deployments and unique deployment URLs ask for a Vercel login. An API deployment is a preview unless you set target to production.
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 Vercel account and an access token and gives the token to the agent, or approves an OAuth connection to the Vercel 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 temporary deployments: vercel deploy --temporary in the CLI, or Vercel Drop in a browser. They expire unless claimed into an account.
Builds and server code None. Files are served exactly as sent. Framework detection, builds, serverless functions, and more.
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.vercel.com with OAuth. Has had a deploy_to_vercel tool since July 2026.
How long sites live 24 hours by default. Pin a site to keep it until you delete it. Until you remove them, subject to the project's retention settings. Temporary (accountless) deployments expire.
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. Up to 50 domains per project on Hobby, unlimited on Pro. Vercel sells domains too.
Price $0.10 per site per day, billed monthly. No free tier, no seats, no egress fees. Hobby is $0. Pro is $20 per month per developer seat and includes $20 of usage credit, with usage-based pricing beyond that.
Limits 1,000 files and 100 MB per site, 10 MB per file, 120 deploys per hour, 1,000 active sites, 100,000 requests per site per day. 100 deployments per day on Hobby and 6,000 on Pro. 200 projects on Hobby, unlimited on Pro. Hobby includes 1M CDN requests and 100 GB of transfer per month.

The same deploy on each

One HTML file, deployed with curl. On ShipSite the request is the files and nothing else:

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 Vercel, following its REST API reference, the request also names a project and says how to build it. Setting framework to null tells Vercel there is nothing to build, and target makes it a production deployment instead of a preview:

Vercel
curl -X POST https://api.vercel.com/v13/deployments \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "hello-site",
    "files": [
      { "file": "index.html", "data": "<html>Hello, world</html>" }
    ],
    "projectSettings": { "framework": null },
    "target": "production"
  }'

# Response: a deployment object. Poll it until readyState is READY,
# then use the production domain it was assigned.

That is a reasonable request, and Vercel's API gives you far more control than ShipSite's does. The cost is that an agent has to get more things right before a stranger can open the link.

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.

Vercel's REST API needs an access token that a person creates in their Vercel account. The Vercel MCP server avoids token handling with OAuth, which works well in the clients it supports. Vercel also now lets the CLI deploy with no account at all, which is the fastest way to a first URL on either service, with the limits described next.

Deploying without an account

Running vercel deploy --temporary with no credentials creates a temporary production deployment and prints a claim link. The deployment expires after a period Vercel sets unless someone opens the claim link, logs in or signs up, and moves the project into their account. Vercel's docs note that this path is not available in CI environments, and the browser version (Vercel Drop) is for people, not API callers.

ShipSite has an accountless mode as well, and it is part of the REST API: POST /v1/sites with no key creates a trial site and returns its URL with a claim token. The site lasts 24 hours 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 to that account once payment is set up. Every other site belongs to a paid account from the start, and keeping one is a single POST /v1/sites/:id/pin call.

Whether the link opens for other people

This is the difference that most often surprises people who deploy to Vercel from a script. New Vercel projects have had Deployment Protection turned on by default since November 2023. Under the Standard Protection setting, the production domain is public, but preview deployments and the unique per-deployment URLs send visitors to a Vercel login. An agent that deploys without "target": "production", or that shares the wrong one of a deployment's several URLs, hands the user a link that only works for them.

Protection is a useful feature and you can change it per project or through the API. ShipSite simply does not have the concept: a site has one URL, plus its custom domains, and they are public.

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.

Vercel's Hobby plan is free, and Pro is $20 per month per developer seat with $20 of included usage. A single long-lived static site costs less on Vercel, often nothing. ShipSite is the cheaper and simpler option only when sites are numerous and short-lived, or when you would rather pay per site than manage a plan, seats, and usage allotments.

Which one to pick

Choose Vercel if

  • You need a build step, a framework such as Next.js, or server-side code
  • You deploy from git and want preview deployments for pull requests
  • You are hosting one site for a long time and want it to be free or close to it
  • You want password or login protection on deployments
  • 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 output is already static files: reports, prototypes, demos, generated pages
  • Every URL has to work for anyone the moment it is returned
  • 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 per seat

Questions people ask

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

Yes. POST /v13/deployments accepts small files inlined in the request body, so one authenticated call can create a deployment. You also send a project name and, on a project's first deployment, projectSettings. The deployment then builds, so you poll readyState until it is READY. Larger files are uploaded first with POST /v2/files and referenced by SHA.

Does an AI agent need a Vercel account to deploy?

Not always. Vercel's CLI can deploy without credentials using vercel deploy --temporary, and Vercel Drop does the same in a browser. Both create a temporary deployment that expires unless someone claims it into a Vercel account. Vercel's docs say the CLI path is not available in CI environments. The REST API and the Vercel MCP server both need an account.

Is ShipSite cheaper than Vercel?

It depends on how long the site lives. ShipSite has no free tier and charges $0.10 per site per day, so a site kept for a month costs about $3. Vercel's Hobby plan is $0 and Pro is $20 per month per developer seat. For a site you keep for months, Vercel usually costs less. For sites that live for hours or days, ShipSite costs cents and needs no plan.

Will the URL work for someone who is not logged in?

On ShipSite, always: every site URL is public as soon as the deploy call returns. On Vercel it depends on the project's Deployment Protection settings. Under Standard Protection, production domains are public, while preview deployments and unique deployment URLs ask visitors to log in to Vercel. An API deployment is a preview unless you set target to production.

Can I use both?

Yes, and many teams should. Keep the app that needs builds, functions, or a git workflow on Vercel, and give your agent ShipSite for the things 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 Netlify and Vercel vs Netlify for AI agents.

Sources

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

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