A credit does not measure a request, it measures what the request reads. A forecast costs one; ten years of degree days cost twelve. The counter resets on the 1st of each month.
What you ask for
Credits
Forecast, current conditions, air quality
1
Degree days (HDD/CDD)+ 1 per whole year past the first
2
Climate series, daily or monthly+ 1 per whole year past the first
2
Climate normals
3
Climate summary for a place+ 1 per whole year past the first
3
Finding a place by name
Included
The same call in CSV costs 4 times its JSON price.
Common questions
Why credits rather than requests?
A city forecast is a cache read; ten years of degree days across five hundred cities is not. Billing the request would price both the same, which means overcharging the first.
Do unused credits roll over?
No. Your counter runs from the day you subscribed to the same day the next month — the very period Stripe invoices — and starts again whole each time. What is left at the end is not carried over.
What happens when my credits run out?
The API answers 429 with the code quota_exceeded and the reset date. Nothing is billed as overage, no key is revoked, and you can change plan at any time from your account.
Does looking up a place cost credits?
No. Resolving “Brussels” to coordinates is a prerequisite of all three products, not a fourth product: billing that step would tax what you already bought. It has its own ceiling, at 5 times your monthly quota.
What happens if a payment fails?
Service continues for 14 days. A card expires on a Friday evening; cutting a production integration before a human can react helps nobody.
Can I withdraw?
Yes, within 14 days, unless you expressly waived that right at payment — which we ask for explicitly, because the service starts immediately.