Vercel vs Netlify for AI agents deploying a static site through an API

Through the REST API alone, Netlify is the easier of the two for an AI coding agent. One request with a ZIP file as the body creates a site and deploys it, with no project settings in the request. Vercel can do it in one request too, but the agent has more to get right before a stranger can open the link.

We make ShipSite, the third column on this page. Details about Vercel and Netlify were checked against their own docs on November 19, 2026. Sources are listed at the bottom.

The short answer. Netlify's API takes a ZIP file in a single POST /api/v1/sites request and returns a site. Vercel's POST /v13/deployments takes small files inlined as JSON, but it also needs a project name, projectSettings on a project's first deployment, and "target": "production". Without that last field the deployment is a preview, and under Vercel's Standard Protection a preview URL asks visitors to log in. On both, the agent polls until the deploy is ready.

From a terminal, the two are close: each has a CLI command that deploys with no account and prints a live URL. Vercel allows far more deployments a day on its paid plan, and Netlify's API is capped at 100 deploys a day.

ShipSite is a narrower third option. An agent sends files as JSON in one request and the response contains a public URL that already works. ShipSite has no builds, no server code, and no free tier.

At a glance

NetlifyVercelShipSite
Requests to a live URL One POST /api/v1/sites with a ZIP body, then poll the deploy until state is ready. With a file digest: one request with a SHA1 for each file, one upload for each file Netlify asks for, then poll. One POST /v13/deployments when files are small enough to inline, then poll readyState until it is READY. Other files are uploaded first, one POST /v2/files each, and referenced by SHA. One POST /v1/sites. The URL in the response is already serving. Nothing to poll.
Upload format A ZIP file as the request body (Content-Type: application/zip), or a file digest. JSON. A files array with inlined data (base64 is an allowed encoding), or files uploaded beforehand. JSON. A files map of path to content. Text files are plain strings; binary files are base64.
What else the request needs Nothing for a new site. A project name. projectSettings on the first deployment of a project. "target": "production", or the deployment is a preview. Nothing.
Credentials an agent needs A personal access token that a person creates in Netlify, sent as a bearer token. Public integrations must use OAuth2. An access token from a Vercel account, sent as a bearer token. An API key. The agent gets it from POST /v1/accounts, with a Stripe checkout link that a person opens once to activate the key.
Without an account CLI only: netlify deploy --allow-anonymous. An unclaimed project is removed after one hour. CLI only: vercel deploy --temporary. It expires after a period Vercel sets and the CLI prints. Not available in CI environments. Yes, through the API: POST /v1/sites with no key creates one trial site. It lasts 24 hours and holds up to 50 files and 5 MB.
MCP server Remote server at mcp.netlify.com/mcp, or @netlify/mcp run locally. It gives an agent the Netlify CLI. Remote server at mcp.vercel.com with OAuth. It has a deploy_to_vercel tool. Hosted at mcp.shipsite.sh/mcp, or @shipsite/mcp run locally. The hosted server takes an OAuth sign-in or an API key.
Deploy limits 3 deploys per minute and 100 per day through the API. 25,000 files per ZIP extraction. 100 deployments per day on Hobby, 6,000 on Pro. 120 deploys per hour. 1,000 files and 100 MB per site, 10 MB per file.
Builds and server code Yes. A deploy created by hand, without continuous deployment, does not run a build command. Yes. An API deployment is queued and built. None. Files are served exactly as sent.
Entry price Free is $0 with 300 credits a month. A production deploy uses 15 credits. Personal is $9 a month with 1,000 credits. Hobby is $0. Pro is $20 a month with $20 of included usage credit. $0.10 per site per day, billed monthly. No free tier.

The same deploy on each

One HTML file, deployed with curl, following each company's API reference.

On Netlify, the agent first puts the files in a ZIP, then sends the ZIP as the body. No JSON and no settings:

Netlify
zip -r website.zip index.html

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

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

On Vercel, the files go inline as JSON, and the request also names a project and says how to build it. Setting framework to null selects no framework, 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.

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-20T12:00:00Z"
}

Where Vercel and Netlify differ for an agent

Getting the files there

Netlify's API accepts a whole site as one ZIP file. That is one request, but the agent must be able to build a ZIP and send binary data, which an agent with a shell can do and an agent limited to JSON tool calls often cannot. Netlify's other method, the file digest, sends a SHA1 for each file, and Netlify answers with the list of files to upload, one PUT request each.

Vercel's API accepts small files inlined in the JSON body of POST /v13/deployments, so an agent that can only send JSON can deploy a small site in one request. Other files are uploaded first with POST /v2/files, one request per file with the file's SHA1 in a header, and then referenced by SHA.

ShipSite's API accepts a JSON map of file paths to file contents in one request, up to 1,000 files and 100 MB per site. There is no ZIP and no hashing.

What the agent has to get right

A Netlify ZIP deploy to POST /api/v1/sites needs a token and a ZIP. Netlify's docs describe creating a site with a ZIP "straight away, to save an HTTP request".

A Vercel deployment needs a project name, and Vercel's reference says projectSettings "is required for the first deployment of a project". If target is omitted, the reference says "the target will be preview". An agent that omits target gets a preview deployment, not a production one.

A ShipSite deploy needs an API key and a files map.

Whether the link opens for other people

On Vercel this depends on the project's Deployment Protection. Vercel's docs call Standard Protection the recommended option and say it "protects all domains except production domains". Vercel turned Deployment Protection on by default for new projects in November 2023. So a preview deployment, or the unique URL of a single deployment, can ask a visitor to log in to Vercel. An agent has to deploy to production and hand over the production domain.

On Netlify, a project claimed from an anonymous deploy follows the team's default project visibility, according to Netlify's docs.

On ShipSite, every site URL is public as soon as the deploy call returns, unless the request set a password.

Knowing when it is live

Neither Vercel nor Netlify returns a URL that is live when the response arrives. A Netlify ZIP deploy "will enter post-processing mode straight after being created", and the docs say "once the state changes to ready, the deploy is live". A Vercel deployment moves through QUEUED, INITIALIZING and BUILDING before it reaches READY or ERROR. Either way the agent needs a polling loop and a decision about what to do when the deploy fails.

ShipSite does not build or post-process, so the URL in the response is serving when the response arrives.

Deploying with no account

Both companies now let a CLI deploy with no credentials, and both describe it as useful for AI agents. Netlify's netlify deploy --allow-anonymous creates a project with a live URL, and a person has one hour to claim it by logging in or creating an account. After one hour, an unclaimed project is removed. Vercel's vercel deploy --temporary deploys to production and prints a claim URL and how long the deployment has left. Vercel sets that period on its servers, and its docs say the command is not available in CI environments or in a directory already linked to a Vercel project.

Both paths need a terminal. Neither company's REST API has an accountless mode. ShipSite's REST API does: POST /v1/sites with no key creates one trial site that lasts 24 hours and holds up to 50 files and 5 MB. Every other site belongs to a paid account, which the agent can create through the API.

Deploying often

Agents 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 successful production deploy uses 15 credits. The Free plan's 300 credits are a hard limit, and when they are used up Netlify pauses all of the team's projects. Netlify's billing docs do not say separately how deploys made through the API are counted.

Vercel allows 100 deployments per day on Hobby and 6,000 on Pro.

ShipSite allows 120 deploys per hour and does not charge per deploy.

What it costs

Netlify's Free plan is $0 with 300 credits a month, Personal is $9 with 1,000, and Pro is $20 with 3,000. Vercel's Hobby plan is $0, and Pro is $20 a month with $20 of included usage credit. A single static site deployed a few times fits inside the free plan of either one.

ShipSite charges $0.10 per site per day, prorated daily. One site for a month is about $3. There is no free tier, so a long-lived site costs more on ShipSite than on Vercel or Netlify.

Which one to pick

Choose Netlify if

  • The agent can build a ZIP and you want one API request with no settings
  • You want a throwaway preview from the CLI with no signup
  • You also need forms, functions, or deploy previews from git
  • The agent deploys fewer than 100 times a day

Choose Vercel if

  • The agent can only send JSON and the files are small enough to inline
  • The project uses a framework such as Next.js, or needs server-side code
  • The agent deploys many times a day and you are on Pro
  • You want login or password protection on deployments

Choose ShipSite if

  • The files are finished and need no build
  • The agent can send JSON but cannot build ZIP files or run a CLI
  • You want the URL in the response to work at once, with nothing to poll
  • Sites are short-lived, and you want them cleaned up after 24 hours unless pinned

Do not choose ShipSite if

  • You need a build step, functions, or forms
  • You need a free plan
  • You need more than 1,000 files or 100 MB per site
  • You are hosting one site for months and want the lowest price

Questions people ask

Which is easier for an AI coding agent to deploy a static site through an API: Vercel or Netlify?

Through the REST API alone, Netlify takes less to get right. One request with a ZIP file as the body creates a site and deploys it, and the request carries no project settings. Vercel can also deploy in one request when the files are small enough to inline, but the request must name a project, send projectSettings on the project's first deployment, and set target to production, or the result is a preview deployment. On both, the agent then polls until the deploy is ready.

Can Vercel or Netlify return a live URL from a single API call?

Each can create a deployment in one authenticated call, but neither URL is live when the response arrives. Netlify's ZIP deploy goes into post-processing, and the deploy is live when its state is ready. Vercel's deployment is queued and built, and it is done when readyState is READY. On ShipSite, POST /v1/sites returns a URL that is already serving.

Can an AI agent deploy to Vercel or Netlify without an account?

Yes, from a terminal, on both. Netlify's CLI has netlify deploy --allow-anonymous, and an unclaimed project is removed after one hour. Vercel's CLI has vercel deploy --temporary, and the deployment expires after a period that Vercel sets and the CLI prints. Vercel's docs say that path is not available in CI environments. Neither company's REST API has an accountless mode: both need a token that a person creates.

How many deploys a day do Vercel and Netlify allow?

Netlify's API allows 3 deploys per minute and 100 per day. Vercel allows 100 deployments per day on Hobby and 6,000 on Pro. ShipSite allows 120 deploys per hour.

Where does ShipSite fit next to Vercel and Netlify?

ShipSite does only the part this page compares. An agent sends files as JSON to POST /v1/sites and the response contains a public URL that already works. There is no ZIP, no file hashing, no project settings, and nothing to poll, and the agent can create the account itself. It costs $0.10 per site per day with no free tier, and it has no builds or server code, so Vercel and Netlify are the better choice for an app or for a site you keep for months.

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.

Want the two-way comparisons? See ShipSite vs Vercel, ShipSite vs Netlify, and the alternatives to Netlify.

Sources

Vercel and Netlify change often. Everything on this page about them comes from these pages as they read on November 19, 2026. If something here is out of date, their docs are right and this page is wrong.

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