Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Poll a fixed indoor CO2 monitor's latest reading (e.g., Kaiterra Sensedge via its /v1/devices/{deviceId} endpoint) on a regular interval such as every 5-15 minutes, since the public API is pull-based, not webhook-based.
Compare the returned CO2 ppm value against a fixed action threshold (commonly referenced informally around 1,000 ppm per ASHRAE 62.1 ventilation guidance) to flag under-ventilated spaces.
Use a sustained-CO2 alert as a secondary trigger prompting an HVAC/ventilation check alongside — not instead of — a dedicated radon monitor reading, since poor ventilation is a shared underlying condition for both CO2 buildup and radon accumulation.
Log the CO2 stream and any co-located radon monitor's stream on a shared timeline so facilities staff can see whether a ventilation change correlates with a radon-level change.
Rate-limit and cache polling per Kaiterra's documented API key usage guidance to avoid hitting per-key request limits when monitoring many spaces.
Known gotchas
CO2 concentration is a ventilation proxy, not a radon proxy — a low CO2 reading does not mean radon is safe, and a high reading does not confirm elevated radon.
No vendor in this space (Kaiterra, Awair, uHoo, Aranet, Qingping) publishes a combined CO2+radon single-API feed — you must run two separate device integrations and join the data yourself.
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?