City Data Lookup Skill

What this skill does

Let your agent resolve any city to its population, country and coordinates. Call it as an MCP tool to add place data across 150K+ cities. 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 City Data Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · citieslookuptool call

{
  "city": "San Francisco"
}

result

search: San Francisco
foundCities: [ 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

Location smarts in one toggle

Enable City Data Lookup and your app can look up city data — geocode, resolve timezones, measure distance — without integrating a maps provider or managing another key.

A tool agents call to place things

Over MCP, citieslookup becomes the tool your model reaches for whenever it needs to ground reasoning in a real location.

Compose with your logic

Call City Data Lookup from your backend and feed its structured output straight into the code you already have.

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.

citieslookup

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

Ask your agent

“Enable City Data Lookup and ask your agent to look up city data.”
“Where is this location and what timezone is it in?”

City Data Lookup Skill, answered

How to connect it over MCP or REST.

How do I add City Data Lookup to my app or agent?

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

How many credits does a City Data Lookup call cost?

Each call costs 1 credit. 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 City Data Lookup is available immediately.

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

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

More Geography skills

Browse all skills

Location smarts in one toggle

A tool agents call to place things

Compose with your logic

City Data Lookup Skill, answered

Give your software a way to act on the world.

Scaling in production?