Agentic Fabriq
Ambee
DATA · DATA & ANALYTICS
Air quality, pollen, weather, and wildfire data for any place they ask about.
Connecting Ambee in practice
Ambee splits "you are going too fast" from "you have used up your plan" into two different status codes — 429 for rate limit and 422 for Quota exceeded — and adds 403 when the key simply is not licensed for that dataset. Three quite different problems all present as a failed call, and the fix differs each time.
Worth knowing
- 403 means "the API key doesn’t have the permissions" for that product, so a key that works against Air Quality can fail against Pollen with no change in how it is used.
- History endpoints require `from` and `to` in the exact format "YYYY-MM-DD hh:mm:ss", not ISO 8601, so a naive timestamp serialisation is rejected.
- aqiStandard defaults to EPA, so an agent reporting air quality outside the United States reports it on the wrong scale unless it explicitly passes IN, UK, CN or CA.
- Ambee publishes no numeric per-plan rate limits in the API documentation, only the 429 and 422 codes and advice to reduce frequency or upgrade, so the ceiling has to be measured.
Checked against Ambee API overview (2026-09-29), Ambee Air Quality API (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Ambee behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.