Docs/Sources/WHOIS Grounding Data for AI Agents

WHOIS Grounding Data for AI Agents

Lookup domain registration

OperationalCredits 8 per callp50 1552msDomain Data

Overview

WHOIS Lookup is a domain WHOIS API: it queries the registry for a domain name and returns its registration record (registrar, creation, update and expiry dates, EPP status codes and authoritative nameservers) plus domain age computed from the creation date. Paid plans extend it to IP address and ASN WHOIS.

Live Test WHOIS Grounding Data for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as WHOISGroundingDataforAIAgents. 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": "WHOISGroundingDataforAIAgents",
  "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 WHOISGroundingDataforAIAgents 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 name for which you want to get the registration data (e.g., myspace.com)
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": {
    "domainName": "MYSPACE.COM",
    "registryDomainID": "3877095_DOMAIN_COM-VRSN",
    "createdDate": "1996-02-22T05:00:00Z",
    "expiryDate": "2029-02-23T05:00:00Z",
    "updatedDate": "2023-01-17T00:16:21Z",
    "domainStatus": [
      "client delete prohibited https://icann.org/epp#client delete prohibited",
      "client renew prohibited https://icann.org/epp#client renew prohibited",
      "client transfer prohibited https://icann.org/epp#client transfer prohibited",
      "client update prohibited https://icann.org/epp#client update prohibited"
    ],
    "dNSSEC": "unsigned",
    "registrar": "GoDaddy.com, LLC",
    "registrarIANAID": "146",
    "registrarURL": "http://www.godaddy.com",
    "registrarAbuseContactEmail": "[email protected]",
    "registrarAbuseContactPhone": "tel:480-624-2505",
    "nameServers": [
      "ns-cloud-a2.googledomains.com",
      "ns-cloud-a3.googledomains.com",
      "ns-cloud-a4.googledomains.com",
      "ns-cloud-a1.googledomains.com"
    ],
    "domain": "myspace.com",
    "fetchedAtUTC": "2025-12-17T01:54:05.069Z",
    "tld": "com",
    "status": "active",
    "domainAgeDays": 11094,
    "domainAgeYears": 30.4,
    "isRecentlyRegistered": false,
    "trustScore": 93,
    "trustLevel": "high"
  }
}

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
domainNamestringMYSPACE.COMThe domain name in uppercase format
registryDomainIDPremiumstring3877095_DOMAIN_COM-VRSNUnique registry identifier for the domain
createdDatestring1996-02-22T05:00:00ZDomain creation date in ISO 8601 format
expiryDatestring2029-02-23T05:00:00ZDomain expiration date in ISO 8601 format
updatedDatestring2023-01-17T00:16:21ZDomain last updated date in ISO 8601 format
domainStatusarray["client delete prohibited https://icann.org/epp#client delete prohibited","client renew prohibited https://icann.org/epp#client renew prohibited","client transfer prohibited https://icann.org/epp#client transfer prohibited"]Array of domain status flags with EPP codes
dNSSECPremiumstringunsignedDNSSEC status (signed or unsigned)
registrarstringGoDaddy.com, LLCDomain registrar company name
registrarIANAIDPremiumstring146Registrar's IANA ID number
registrarURLstringhttp://www.godaddy.comRegistrar's website URL
registrarAbuseContactEmailPremiumstring[email protected]Registrar abuse contact email address
registrarAbuseContactPhonePremiumstringtel:480-624-2505Registrar abuse contact phone number
nameServersarray["ns-cloud-a2.googledomains.com","ns-cloud-a3.googledomains.com","ns-cloud-a4.googledomains.com"]Array of authoritative nameserver hostnames
domainstringmyspace.comDomain name in lowercase format
fetchedAtUTCPremiumstring2025-12-17T01:54:05.069ZWhen this record was fetched from the registry (ISO 8601); cached for up to 24 hours
tldstringcomTop-level domain extension
statusstringactiveCurrent domain registration status
domainAgeDaysnumber11094Age of the domain in days, derived from the creation date
domainAgeYearsnumber30.4Age of the domain in years (one decimal), derived from the creation date
isRecentlyRegisteredPremiumbooleanfalseWhether the domain was registered within the last 90 days — a common fraud/phishing signal
trustScorePremiumnumber930-100 trust score derived from domain age, registration recency, expiry runway and DNSSEC
trustLevelPremiumstringhighCategorical trust level (low, medium, high) derived from the trust score

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 domainName: 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 8 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Expiration Monitoring
Domain portfolio managers inspect expiration dates and registrar details to schedule timely renewals before web properties lapse or drop.
Phishing Detection
Security teams flag newly created sender domains during user onboarding by reading domain age in days directly from the registration record.
Trademark Infringement Review
When auditing suspicious brand lookalikes, legal specialists identify the sponsoring registrar and nameserver hosts to route takedown notices accurately.
Vendor Infrastructure Auditing
Evaluate third-party vendor websites by verifying active domain status codes, current registration timelines, and authoritative nameserver delegations.

Other ways to use WHOIS Grounding Data for AI Agents

Set up WHOIS Grounding Data for AI Agents 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?