Skip to main content
skill CX Codex

domains — Claude Code skill for Vercel domains

The domains Claude Code skill searches domain names and manages them through Vercel tools. It activates for availability checks, DNS changes, transfers, and renewals.

Apache-2.0 143 installs ★ 344 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vercel/vercel-plugin --skill domains -a claude-code
Open on GitHub

What domains does

The skill searches for domains, checks availability and prices, and helps register a name, connect it to a project, manage DNS, transfer it, or renew it. Exact-name searches use the public Registrar API; account and project operations use the Vercel CLI or REST API.

The public search endpoint needs no Vercel account, token, or project link. Account operations require an authenticated Vercel CLI session. DNS records are changed at the authoritative DNS provider; vercel dns only manages DNS hosted by Vercel.

What it helps with

  • check domain availability and pricing
  • attach an existing domain to a Vercel project
  • manage DNS records and verify a domain
  • transfer or renew a domain registration

Example prompts for the agent

  • Check availability and pricing for example.com and example.dev.
  • Connect example.com to project my-project under team my-team.
  • Inspect DNS and renewal options for example.com.

How to install domains

1Skills CLI (Vercel)

npx skills add vercel/vercel-plugin --skill domains -a claude-code

2Manually: put the files in place

~/.claude/skills/domains/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/domains/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about domains

How do I install domains in Claude Code?

Run npx skills add vercel/vercel-plugin --skill domains -a claude-code. The skill file is placed at ~/.claude/skills/domains/SKILL.md.

What does domains do?

It searches domain names and checks availability and prices, then helps with registration, project assignment, DNS, transfers, and renewals.

What does domains need to work?

Exact-name searches use the public Registrar API without a Vercel account. Account and project tasks require an authenticated Vercel CLI session or the REST API.

Source text

SKILL.md · Apache-2.0
---
name: domains
description: Search, register, connect, transfer, and renew domain names on Vercel using the CLI or Domains Registrar API. Use for domain availability and pricing, custom domains, DNS records, nameservers, ownership verification, and domain orders.
summary: Search domains without authentication; manage registration, project assignment, DNS, transfers, and renewals with Vercel CLI or API.
metadata:
  priority: 7
  docs:
    - "https://vercel.com/docs/domains/registrar-api"
    - "https://vercel.com/docs/cli/domains"
    - "https://vercel.com/docs/cli/dns"
    - "https://openapi.vercel.sh"
  sitemap: "https://vercel.com/sitemap.xml"
  pathPatterns: []
  bashPatterns:
    - '\b(?:vercel|vc)\s+(?:domains?|dns)\b'
    - 'https://api\.vercel\.com/v1/registrar/'
  importPatterns: []
  promptSignals:
    phrases:
      - "domain name"
      - "domain search"
      - "domain availability"
      - "domain pricing"
      - "buy a domain"
      - "register a domain"
      - "transfer a domain"
      - "renew a domain"
      - "renew my domain"
      - "custom domain"
      - "dns record"
      - "nameserver"
      - "registrar api"
      - "vercel domains"
      - "vercel dns"
    allOf:
      - [domain, vercel]
      - [domain, register]
      - [domain, renew]
      - [domain, transfer]
    anyOf:
      - "availability"
      - "pricing"
      - "dns"
      - "registrar"
    minScore: 6
---

# Domains

Use the public Registrar API for unauthenticated discovery. Use the installed Vercel CLI for account and project operations, or the REST API for structured automation. `vc` and `vercel` are equivalent.

Registration, Vercel team ownership, project assignment, and authoritative DNS are separate. Connecting an already-owned domain does not require buying it or transferring its registration.

## Search before asking for credentials

Start exact-name research with one request returning availability and pricing together:

```bash
curl --fail-with-body --silent --show-error \
  https://api.vercel.com/v1/registrar/domains/search \
  --header 'Content-Type: application/json' \
  --data '{"domains":["example.com","example.dev","example.app"]}'
```

Send 1–200 exact domain names per request. The endpoint checks the supplied names; it does not generate suggestions. Generate candidates from the user's naming constraints, then batch them. No Vercel account, token, or project link is needed.

Results preserve input order. Available entries include `domain`, `available`, `years`, `price`, `renewalPrice`, and `premium`; prices are USD for the returned term. Report registration and renewal costs with that term, and flag premium domains. `available: false` means unavailable **or availability could not be confirmed**; it does not prove someone owns the name. Missing prices are unknown, not zero. Availability and quotes can change before purchase.

For keyword/TLD discovery, a recent CLI can generate candidates:

```bash
vercel domains search acme --tld com --tld dev --available --json
vercel domains check example.com example.dev --json
vercel domains price example.com --json
```

Check `vercel domains --help` and the selected subcommand's `--help` against the installed version (`--json` needs CLI 58.1+; older CLIs use `--format=json`). If discovery is unavailable or the CLI asks for login, use the public endpoint directly. CLI `search` accepts a keyword; API `search` accepts exact names. Do not substitute one input shape for the other.

## Connect and diagnose an existing domain

For authenticated work, inspect `vercel whoami` and use `--scope <team>` when selecting a team. Resolve the intended project before changing its domains.

```bash
vercel domains ls --scope my-team
vercel domains inspect example.com --scope my-team
vercel domains add example.com my-project --scope my-team
vercel domains verify example.com --project my-project --json --scope my-team
```

Use the actual expected DNS records and ownership-verification values returned for that domain and project. Do not hardcode a universal A record or CNAME target. Configure records at the authoritative DNS provider; `vercel dns` changes Vercel DNS only. Preserve unrelated records, especially MX and email-verification TXT records. Nameserver changes require carrying over the zone's required records.

| Task | CLI |
| --- | --- |
| List DNS records | `vercel dns ls example.com` |
| Inspect a record | `vercel dns inspect <record-id> --json` |
| Add the required TXT record | `vercel dns add example.com <record-name> TXT <record-value>` |
| Update an existing record | `vercel dns update <record-id> --value <record-value>` |
| Remove a specific record | `vercel dns rm <record-id>` |
| Move team ownership | `vercel domains move example.com <destination-team>` |
| Remove team ownership | `vercel domains rm example.com` |

After a change, rerun `domains verify` and check DNS propagation and HTTPS. Verification can exit nonzero while returning useful JSON describing the mismatch. An accepted DNS write is not proof that DNS has propagated or a certificate is ready. `domains add --force` can detach the domain from another project; use it only when that reassignment is intended. Removing team ownership is not a registrar transfer or cancellation of registration.

## Purchase, transfer, and renew

Use existing authorization for the exact domain, term, price, and renewal preference. If those choices are unresolved, prepare the current quote before asking. Do not treat a discovery request as permission to purchase. Use real user-provided registrant information and keep tokens, contact data, and transfer codes out of logs and committed files.

| Task | CLI |
| --- | --- |
| Register a domain | `vercel domains buy example.com` |
| Transfer from another registrar | `vercel domains transfer-in example.com` |
| Renew registration | `vercel domains renew example.com` |
| Enable or disable automatic renewal | `vercel domains auto-renew enable example.com` / `disable` (CLI 65.1.0+; older CLIs: `auto-renew example.com on` / `off`) |

Transfer flows may require interactive input. With Vercel CLI 63.1.0+, `domains buy` and `domains renew` run without prompts: pass `--scope <team> --json` without `--amount` to get the price, term, and next command without charging; after a person approves, run the returned command with `--amount <approved-price-in-USD>` (purchases also need registrant flags and exactly one of `--auto-renew` / `--no-auto-renew`). The CLI doesn't retry charges; if the outcome is unknown, run `domains inspect` before retrying. On older CLIs, use the Registrar API with the required payload instead of inventing CLI flags. Moving between Vercel teams uses `domains move`, not `transfer-in`.

## Registrar API

Base URL: `https://api.vercel.com`. Consult the [live OpenAPI schema](https://openapi.vercel.sh) for the selected operation's request and response fields before constructing a mutation.

### Public discovery

Use the [Registrar API reference](https://vercel.com/docs/domains/registrar-api) for public TLD metadata, term-specific domain prices, availability, and contact requirements. These operations require no authentication. Bulk availability and price calls accept 1–50 domains; search accepts 1–200.

TLD base prices do not quote premium domains. Use domain-specific prices for the requested term; price endpoints return `purchasePrice`, unlike search's `price`. Some price fields can be strings rather than numeric quotes; do not submit those as `expectedPrice`.

### Authenticated operations

Send `Authorization: Bearer <token>` and use `?teamId=<team-id>` for the intended team. Use `Content-Type: application/json` for JSON bodies. Reuse a securely available token; do not ask for one for public discovery.

Use the selected operation in the live schema for purchases, transfers, renewals, automatic renewal, nameservers, and contact verification. Inspect asynchronous results with `GET /v1/registrar/orders/{orderId}`. An empty nameservers array selects Vercel defaults; contact verification is unavailable for the first 30 minutes after purchase.

For purchases, retrieve the contact schema and supply required TLD-specific values through the purchase payload's `contactInformation.additional` field. For transfers, use only contact fields accepted by that operation's live schema; it does not accept the purchase-only `additional` field. Punycode purchases require a supported `languageCode`; inspect the TLD metadata. Quote the exact operation and term, then use that numeric quote as `expectedPrice`. Reassess a price mismatch against the user's authorized spend instead of silently accepting an increase.

Purchases, renewals, and transfers can complete asynchronously. Save the returned order ID, inspect the order and each domain's status, and report pending or failed outcomes accurately. If a submission times out, reconcile its order status before resubmitting a charge. Stop polling when completed or failed; if still pending after a bounded check, return the order ID and next status-check action. Complete any required registrant email verification.

Use `/v1/registrar/*` for registrar operations instead of sunset legacy purchase, price, availability, or transfer endpoints. Existing project-domain and DNS APIs serve separate purposes; the registrar API does not replace them.

© vercel · Apache-2.0 · vercel/vercel-plugin

Similar skills

All skills for DevOps and infrastructure →

From the same set9

access-protected-vercel-deployment access-protected-vercel-deployment — a skill that tells your agent how to get past Vercel Authentication, SSO and Deployment Protection: vercel curl for HTTP, a short-lived OIDC token for browsers. CX Codex +1 2,600installs build-agents build-agents provides default guidance for building AI agents using Vercel's eve framework. Helps scaffold agent projects, configure tools, and set up schedules. CX Codex +1 1,500installs create-a-backend create-a-backend helps plan and architect backend workloads on Vercel before writing implementation code. Selects the right compute, queues, workflows, and database integrations. CX Codex +1 708installs vercel-schedules vercel-schedules — a skill for Claude Code guides scheduled tasks and cron jobs in Vercel. Activates when configuring recurring background work, migration from crons, or one-time reminders. CX Codex +1 183installs queues Learn how to use Vercel Queues for background work, message buffering, and event fan-out. The skill also helps decide when Workflows fit better. CX Codex +1 178installs custom-metrics custom-metrics — a skill for Claude Code that instruments Vercel Functions with custom telemetry. It injects metric() calls into server handlers to record latencies and execution outcomes. CX Codex +1 148installs is-agentic The is-agentic Claude Code skill scores how ready a website, domain, or public MCP endpoint is for AI agents. It can fetch a report or help address the issues behind a score. CX Codex +1 108installs vercel vercel is a Claude Code plugin for managing Vercel deployments, checking builds, and reading logs. It brings Vercel tools into work on projects, domains, and frontend infrastructure. ★ 344repo stars

Project sponsors

Companies that keep this analytics open