Domain Age Skill

What this skill does

Domain Age returns when a domain was first registered and how old it is in days, months and years, with a readable age, an age bracket and a newly-registered flag. Paid plans add the expiration date and the last registry update. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Domain Age Skill — exactly what your agent gets back when it makes the call.

vervekit · domainagetool call

{
  "domain": "myspace.com"
}

result

domain: myspace.com
createdDate: 1996-02-22T05:00:00Z
domainAgeDays: 11193
domainAgeMonths: 367
domainAgeYears: 30.6
domainAgeText: 30 years, 7 months
ageCategory: veteran
isNewlyRegistered: false

+3 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Domain intelligence in one skill

Enable Domain Age so your app can add domain age to your app — pull records, health, or ownership — without integrating a WHOIS/DNS provider per data type.

A tool for security & research agents

Over MCP, your model calls domainage to ground a claim about a domain in real records before it reasons about risk.

Enrich from your backend

Call Domain Age over REST to add domain age to your app across a list of domains in a scheduled job, one key for all of it.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

domainage

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/domainage

Ask your agent

“Enable Domain Age and ask your agent to add domain age to your app.”
“Pull the records and health for example.com.”

Domain Age Skill, answered

How to connect it over MCP or REST.

How do I add Domain Age to my app or agent?

Enable the Domain Age Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the domainage tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add domain age to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Domain Age appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Domain Age call cost?

Each call costs 10 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Domain Age is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Domain Age is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Domain intelligence in one skill

A tool for security & research agents

Enrich from your backend

Domain Age Skill, answered

Other ways to use Domain Age

Give your software a way to act on the world.

Scaling in production?