URL Title Skill

What this skill does

Let your agent read page titles. Call it as an MCP tool to fetch the live title of any web page from its URL. 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 URL Title Skill — exactly what your agent gets back when it makes the call.

vervekit · urltitletool call

{
  "url": "https://blog.apiverve.com/chuck-norris-api-how-to"
}

result

title: Chuck Norris API: How to Easily Add Joke…
h1: [ 1 item ]

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

Sign in to try

Ways to use it

Domain intelligence in one skill

Enable URL Title so your app can add url title 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 urltitle to ground a claim about a domain in real records before it reasons about risk.

Enrich from your backend

Call URL Title over REST to add url title 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.

urltitle

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/urltitle

Ask your agent

“Enable URL Title and ask your agent to add url title to your app.”
“Pull the records and health for example.com.”

URL Title Skill, answered

How to connect it over MCP or REST.

How do I add URL Title to my app or agent?

Enable the URL Title Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the urltitle 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 url title 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 URL Title appears as a standard tool with nothing skill-specific to integrate.

How many credits does a URL Title call cost?

Each call costs 5 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 URL Title is available immediately.

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

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

More Domain Data skills

Browse all skills

Domain intelligence in one skill

A tool for security & research agents

Enrich from your backend

URL Title Skill, answered

Give your software a way to act on the world.

Scaling in production?