> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avrxt.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Location and weather reads

> Validated geocoding and forecast queries passed through the AVRXT Worker to Open-Meteo.

## Find a location

```bash theme={null}
curl --get https://api.avrxt.dev/v1/geo/search --data-urlencode "name=London" --data-urlencode "count=5" --data-urlencode "language=en"
```

`name` is required and limited to 120 characters. `count` is clamped to 1–10, defaulting to 5. An optional `language` uses two letters. The response follows the upstream geocoding service’s JSON.

## Read a forecast

```bash theme={null}
curl --get https://api.avrxt.dev/v1/geo/forecast --data-urlencode "latitude=51.5074" --data-urlencode "longitude=-0.1278" --data-urlencode "current=temperature_2m" --data-urlencode "timezone=auto"
```

Always send explicit numeric coordinates: latitude −90 to 90 and longitude −180 to 180. The adapter forwards validated `current`, `hourly`, `daily`, `timezone`, `forecast_days`, and `past_days` parameters. Oversized or unsupported optional values are not forwarded.

## Freshness and limits

Location searches may be cached for up to one hour and forecasts for up to 15 minutes, subject to a shorter existing response policy. Treat results as informational, not an operational aviation or safety forecast.

## Related reading

* [Origin rules](https://docs.avrxt.dev/api-reference/cors.md)
* [Error handling](https://docs.avrxt.dev/api-reference/errors.md)
* [Cache policy](https://docs.avrxt.dev/maintaining/caching.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.