Ambeedata Ambee Air Quality API

Name: Ambee Air Quality API
Brand: Ambee Air Quality API
Availability: InStock

✓ Official Vendor SpecData EnrichmentAddress ValidationapiKey7 EndpointsREST

For 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.

Install Jentic One Beta

Connect the Ambee Air Quality API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ambee Air Quality API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ambee Air Quality API.

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

GET STARTED

Start building with Ambee Air Quality API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ 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.

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.

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.

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.

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

7 endpoints — 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.

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Ambee Air Quality API through Jentic.

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.