API terms of use

A plain-language summary of how the API may be used. It supplements — and is governed by — the full terms at weatherfiles.com.

Acceptable use

• Use the API within your plan's quota and rate limits. Don't try to circumvent them with multiple accounts or tokens.
• Back off on 429 (honour Retry-After); don't hammer endpoints in tight loops.
• Use slices for repeated downloads rather than re-issuing identical one-shot requests.
• Don't use the API to attack, probe, or degrade the service.

Data & redistribution

GRIBs are derived from third-party numerical weather models, each carrying its source provider's licence. WeatherFiles slices them for your own navigation, forecasting and applications. Do not bulk-mirror the API or re-publish raw model data as a competing feed. If you're unsure whether your use is allowed, ask first.

Service level

• Best-effort, no SLA in v1. Availability and model freshness mirror the website.
• No uptime guarantee or compensation for downtime. Build retries and graceful degradation into your client.

Tokens

• You're responsible for keeping your tokens secret and for activity under them.
• We may revoke a token or suspend access for abuse or terms violations.

Questions about acceptable use? Get in touch.