Community. Driven. Weather. Data. | Always Ad-Free | Developer FriendlyChecking statusDiscord
Become a supporter
Sign in
DocsDevelopersReference

Terms for builders

The three clauses of the Terms of Service that decide whether what you are building is allowed.


The full text is at /terms. Three clauses decide whether what you are building is allowed:

  • Personal, educational and research use. The license covers those (§4.1). Reselling the feed, redistributing it for gain, or building a commercial service on top of it needs written permission first (§3). The endpoints being open is not that permission; ask first.
  • Attribute, and do not imply endorsement. NWS and NOAA data stays theirs: do not claim it as your own, do not present it as official government output, and do not imply NOAA or the NWS endorses what you built (§4.2, §3). The derived products (processed GLM, ML nowcasts, anything under focus) are ours, and are not official NWS products either. Credit both: NWS/NOAA for the alert, WxAlerts for the processing.
  • No EAS or WEA tones. You may not reproduce, transmit or simulate the WEA attention signal, the EAS Attention Signal or EAS header codes, or anything substantially similar, from API output, including as a notification sound (§3.1). This one is FCC rule, not house style.

The API Terms for keyed access and authenticated MQTT are Terms §20 and §21. The life-safety disclaimer that governs all of it is Terms §6.

View this page as Markdown

May we use Microsoft Clarity to see how pages are used (clicks, scrolling and replays of a visit, with anything you type hidden), plus a random ID linking that to crash reports? Only to find bugs and confusing screens. Never advertising, never sold.