Docs/Sources/Domain Availability Grounding Data

Domain Availability Grounding Data

Check domain availability

OperationalCredits 10 per callp50 911msDomain Data

Overview

Domain Availability Checker works by analyzing the domain provided and checking if it is available. It uses advanced algorithms to check the availability of the domain and returns if the domain is available or not.

Live Test Domain Availability Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as DomainAvailabilityGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "DomainAvailabilityGroundingData",
  "arguments": {
    "domain": "myspace.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about myspace.com in the terms this source covers is enough for it to reach for DomainAvailabilityGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
domainRequiredstringThe domain to check if it is available
domain

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "myspace.com",
    "available": false,
    "owner": {
      "registrar": "GoDaddy.com, LLC",
      "createdDate": "1996-02-22T05:00:00Z",
      "expiryDate": "2029-02-23T05:00:00Z"
    },
    "source": "rdap"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
domainstringmyspace.comThe domain name that was checked for availability
availablebooleanfalseWhether the domain is available for registration
ownerobject{…}Registration details for a taken domain; null when the domain is available
owner.registrarPremiumstringGoDaddy.com, LLCThe registrar company managing the domain registration
owner.createdDatestring1996-02-22T05:00:00ZWhen the domain was first registered (ISO 8601)
owner.expiryDatestring2029-02-23T05:00:00ZWhen the current registration expires (ISO 8601)
sourcestringrdapWhich lookup answered: rdap, whois, rdap_proxy, whois_proxy, or cache

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at available: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Business Name Generators
When entrepreneurs test company names, business formation apps verify if matching dot-com addresses are unregistered before finalizing entity paperwork.
Domain Reseller Storefronts
Show buyers instant availability flags and registration expiry dates directly inside custom search bars for registrar and web hosting portals.
Trademark Defense Audits
Legal teams scan potential brand collisions across key top-level domains, inspecting registration dates to establish prior use or bad-faith squatting.
Agency Rebranding Workflows
Filter out claimed domains early during client naming sprints so design studios pitch only project handles that can actually be acquired.

Other ways to use Domain Availability Grounding Data

Set up Domain Availability Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Domain Data:

Was this page helpful?