Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign up for an Aeroqual Cloud subscription tier that includes API access, since API availability depends on the subscription level.
Register Aeroqual instruments (e.g., Dust Sentry monitors reporting PM1, PM2.5, PM4, PM10, and TSP) to the Cloud account for centralized data collection.
Use the API to plug in third-party devices/sensors alongside native Aeroqual instruments so all readings appear in one dashboard.
Configure auto-forwarding of data via email or FTP as an alternative/complement to API polling, if downstream systems prefer push delivery.
Query historical PM fraction data through the API for compliance reporting, keeping in mind the platform is built to handle high-volume streams (millions of datapoints per day).
Known gotchas
API access is gated by subscription tier — confirm the account plan includes API access before building an integration around it.
Aeroqual's public materials do not document a specific named third-party sensor brand integration; treat "integrate any third-party device" as a general capability to verify against the specific sensor model, not a confirmed named partnership.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?