AQICN Air Quality Index API

Name: AQICN Air Quality Index API API
Brand: AQICN Air Quality Index API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey5 EndpointsREST

For Agents

Read real-time air quality index and pollutant data for any city, coordinate, or map region worldwide.

Quickstart

Get started with AQICN Air Quality Index API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"check the air quality in a city"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AQICN Air Quality Index API API.

Look up the real-time AQI and pollutant breakdown for a named city

Resolve the AQI for the user's current location using IP geolocation

Fetch AQI for arbitrary latitude and longitude coordinates

Search the AQICN station directory by name or keyword

GET STARTED

Start building with AQICN Air Quality Index API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AQICN Air Quality Index API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AQICN Air Quality Index API, keeping it validated and agent-ready. AQICN provides real-time air quality index data for over 1,000 cities worldwide, including individual pollutant readings such as PM2.5, PM10, NO2, CO, SO2, and Ozone. The API supports city lookups by name, IP-based geolocation, latitude/longitude coordinates, station search, and bounding-box map queries. Authentication is via an API token passed as a query parameter.

Use Cases

Patterns agents use AQICN Air Quality Index API API for, with concrete tasks.

★ City-Level Air Quality Lookup

Fetch the current AQI for a named city and surface the dominant pollutant alongside the index value. Travel and outdoor-activity products use this to give users a one-glance read on whether to go outside, change plans, or take protective measures. The /feed/{city} endpoint returns a single JSON object with the city's AQI, dominant pollutant, and individual readings.

Call GET /feed/{city} for the requested city name and return the AQI value plus the dominant pollutant in plain English.

Coordinate-Based AQI for Mobile Apps

When a mobile app has the user's GPS coordinates, query AQICN by lat/lng to get the AQI from the closest monitoring station. Outdoor fitness and weather apps use this to show hyperlocal air quality without asking the user for their city. The /feed/geo:{lat};{lng} endpoint returns the nearest station's reading and identifies which station was used.

Call GET /feed/geo:{lat};{lng} with the user's coordinates and return the AQI, dominant pollutant, and the name of the nearest station.

Map Overlay of Stations

Render a map of monitoring stations and their AQI values inside a visible bounding box. Air quality dashboards and environmental research tools use this to show regional patterns without making one call per station. The /map/bounds endpoint returns all stations within a lat/lng box in a single response.

Call GET /map/bounds with the user's current map viewport coordinates and return the list of stations with their AQI values for rendering.

AI Agent Air Quality Briefings via Jentic

An assistant agent that drafts a daily morning briefing can call AQICN through Jentic to include today's air quality alongside weather and calendar context. The agent searches for the AQI lookup operation, loads the schema, and executes the city feed call without managing the API token. Jentic resolves the token from its credential vault.

Use Jentic search 'check the air quality in a city', load the schema for GET /feed/{city}, then execute with the user's home city and return the AQI for the briefing.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for aqicn air quality index api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/feed/{city}

Get AQI for a city

GET

/feed/here

Get AQI for the IP geolocation

GET

/feed/geo:{lat};{lng}

Get AQI by coordinates

GET

/search

Search stations by name

GET

/map/bounds

List stations in a bounding box

GET

/feed/{city}

Get AQI for a city

GET

/feed/here

Get AQI for the IP geolocation

GET

/feed/geo:{lat};{lng}

Get AQI by coordinates

GET

/search

Search stations by name

GET

/map/bounds

List stations in a bounding box

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AQICN tokens are stored encrypted in the Jentic vault. Agents receive scoped access — the raw token never enters the agent's context and is injected at request time as the token query parameter.

Intent-based discovery

Agents search by intent (e.g. 'check the air quality in a city') and Jentic returns matching AQICN operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct AQICN integration: a few hours to handle token registration, response shape, and station selection edge cases. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

OpenWeatherMap API

Pair OpenWeatherMap forecasts with AQICN air quality for combined outdoor-activity briefings.

Use OpenWeatherMap for temperature and precipitation, then call AQICN for the air quality reading at the same location.

Complementary

WeatherAPI

WeatherAPI exposes weather and basic air quality; combine with AQICN when station-level pollutant detail is needed.

Use WeatherAPI for general forecast data; switch to AQICN when the workflow requires individual pollutant readings or station identifiers.

Alternative

BreezoMeter API

Hyperlocal air quality and pollen API with sub-kilometre resolution, contrasted with AQICN's station-derived values.

Choose BreezoMeter when sub-kilometre resolution and pollen data are required; pick AQICN for global station coverage and free non-commercial access.

FAQs

Specific to using AQICN Air Quality Index API API through Jentic.

Why is there no official OpenAPI spec for AQICN Air Quality Index API?

AQICN does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AQICN Air Quality Index API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AQICN API use?

AQICN uses an API token passed as a query parameter named token on every request. Tokens are issued free for non-commercial use at aqicn.org/data-platform/token. Through Jentic, the token is stored encrypted in the vault and never enters the agent's context.

Can I get historical air quality data with this API?

No. The endpoints in this spec return real-time and forecast values only. Historical archive access is offered separately by AQICN under their data platform — contact AQICN for bulk historical data.

What pollutants are included in the AQI response?

City and geo feeds return individual readings for PM2.5, PM10, NO2, CO, SO2, and Ozone where the station reports them, plus the dominant pollutant identifier and weather context such as temperature and humidity.

What are the rate limits for the AQICN API?

AQICN enforces a rate limit of around 1,000 requests per second per token in practice; the OpenAPI spec does not declare a fixed value. For heavy production use, contact AQICN to request a higher quota.

How do I check the AQI in a city through Jentic?

Install Jentic with pip install jentic, search for 'check the air quality in a city', load the schema for GET /feed/{city}, then execute with the city name. Jentic injects the token automatically.