Pirate Weather vs Xweather Weather API

Pirate Weather

Named model sources and a documented priority order for every field. No SLA, and the terms call it best effort.

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.

Pirate Weather

1. Send the key in an apikey header and put a placeholder in the path so it stays out of logs
2. Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
3. Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
4. Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
5. Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day

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