Ambee (BYOK)
Read air quality, pollen and weather data for any coordinates or place, now, forecast and history, from Ambee with your own API key
Read aviation weather and airport data (METAR, TAF, PIREP, AIRMET/SIGMET, NOTAM, stations) with your own AVWX token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_stationnearest_stationssearch_stationsget_metarget_tafget_weather_summaryAVWX (BYOK) lets an AI assistant read your own AVWX data through the AVWX API with a key you supply (AVWX API token). Read-only: 10 tools (get_station, nearest_stations, search_stations, get_metar, get_taf, get_weather_summary, get_pireps, list_airsigmets, airsigmets_at_location, get_notams). 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 avwx.rest. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AVWX. AVWX and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the AVWX API (avwx.rest) with a BYOK key; documentation: https://avwx.docs.apiary.io/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
10 tools, grouped by job. Every one is read-only or compute-only.
https://byok-avwx.connectorbay.com/mcpThree ways in, the same 10 tools.
https://byok-avwx.connectorbay.com/mcpPOST https://byok-avwx.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-avwx.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at account.avwx.rest).AVWX (BYOK) lets an AI assistant read your own AVWX data through the AVWX API with a key you supply (AVWX API token). It is a hosted MCP server with 10 tools such as Get station, Nearest stations, Search stations, Get metar, Get taf, Get weather summary, published by Unify Dynamics LLC. It is independent and not affiliated with AVWX.
Add the MCP endpoint https://byok-avwx.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-avwx.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-avwx.json.
Yes: this is a bring-your-own-key connector. Create a AVWX API token at https://account.avwx.rest/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read air quality, pollen and weather data for any coordinates or place, now, forecast and history, from Ambee with your own API key
Look up airports, runways, service providers, weather, sun times and operational notes with your own aviowiki API token
Read hourly, quarter-day, daily and minute forecasts, severe weather alerts, daily indices and weather along a route with your own Azure Maps subscription key
Read aviation weather (METAR, TAF, G-AIRMET) and airport station data with your own CheckWX API key
Read your Davis WeatherLink weather stations with current conditions, historic archive records, sensors and evapotranspiration using your own API key and secret
Read Danish Meteorological Institute weather station lists, observations and climate statistics for Denmark and Greenland with your own API key
https://byok-avwx.connectorbay.com/mcpPOST https://byok-avwx.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-avwx.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-avwx.connectorbay.com/health · Tool schemas: https://byok-avwx.connectorbay.com/tools.jsonAVWX (BYOK) lets an AI assistant read your own AVWX data through the AVWX API with a key you supply (AVWX API token). Read-only: 10 tools (get_station, nearest_stations, search_stations, get_metar, get_taf, get_weather_summary, get_pireps, list_airsigmets, airsigmets_at_location, get_notams). 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 avwx.rest. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AVWX. AVWX 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:
get_station: Get an airport or weather station by ICAO or IATA code: name, city, coordinates, elevation, type and runways.nearest_stations: List the stations nearest to a coordinate pair, with distance; reporting airports only by default. Free plans may request at most 10.search_stations: Search stations by text matching ICAO, IATA, name, city or state; reporting airports only by default.get_metar: Get the latest METAR observation for a station or coordinate: flight rules, wind, visibility, temperature, dew point, altimeter, clouds and the raw report.get_taf: Get the latest TAF forecast for a station or coordinate, with each forecast period's flight rules, wind, visibility and clouds.get_weather_summary: Get a short flight-conditions summary for a station: current METAR flight rules, visibility and ceiling plus the TAF forecast periods.get_pireps: Get pilot reports (PIREPs) within about 200 miles of a station or coordinate: aircraft, altitude, turbulence, icing and raw text.list_airsigmets: List all current global AIRMET and SIGMET advisories with bulletin, issuer, area, validity times and body text.airsigmets_at_location: List AIRMET and SIGMET advisories whose boundary polygon contains a station or coordinate.get_notams: Get NOTAMs (notices to airmen) for an airport or within a distance of a coordinate; some may be served up to 10 days after they end.You bring your own AVWX AVWX API token (https://account.avwx.rest/). 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 avwx.rest 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.
Live from the AVWX API (avwx.rest) with a BYOK key; documentation: https://avwx.docs.apiary.io/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by AVWX. AVWX 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 AVWX account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What AVWX (BYOK) is. AVWX (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own AVWX data: Read aviation weather and airport data (METAR, TAF, PIREP, AIRMET/SIGMET, NOTAM, stations) with your own AVWX token. You bring your own AVWX AVWX API token; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one AVWX 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 avwx.rest, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If AVWX 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 AVWX receives. The request we make on your behalf, including the key and the arguments, under AVWX's own terms and privacy policy. AVWX acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer AVWX 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 AVWX 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. AVWX (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 AVWX at any time to end all access.
Children. AVWX (BYOK) is a general-audience service operated by the adult using the assistant, under AVWX's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the AVWX (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-avwx.connectorbay.com/mcphttps://byok-avwx.connectorbay.com/openapi.jsonWhen 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. AVWX (BYOK) never asks for them.