Plant hardiness zones for any coordinate on Earth.

coords.zone is an API that returns the plant hardiness zone for any GPS coordinate on Earth in a single HTTP GET. One stop for hardiness data anywhere: USDA zones globally, climate data, plus each supported country's own local zone system layered on top. No sign-up or API key required, and a generous free tier when you're ready to ship.

How do I get a hardiness zone for a coordinate?

curl "https://coords.zone/api/v1/zone?lat=48.14&lng=11.58"
{"usda_zone":"7b","local_zone":"Z7b","lat":48.14,"lng":11.58}

Zone and climate data is extracted from global climate data averages over 30 years - same as the USDA official hardiness system - but more up to date. Currently based on full-year data from 1996 through 2025.

Free tier limits and pricing →

How do I use it with an AI agent?

coords.zone is also an MCP server, so Claude, Cursor, and any other MCP client can look up zones and climate data on their own — no glue code, one line to connect.

claude mcp add --transport http coords-zone https://coords.zone/mcp

Set up the MCP server →

What you can build

USDA zones cover any coordinate on Earth. Six countries also get their own local zone layered on top — Australia, the UK, Sweden, Norway, Germany, and South Africa — returned alongside the USDA zone whenever a point falls inside one.

Garden & plant apps

Show users which plants will survive their winters. Drop in a map tap, get a zone, filter your plant catalog.

Plant nurseries & seed shops

Automatically tag products with compatible zones. Warn buyers before they order something that won't survive their climate.

Smart irrigation & sensors

Enrich device data with zone context. Drive seasonal watering schedules based on the actual hardiness zone of each installation.

Agricultural & research tools

Batch-process field coordinates, validate growing-region assumptions, or power zone-aware recommendation engines.

Is it used in production?

Yes. coords.zone was written for my own gardening app gardenhero.app and still serves it, against the same public endpoints documented here — no private API, no separate data path. That app is global, and several countries lean on their own local zone scale rather than USDA — an easy detail to miss until users outside the US turn up. The USDA-only APIs I found were priced past what one field in a garden app could justify, and none answered the local-zone question at all. So I built it, and pulled it out into an API anyone can call.

More on why it exists →

© 2026 coords.zone