Pricing
From your first call to production scale.
Every plan ships the same multi-source data and the same per-source attribution. You pay for volume, not for honesty.
Not ready to sign up? Try the API without a key.
Free
$0
forever
10,000 requests / month
- weather/point
- weather/hourly (24h)
- space-weather
Visible attribution required in your app
Get free keyHobby
Popular$9
per month
100,000 requests / month
- everything in Free
- weather/hourly (72h + pastHours)
- aviation/nearest
- flight-score
Commercial use OK
Start HobbyPro
$49
per month
500,000 requests / month
- everything in Hobby
- windProfile (upper-air)
- multi-source comparison
No required visible attribution
Start ProEnterprise
Contact us
annual
1M+ / month with SLA
- everything in Pro
- dedicated support
- custom thresholds
- SLA 99.5%
- VPC / on-prem proxy (optional)
Custom terms
Talk to us10 requests / second across all tiers
Questions worth answering before you commit
- What counts as a request?
- One call to any /v1 endpoint that returns data, including responses served from cache. Calls rejected with a 4xx or 5xx are not counted against your quota.
- What happens when I reach my monthly quota?
- Requests return 429 with the reset time in the response headers. Nothing is billed automatically and there is no overage charge, so a traffic spike cannot produce a surprise invoice.
- What does the attribution requirement mean in practice?
- On the free tier, name DroneInfo as the weather source somewhere a user of your application can see it. Pro and Enterprise remove that requirement. Attribution owed to the upstream agencies, such as the Met Office and Environment Canada, applies on every tier and is listed in the API documentation.
- Is the free tier permanent?
- Yes. It is a standing commitment rather than an introductory offer, and it exists because a decision-support tool nobody can afford to call is not much of a decision-support tool.
- Can I try the API before signing up?
- Yes. The demo endpoint takes no key at all and answers 20 requests per hour per IP against the live pipeline, not a fixture.