PM25.in Air Quality API

Name: PM25.in Air Quality API
Brand: PM25.in Air Quality API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey11 EndpointsREST

For Agents

Programmatically get simplified city aqi data, get detailed city aqi data. Covers 11 operations with apiKey authentication.

Install Jentic One Beta

Connect the PM25.in Air Quality API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PM25.in 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 PM25.in Air Quality API.

Get simplified city AQI data

Access PM25.in Air Quality API resources via REST API

Use Cases

GET STARTED

Start building with PM25.in Air Quality API

Explore with Jentic

View OpenAPI Document

Automated City Data Management

Automate city data operations by combining multiple PM25.in Air Quality API endpoints. Agents can get detailed city aqi data and then get pm2.5 data for a city in a single workflow.

Call GET /querys/aqi_details.json to get detailed city aqi data, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PM25.in Air Quality API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'get simplified city aqi data', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — pm25.

METHOD

PATH

DESCRIPTION

GET

/querys/only_aqi.json

Get simplified city AQI data

GET

/querys/aqi_details.json

Get detailed city AQI data

GET

/querys/pm2_5.json

Get PM2.5 data for a city

GET

/querys/pm10.json

Get PM10 data for a city

GET

/querys/co.json

Get CO data for a city

GET

/querys/no2.json

Get NO2 data for a city

GET

/querys/o3.json

Get O3 data for a city

GET

/querys/so2.json

Get SO2 data for a city

GET

/querys/only_aqi.json

Get simplified city AQI data

GET

/querys/aqi_details.json

Get detailed city AQI data

GET

/querys/pm2_5.json

Get PM2.5 data for a city

GET

/querys/pm10.json

Get PM10 data for a city

GET

/querys/co.json

Get CO data for a city

Why Jentic?

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

Credential isolation

PM25.in Air Quality API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get simplified city aqi data') and Jentic returns the matching PM25.in Air Quality API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PM25.in Air Quality API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using PM25.in Air Quality API through Jentic.

What authentication does the PM25.in Air Quality API use?

The PM25.in Air Quality API uses an API key passed in the `token` query. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get simplified city aqi data with the PM25.in Air Quality API?

Yes. Use the GET /querys/only_aqi.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PM25.in Air Quality API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get simplified city aqi data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get simplified city aqi data'. Jentic returns the matching PM25.in Air Quality API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the PM25.in Air Quality API have?

The PM25.in Air Quality API exposes 11 endpoints covering city data, pollutants, station operations.