Vercel Domains

Vercel Domains — Buy a domain with the token that runs your deploys — narrow list, high prices. Vercel exposes buy, price and status endpoints for domains inside its main REST API, authenticated with the same bearer token as everything else, and wires the result straight into project configuration and DNS. For a product whose onboarding ends in a live site on a custom domain, that integration is worth real money. The buyable TLD list is short, there is no sandbox, and prices sit above the retail market. Built by Vercel Inc.. Founded 2015. Series F.

We track it in 1 comparison — Domain APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 14 other tools, and what follows is where it visibly separates from them.

Where it wins.

• API auth — bearer-token, tied for best across 2 of 15 tools.
• Privacy via API — free-and-default, tied for best across 5 of 15 tools.
• Machine-readable spec — Yes, which only 3 of 15 tools here manage.
• MCP server — Yes, and it is the only one of 15 here that manages it.
• API since — 2018, 2nd of 15.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Sandbox / OTE — No. Namecheap records Yes.
• .au support — No. OpenSRS records Yes.
• EPP code via API — No. Name.com records Yes.
• Pricing basis — retail-premium, 14th of 15. Hexonet records wholesale.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 25 of 26 tracked fields carry a value for Vercel Domains, and 5 of those cite a document you can open. Last verified 2026-07-23. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Direct EPP (own accreditation). Vercel Domains is ahead on Spend to first call ($0 up front against $7,500 up front) and DNS record API (Yes against No). Direct EPP (own accreditation) takes Sandbox / OTE (Yes against No) and .au support (Yes against No). That pattern repeats across the rest of the roster — see Vercel Domains alternatives for the other rivals, each compared the same way.

Company

Vercel Inc.

Founded

2015

Funding

Series F

Fields we track

25 of 26

Last verified

2026-07-23

Buying a domain in the same request flow that configures the project is a real product advantage, and the MCP server makes it the easiest option for an agent to drive. It is also the narrowest catalogue, the least portable registrant model, and priced accordingly.

Sandbox / OTE

○No10th of 14

Inferred

.au support

○No9th of 12

Inferred

EPP code via API

○No12th of 15

Inferred

Pricing basis

retail-premium14th of 15

Inferred

Bulk availability

○No13th of 15

Inferred

Contact model

account-default14th of 15

Inferred

TLDs offered

50 TLDs14th of 14

Inferred

API auth

bearer-token1st of 15

Vendor-claimedverified 2026-07-23source

Vercel Domains is the right call in these situations, each one drawn from a field we actually record:

• Onboarding flows that end with a live site on a custom domain.
• Agent-driven workflows already holding a Vercel token.
• Teams that value one bill over per-name price.
• API auth is your binding constraint. Vercel Domains records bearer-token, the best figure in the Domain APIs roster. We define that field as how the API authenticates callers, ranked by how well it survives ephemeral infrastructure.
• Privacy via API is your binding constraint. Vercel Domains records free-and-default, the best figure in the Domain APIs roster. We define that field as whether WHOIS/RDAP privacy can be controlled from the API and what it costs at your tier.
• Machine-readable spec is your binding constraint. Vercel Domains records Yes, which only 3 of the 15 tools in the Domain APIs roster do.
• MCP server is your binding constraint. Vercel Domains records Yes, which only 1 of the 15 tools in the Domain APIs roster do.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Sandbox / OTE. Vercel Domains records No on the Domain APIs table. Namecheap records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• .au support. Vercel Domains records No on the Domain APIs table. OpenSRS records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• EPP code via API. Vercel Domains records No on the Domain APIs table. Name.com records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Pricing basis. Vercel Domains records retail-premium, 14th of 15 in the Domain APIs roster. Hexonet records wholesale on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Bulk availability. Vercel Domains records No on the Domain APIs table. Namecheap records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 1 of the 26 fields we track for Vercel Domains are still blank: Rate limit. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.