domains
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.
- Installs
- 100
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/vercel/vercel-plugin --skill domains- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads domains automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
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:
vercel domains search acme --tld com --tld dev --available --format=json
vercel domains check example.com example.dev --format=json
vercel domains price example.com --format=json
Check vercel domains --help and the selected subcommand's --help against the installed version. 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.
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 --format=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> --format=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 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 for the selected operation's request and response fields before constructing a mutation.
Public discovery
Use the Registrar API reference 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.
FAQ
What does the domains skill do?
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.
How do I install domains?
Run npx skills add https://github.com/vercel/vercel-plugin --skill domains in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/domains/ (personal) or .claude/skills/domains/ (project).
Which AI agents can use domains?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is domains safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains domains?
It is published by vercel in vercel/vercel-plugin. It has 100 recorded installs.
More from vercel/vercel-plugin
access-protected-vercel-deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTEDSOURCESENVIRONMENTMISMATCH appears; or when choosing between vercel curl and the x-vercel-trusted-oidc-idp-token header.
build-agents
vercel/vercel-plugin
Default guidance for building AI agents. Use for generic requests to build, create, scaffold, design, architect, or implement an AI agent, agent app, tool-calling agent, durable agent, multi-agent system, or scheduled agent.
create-a-backend
vercel/vercel-plugin
Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Daemons, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.
flags-sdk
vercel/vercel-plugin
Implement feature flags in Next.js or SvelteKit code with the Flags SDK (flags npm package). Use when installing or configuring the SDK, declaring flags with flag(), wiring a provider adapter (@flags-sdk/vercel, Statsig, LaunchDarkly, PostHog, GrowthBook, Global Config, OpenFeature, and others), using identify, dedupe, or evaluate, keeping pages static with precompute, setting up Flags Explorer, or encrypting flag values. For planning a flag, Vercel Flags rollouts and experiments, the vercel flags CLI, or other frameworks, use the vercel-flags skill.
queues
vercel/vercel-plugin
Vercel Queues guidance — durable topics with at-least-once delivery, independent consumer groups, retries, delays, and idempotency keys via @vercel/queue (JS) or vercel-queue (Python). Use when deferring background work, buffering traffic, fanning out events, or choosing between Queues and Workflows.
custom-metrics
vercel/vercel-plugin
Emit and query Vercel Custom Metrics. Use when instrumenting application or business measurements in Vercel Functions, using metric() from @vercel/functions, choosing metric names and attributes, or querying emitted values with vc metrics.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.