OpenAQ
OpenAQ is a non-profit organization that focuses on collecting and sharing air quality data from around the world. By providing access to this information through their open-source platform, OpenAQ aims to empower individuals, communities, and organizations to take action towards improving air quality and public health.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles OpenAQ the way a machine reads it — 36 machine-readable artifacts across 28 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenAQ scores 39.4/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OpenAQ
Each block below is one kind of artifact we hold for OpenAQ. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OpenAQ Averages API
The Averages API from OpenAQ — 1 operation(s) for averages.
OpenAQ Cities API
The Cities API from OpenAQ — 2 operation(s) for cities.
OpenAQ Countries API
The Countries API from OpenAQ — 6 operation(s) for countries.
OpenAQ Daily API
The Daily API from OpenAQ — 2 operation(s) for daily.
OpenAQ Days API
The Days API from OpenAQ — 5 operation(s) for days.
OpenAQ Flags API
The Flags API from OpenAQ — 2 operation(s) for flags.
OpenAQ Hourly API
The Hourly API from OpenAQ — 1 operation(s) for hourly.
OpenAQ Hours API
The Hours API from OpenAQ — 7 operation(s) for hours.
OpenAQ Instruments API
The Instruments API from OpenAQ — 3 operation(s) for instruments.
OpenAQ Latest API
The Latest API from OpenAQ — 6 operation(s) for latest.
OpenAQ Licenses API
The Licenses API from OpenAQ — 2 operation(s) for licenses.
OpenAQ Locations API
The Locations API from OpenAQ — 11 operation(s) for locations.
OpenAQ Manufacturers API
The Manufacturers API from OpenAQ — 3 operation(s) for manufacturers.
OpenAQ Measurements API
The Measurements API from OpenAQ — 5 operation(s) for measurements.
OpenAQ Monthly API
The Monthly API from OpenAQ — 2 operation(s) for monthly.
OpenAQ Owners API
The Owners API from OpenAQ — 2 operation(s) for owners.
OpenAQ Parameters API
The Parameters API from OpenAQ — 5 operation(s) for parameters.
OpenAQ Project API
The Project API from OpenAQ — 1 operation(s) for project.
OpenAQ Projects API
The Projects API from OpenAQ — 2 operation(s) for projects.
OpenAQ Providers API
The Providers API from OpenAQ — 2 operation(s) for providers.
OpenAQ Readme API
The Readme API from OpenAQ — 1 operation(s) for readme.
OpenAQ Sensor API
The Sensor API from OpenAQ — 1 operation(s) for sensor.
OpenAQ Sensors API
The Sensors API from OpenAQ — 19 operation(s) for sensors.
OpenAQ Slug API
The Slug API from OpenAQ — 1 operation(s) for slug.
OpenAQ Sources API
The Sources API from OpenAQ — 3 operation(s) for sources.
OpenAQ Summary API
The Summary API from OpenAQ — 1 operation(s) for summary.
OpenAQ Yearly API
The Yearly API from OpenAQ — 2 operation(s) for yearly.
OpenAQ Years API
The Years API from OpenAQ — 1 operation(s) for years.
Scroll within the panel for all 28 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
OpenAQ
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Openaq Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Openaq Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Openaq Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for OpenAQ — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/openaq · machine-readable index on apis.io