canonical: https://jentic.com/apis/ambeedata.com/ambeedata

# Ambeedata Ambee Air Quality API

The Ambee Air Quality API delivers real-time, historical, and forecast air quality data indexed by latitude and longitude, postal code, city, or country code. Each response returns the Air Quality Index (AQI) plus pollutant concentrations for CO, NO2, O3, PM10, PM2.5, and SO2 at the requested location. The spec exposes 7 GET endpoints under api.ambeedata.com, authenticated with a single x-api-key header. It is commonly used by health, climate, logistics, and consumer apps that need pollution data without running their own monitoring network.

## For AI agents

Lets agents fetch real-time, historical, or forecast air quality (AQI plus CO, NO2, O3, PM10, PM2.5, SO2) for any location worldwide via x-api-key authenticated GET calls.

## Scope

Does not handle weather, pollen, fire, soil, or water vapour readings - use for air quality (AQI plus CO, NO2, O3, PM10, PM2.5, SO2) only.

## Capabilities

- Retrieve current AQI and pollutant concentrations by latitude and longitude for any location worldwide
- Look up the latest air quality reading by postal code, city name, or ISO country code
- Pull historical air quality readings for a coordinate or postal code over a custom date range
- Generate hourly air quality forecasts up to several days ahead by latitude and longitude
- Compare pollutant levels (CO, NO2, O3, PM10, PM2.5, SO2) across multiple locations in a single workflow
- Surface AQI values for risk-aware decisions in logistics, outdoor events, and health applications

## Use cases

### Health and Wellness App Pollution Alerts

Asthma, allergy, and fitness apps can warn users before they head outside by polling Ambee's latest AQI for the user's coordinates and pushing a notification when PM2.5 or O3 crosses a threshold. Ambee's coverage spans most populated regions worldwide, and a single GET call returns both the AQI band and the underlying pollutant readings the app needs to render a chart.

Example prompt: Call GET /latest/by-lat-lng with lat=40.7128 and lng=-74.0060 and return the AQI value plus the PM2.5 concentration

### Outdoor Event and Venue Risk Checks

Event organisers and outdoor sports apps can query the forecast endpoint for the start time and venue location to decide whether to proceed, postpone, or move indoors. Ambee's forecast returns hourly pollutant levels so an agent can flag the riskiest window without pulling ground-level monitor data manually.

Example prompt: Call GET /forecast/aq/by-lat-lng with the venue coordinates and flag any hour in the next 24 where AQI exceeds 150

### Climate and ESG Reporting

Sustainability teams pulling year-over-year pollutant trends for ESG reports can use the historical endpoints to fetch hourly readings by coordinate or postal code, then aggregate into monthly averages for offices, warehouses, or supplier sites. The same call covers six pollutants so a single integration powers the full report.

Example prompt: Call GET /history/by-postal-code with postalCode=10001 and a 30-day date range, then return the daily mean PM2.5 and NO2

### AI Agent Climate Lookups

Climate-aware AI agents (travel planners, delivery routers, smart-home automations) can query Ambee through Jentic without storing raw API keys. The agent searches Jentic for an air quality intent, loads the input schema, and Jentic injects the x-api-key at execution time. Useful when the same agent already calls weather, geocoding, or routing APIs.

Example prompt: Search Jentic for 'check air quality by city', load the operation backed by GET /latest/by-city, and execute with city='Delhi' to return the current AQI

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /latest/by-lat-lng | Latest air quality by coordinates |
| GET | /latest/by-postal-code | Latest air quality by postal code |
| GET | /latest/by-city | Latest air quality by city |
| GET | /latest/by-country-code | Latest air quality by country |
| GET | /history/by-lat-lng | Historical air quality by coordinates |
| GET | /history/by-postal-code | Historical air quality by postal code |
| GET | /forecast/aq/by-lat-lng | Air quality forecast by coordinates |

## Key resources

- **Latest** — Current AQI and pollutant readings by coordinate, postal code, city, or country
- **History** — Historical hourly air quality readings over a date range
- **Forecast** — Hourly air quality forecast by coordinate

## Why Jentic

- **Setup:** Wiring the Ambee Air Quality API by hand means managing the x-api-key header and choosing between the by-coordinate, by-postal-code, and by-city lookup routes yourself. Through Jentic you install once, import Ambee from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Ambee passes location as query parameters rather than resource ids in the path, so scope the agent to the operations it needs, such as the latest and forecast air-quality lookups. You choose the operations it may call, so historical queries are not included unless you add them.
- **Credential handling:** Your Ambee x-api-key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check current air quality by coordinates' or 'forecast air quality for a city', and Jentic returns the matching Ambee operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **OpenWeatherMap** — Bundles air pollution endpoints alongside weather forecasts under a single API key
- **AQICN World Air Quality Index** — Crowd-sourced and government monitor data with strong city-level coverage
- **BreezoMeter** — Hyperlocal air quality and pollen data with tile-level resolution
- **WeatherAPI** — Pairs current and forecast weather alongside Ambee's pollution data

## FAQ

### What authentication does the Ambee Air Quality API use?

Ambee uses API key authentication via the x-api-key header on every request. There is no OAuth flow or signed-request scheme. Through Jentic, the x-api-key is stored in your Jentic One instance and injected at execution time, so the agent never sees the raw key.

### Can I get historical air quality data with the Ambee Air Quality API?

Yes. GET /history/by-lat-lng and GET /history/by-postal-code return hourly historical AQI and pollutant concentrations (CO, NO2, O3, PM10, PM2.5, SO2) for a date range you specify. There is no separate historical-only product.

### What are the rate limits for the Ambee Air Quality API?

Limits depend on the Ambee plan tier - free trial keys are typically capped at a few hundred calls per day, while paid tiers support several requests per second. The spec does not enumerate limits, so confirm against the plan listed in the Ambee dashboard.

### How do I forecast air quality through Jentic?

Search Jentic for 'forecast air quality by coordinates'. Jentic returns the operation backed by GET /forecast/aq/by-lat-lng, you load the schema (lat and lng are required), and execute. Jentic injects the x-api-key from the vault. Run it through Jentic One, the self-hosted execution layer.

### Does the Ambee Air Quality API include weather data?

No. This spec only exposes air quality readings - AQI plus the six pollutants. Ambee sells separate APIs for weather, pollen, soil, fire, and water vapour, but those are not part of this OpenAPI spec. For temperature and precipitation, pair this API with a weather provider.

### Which pollutants does each response include?

Every latest, history, and forecast response includes the AQI value plus concentrations for CO, NO2, O3, PM10, PM2.5, and SO2. Units are micrograms per cubic metre for the particulates and parts per billion for the gases, matching the standard EPA reporting convention.

### Can I limit what my agent is allowed to do with the Ambee Air Quality API?

Yes. Jentic One is self-hosted, so you set the rules that decide which Ambee operations and credentials your agent may use. Because Ambee passes location as query parameters rather than resource IDs in the path, you scope the agent to only the operations it needs, such as the latest and forecast air-quality lookups (GET /latest/by-lat-lng, /latest/by-city, /forecast/aq/by-lat-lng). The historical endpoints like GET /history/by-postal-code stay off limits unless you add them, and your x-api-key is injected at execution time so the agent never sees the raw key.