University Lookup Skill

What this skill does

Let your agent find a university by name or tell whether an email address belongs to one. 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 University Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · universitylookuptool call

{
  "name": "Stanford"
}

result

domain: null
isAcademicDomain: null
matchType: null
matchedDomain: null
count: 1
totalMatches: 1
universities: [ 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

Trusted facts in one call

Enable University Lookup and your app can look up university from a live source instead of shipping a lookup table you have to keep current.

A tool agents call for ground truth

Over MCP, your model calls universitylookup to fetch a reference value at the moment it needs it, rather than recalling it imperfectly.

REST from any stack

Call University Lookup directly to look up university inline, one key across every skill.

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.

universitylookup

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

Ask your agent

“Enable University Lookup and ask your agent to look up university.”
“Use the University Lookup skill for me.”

University Lookup Skill, answered

How to connect it over MCP or REST.

How do I add University Lookup to my app or agent?

Enable the University Lookup Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the universitylookup 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 look up university — 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 University Lookup appears as a standard tool with nothing skill-specific to integrate.

How many credits does a University Lookup call cost?

Each call costs 2 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 University Lookup is available immediately.

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

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

More Reference Data skills

Browse all skills

Trusted facts in one call

A tool agents call for ground truth

REST from any stack

University Lookup Skill, answered

Other ways to use University Lookup

Give your software a way to act on the world.

Scaling in production?