AirQo (BYOK)

AirQo (BYOK) — connector documentation

• MCP endpoint: https://byok-airqo.connectorbay.com/mcp
• REST API: POST https://byok-airqo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-airqo.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own AirQo AirQo API access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-airqo.connectorbay.com/health · Tool schemas: https://byok-airqo.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-airqo · agent@connectorbay.com

What AirQo (BYOK) is for

AirQo (BYOK) lets an AI assistant read your own AirQo data through the AirQo API with a key you supply (AirQo API access token). Read-only: 12 tools (list_grids, list_countries, list_sites, get_site, find_nearest_sites, list_devices, get_recent_grid_measurements, get_recent_cohort_measurements, get_daily_forecast, list_coverage_countries, list_country_monitors, get_coverage_impact). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.airqo.net. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AirQo. AirQo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which cities does AirQo monitor air quality in?"
• "In which countries does AirQo have air quality monitors?"
• "List AirQo air quality monitoring sites"
• "Show details of monitoring site 64f7b3e8c9d25a0013f2d456"
• "Which AirQo monitors are within 5 km of 0.3476, 32.5825?"
• "List AirQo monitoring devices"

What it does

• list_grids: List the public AirQo grids (city and administrative-area groupings of monitoring sites) with their id, name, admin level and network.
• list_countries: List the countries where AirQo has air quality monitoring coverage.
• list_sites: List public monitoring sites with name, coordinates, network and online status.
• get_site: Get full details of one monitoring site: coordinates, administrative context and current online status.
• find_nearest_sites: Find monitoring sites near a coordinate within a radius, closest first, with distance in km (site coordinates are offset by up to about 0.5 km for privacy).
• list_devices: List public sensor devices with category (lowcost, bam, gas), deployment status, site and last activity.
• get_recent_grid_measurements: Get the latest hourly calibrated PM2.5 and PM10 measurements (about the last 7 days) from all public sites of a city grid.
• get_recent_cohort_measurements: Get hourly calibrated PM2.5 and PM10 measurements (about the last 7 days on the Free plan) for a cohort of devices; use the cohort id airqo-public for a network-wide sample.
• get_daily_forecast: Get the 7-day PM2.5 forecast for one site with AQI category, health advice and weather context (needs the Premium plan).
• list_coverage_countries: Pan-African registry of air quality monitors from any operator: list countries with monitor counts by type (reference or low-cost) and status.
• list_country_monitors: List the monitors of one African country from the registry with type, status, operator, equipment, pollutants, resolution and uptime.
• get_coverage_impact: Get aggregate registry statistics: total monitors by type and status, number of cities and countries covered and estimated population reached.

BYOK key

You bring your own AirQo AirQo API access token (https://platform.airqo.net/docs/api/getting-started/authentication/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.airqo.net over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://platform.airqo.net/docs/api/intro/ (the API this connector calls, with a BYOK key)

Live from the AirQo API (api.airqo.net) with a BYOK key; documentation: https://platform.airqo.net/docs/api/intro/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AirQo. AirQo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your AirQo account.

Built for: Worldwide. Languages: English.

AirQo (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What AirQo (BYOK) is. AirQo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own AirQo data: Read air quality (PM2.5, PM10) measurements, monitoring sites, devices and a pan-African monitor registry from the AirQo network with your own API token. You bring your own AirQo AirQo API access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one AirQo call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.airqo.net, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If AirQo rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What AirQo receives. The request we make on your behalf, including the key and the arguments, under AirQo's own terms and privacy policy. AirQo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer AirQo gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your AirQo data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. AirQo (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at AirQo at any time to end all access.

Children. AirQo (BYOK) is a general-audience service operated by the adult using the assistant, under AirQo's own age rules.

Changes. We will post changes here with a new effective date.

AirQo (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the AirQo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. AirQo (BYOK) provides: Read air quality (PM2.5, PM10) measurements, monitoring sites, devices and a pan-African monitor registry from the AirQo network with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own AirQo credentials and only access data you are allowed to access. AirQo's terms apply to your use of AirQo; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AirQo. AirQo and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data AirQo returns, lightly trimmed; it may be incomplete, delayed or changed by AirQo. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your AirQo account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent AirQo's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; AirQo may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your AirQo key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action AirQo takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-airqo

AirQo (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-airqo.connectorbay.com/mcp
• REST API: https://byok-airqo.connectorbay.com/openapi.json
• Live status: https://byok-airqo.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. AirQo (BYOK) never asks for them.