Air Quality Skill

What this skill does

Let your agent read live air quality. Call it as an MCP tool to pull PM2.5, ozone and the AQI for any city or ZIP 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 Air Quality Skill — exactly what your agent gets back when it makes the call.

vervekit · airqualitytool call

{
  "city": "San Francisco"
}

result

pm2_5: 16.75
pm10: 18.85
carbonMonoxide: 387.85
ozone: 9
nitrogenDioxide: 38.55
sulfurdioxide: 5.95
usEpaIndex: 2
gbDefraIndex: 2

+2 more fields

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

Sign in to try

Ways to use it

Add weather without a provider

Give your app the ability to add air quality to your app by enabling one skill instead of signing up for a weather API and wiring its SDK. Same key as every other skill.

An agent tool for conditions

Over MCP, your model calls the airquality tool when a task needs live conditions — trip planning, logistics, scheduling — without any per-source plumbing.

REST from any backend

Node, Python, Go — anything that can send a GET can call Air Quality directly, so a server-side job can add air quality to your app in one request.

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.

airquality

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

Ask your agent

“Enable Air Quality and ask your agent to add air quality to your app.”
“What's the weather in Tokyo right now?”

Air Quality Skill, answered

How to connect it over MCP or REST.

How do I add Air Quality to my app or agent?

Enable the Air Quality Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the airquality 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 air quality 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 Air Quality appears as a standard tool with nothing skill-specific to integrate.

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

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

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

More Weather skills

Browse all skills

Add weather without a provider

An agent tool for conditions

REST from any backend

Air Quality Skill, answered

Give your software a way to act on the world.

Scaling in production?