Xweather History And Roads (BYOK)

Xweather History And Roads (BYOK) — connector documentation

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

What Xweather History And Roads (BYOK) is for

Xweather History And Roads (BYOK) lets an AI assistant read your own Xweather History And Roads data through the Xweather History And Roads API with a key you supply (Xweather client id). Read-only: 8 tools (get_place, search_places, get_observation_summary, get_observation_archive, get_road_weather_conditions, get_road_weather_analytics, get_storm_report_summary, get_storm_cell_summary). 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 data.api.xweather.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xweather History And Roads. Xweather History And Roads 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:

• "What time zone and elevation does Minneapolis have?"
• "Which cities in Minnesota start with the letters Min?"
• "What was the daily weather summary at Minneapolis over the last week?"
• "What were the hourly weather observations at Chicago O'Hare on 2026-10-01?"
• "Will the roads be icy around Minneapolis tonight?"
• "What is the hydroplaning and fog risk on the roads around Seattle tonight?"

What it does

• get_place: Look up a place by name, coordinates, postal code or id: position, state, country, region, elevation, population, time zone, weather zones and county ids.
• search_places: Search the Xweather places database (cities, stations, airports, points of interest) with an advanced query, for example the largest cities of a state.
• get_observation_summary: Get daily summaries of the observations of the reporting stations near a place for a date range (up to one month per call, back to 2011): temperature range, humidity, pressure, wind, precipitation and weather.
• get_observation_archive: Get every archived observation of one past day from the stations near a place (back to 2011): temperature, humidity, pressure, wind, visibility, weather and precipitation.
• get_road_weather_conditions: Get the road weather forecast at a place (US, Canada, Europe, Japan, Australia, New Zealand): a green, yellow or red driving index, the road surface condition (dry, wet, snow, ice) and surface temperature, every 15 minutes for 2 hours then hourly for 24 hours. Counts as 5 accesses per call.
• get_road_weather_analytics: Get the full road weather forecast at a place: surface condition and temperature plus water film, snow and ice thickness and probabilities of truck rollover, hydroplaning, fog and blowing snow. Counts as 10 accesses per call.
• get_storm_report_summary: Summarise the US local storm reports that match a query and time range: how many reports, per type and per state, with maximum hail size or wind speed.
• get_storm_cell_summary: Summarise the current US storm cells within a radius of a place: how many, with hail probability and size, tornadic signatures, rotation, cell top and intensity.

BYOK key

You bring your own Xweather History And Roads Xweather client id (https://www.xweather.com/account/apps). 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 data.api.xweather.com 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.

Notices

Xweather data requires attribution to Vaisala Xweather and the listed data sources (NWS, NOAA and others) as described in the Xweather attribution guide.

Data sources

• https://www.xweather.com/docs/weather-api/endpoints (the API this connector calls, with a BYOK key)

Live from the Xweather History And Roads API (data.api.xweather.com) with a BYOK key; documentation: https://www.xweather.com/docs/weather-api/endpoints. 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 Xweather History And Roads. Xweather History And Roads 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 Xweather History And Roads account.

Built for: Worldwide. Languages: English.

Xweather History And Roads (BYOK) — Privacy Policy

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

What Xweather History And Roads (BYOK) is. Xweather History And Roads (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Xweather History And Roads data: Read place lookups, daily observation summaries, archived station observations, road weather forecasts and storm report and storm cell summaries from Xweather with your own client id and secret. You bring your own Xweather History And Roads Xweather client id; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Xweather History And Roads 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 data.api.xweather.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Xweather History And Roads 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 Xweather History And Roads receives. The request we make on your behalf, including the key and the arguments, under Xweather History And Roads's own terms and privacy policy. Xweather History And Roads acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Xweather History And Roads 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 Xweather History And Roads 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. Xweather History And Roads (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 Xweather History And Roads at any time to end all access.

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

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

Xweather History And Roads (BYOK) — Terms of Service

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

1. The Service. Xweather History And Roads (BYOK) provides: Read place lookups, daily observation summaries, archived station observations, road weather forecasts and storm report and storm cell summaries from Xweather with your own client id and secret. 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 Xweather History And Roads credentials and only access data you are allowed to access. Xweather History And Roads's terms apply to your use of Xweather History And Roads; 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 Xweather History And Roads. Xweather History And Roads 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 Xweather History And Roads returns, lightly trimmed; it may be incomplete, delayed or changed by Xweather History And Roads. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Xweather History And Roads 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 Xweather History And Roads'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; Xweather History And Roads 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 Xweather History And Roads 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 Xweather History And Roads 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-xweather-history-roads

Xweather History And Roads (BYOK) support

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

• MCP endpoint: https://byok-xweather-history-roads.connectorbay.com/mcp
• REST API: https://byok-xweather-history-roads.connectorbay.com/openapi.json
• Live status: https://byok-xweather-history-roads.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. Xweather History And Roads (BYOK) never asks for them.