Per-call charges

Apart from the fixed 'per-call' charge, the following are only added when data is not available from our cache and has to be fetched direct from the source... if the data is already available from our cache then there is no charge for the source concerned.

per-call: 1

met.no: 1

darksky.net: 4

pirateweather.net: 2

wwo.com: 3

noaa.gov: 1

openweathermap.org: 1

accuweather.com: 5

metoffice.gov.uk: 1

metoffice.com: 3

bom.gov.au: 1

smhi.se: 1

dwd.de|mosmix: 1

dwd.de|icon-eu: 2

dwd.de|icon-d2: 2

dwd.de|cosmo-d2: 2

dwd.de|icon: 2

weather.com: 5

aerisweather.com: 2

weatherbit.io: 3

meteogroup.com: 5

here.com: 1

openmeteo.com: 1

foreca.com: 5

visualcrossing.com: 4

knmi.nl: 2

tomorrow.io: 4

fmi.fi|hirlam: 1

fmi.fi|harmonie: 1

meteofrance.fr|arome: 2

meteofrance.fr|arpege-europe: 2

meteofrance.fr|arpege-global: 2

tide: 3

alerts: 3

For example, if data from met.no, darksky.net and wwo.com is used in the requested meteogram, then the API call cost incurred will be between (1 + 0 + 0 + 0 = 1) and (1 + 1 + 4 + 3 = 9), depending on whether or not the relevant data is fetched from local cache. It will often be at the lower end of this range. As another example, for a simple chart drawing data from just met.no, the API call cost incurred will be between (1 + 0 = 1) and (1 + 1 = 2).