Airport Lookup Skill

What this skill does

Let your agent resolve any airport code. Call it as an MCP tool to fetch name, city, country and coordinates from an IATA or ICAO code. 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 Airport Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · airportstool call

{
  "iata": "MCI"
}

result

icao: KMCI
iata: MCI
name: Kansas City International Airport
city: Kansas City
state: Missouri
country: US
elevation: 1026
lat: 39.2975997925

+3 more fields

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

Ways to use it

One toggle, a new capability

Enable Airport Lookup and your app or agent can look up airport on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, Airport Lookup appears to your model as the airports tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit Airport Lookup to look up airport inline in your own server-side code.

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.

airports

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

Ask your agent

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

Airport Lookup Skill, answered

How to connect it over MCP or REST.

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

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

How many credits does a Airport 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 Airport Lookup is available immediately.

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

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

One toggle, a new capability

A tool agents call themselves

REST from any backend

Airport Lookup Skill, answered

Give your software a way to act on the world.

Scaling in production?