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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpm25.in%2Fpm25" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpm25.in%2Fpm25" | 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

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

★ Developer Tools Operations

Use the PM25.in Air Quality API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including get simplified city aqi data, get detailed city aqi data, get pm2.5 data for a city.

GET STARTED

Start building with PM25.in Air Quality API

Explore with Jentic One

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PM25.in Air Quality API by hand means attaching your API key as a query token on every call to www.pm25.in and selecting the right pollutant endpoint per request. Through Jentic you install once, import the PM25.in Air Quality API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

PM25.in reads take their city and station selection as query parameters rather than pinning a resource in the URL path, so scope the agent to the operations it needs, such as fetching city AQI or a specific pollutant reading. Every endpoint here is read-only, so the agent's allowed set is simply the pollutant queries you grant it.

Credential isolation

Your PM25.in 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 'get simplified city AQI data' or 'read PM2.5 levels', and Jentic returns the matching PM25.in operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the PM25.in Air Quality API?

Yes. Because you run Jentic One yourself, your own rules decide which PM25.in operations and credentials the agent may use. Every endpoint here is read-only, so you grant only the queries the agent needs, such as fetching simplified city AQI, detailed city AQI, or a single pollutant reading like PM2.5, PM10, CO, NO2, O3, or SO2. Since the city and station are passed as query parameters rather than pinned in the path, the agent's allowed set is simply the pollutant and AQI queries you approve.

PM25.in Air Quality API

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

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey11 EndpointsREST

For Agents

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

Use for: I need to simplified city aqi data, I want to detailed city aqi data, Search for pm2.5 data for a city, Find all pm10 data for a city

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

PM25.in provides real-time air quality data for cities across China, including AQI, PM2.5, PM10, CO, NO2, O3, and SO2 readings from monitoring stations. Data is available per city (simplified or detailed), per monitoring station, as a national aggregate, or as a city ranking. The API exposes 11 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

52%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PM25.in Air Quality API to your agent

Capabilities

Use Cases

Start building with PM25.in Air Quality API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PM25.in Air Quality API

Jentic AI Readiness Score

PM25.in Air Quality API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness