OpenWeather One Call API vs Xweather Weather API

OpenWeather One Call API

1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.

Xweather Weather API

A public OpenAPI file with 236 operations, a hosted MCP server in the official registry and a free tier of 15,000 accesses a month suit agents. REST credentials travel only in the query string, per-minute limits are unpublished, and the group terms bar commercial use of free plans and passing data to third parties unless a service description allows it.

OpenWeather One Call API

1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once
2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance
3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop
4. Pass units=metric. The default is Kelvin
5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses

Xweather Weather API

1. Check success and error.code on every response. Application errors such as invalid_location return HTTP 200 with success false
2. Send fields, limit and plimit. The docs put a 15-day hourly forecast at about 600 KB, and about 25 KB with three fields
3. Read X-Cost-Tokens after each call. Cost is the endpoint multiplier times the intervals requested, so narrow from and to
4. For MCP, send Authorization: Bearer <client_id>_<client_secret> and avoid the api_key query parameter, which puts the secret in the URL
5. Add include_tags or include_tools to the MCP URL to load only the tool groups the task needs
6. On 429 read Retry-After and the X-RateLimit-Reset-* headers. maxhits_min clears at the next minute, maxhits at the period reset