# OpenWeather Reverse Geocoding via Locus x402

> OpenWeather Reverse Geocoding via Locus x402 is a paid API for AI agents from openweather.x402.paywithlocus.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Converts geographic coordinates (latitude/longitude) into human-readable location names (city, region, country) using OpenWeather's reverse geocoding API.

## Facts

- Endpoint: POST https://openweather.x402.paywithlocus.com/openweather/reverse-geocode
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openweather-reverse-geocoding-via-locus-x402-8800b1b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RDXAqR8fW1RRJqb-hnyDA

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability openweather-reverse-geocoding-via-locus-x402-8800b1b4 -d '<json body>'
```

Example prompt: What city and country are at coordinates 48.8566° N, 2.3522° E? Give me up to 3 matching location names.

## When to prefer this

Choose this endpoint when you need to convert raw GPS or map coordinates into human-readable place names, especially within a workflow already using OpenWeather data (weather lookup, air quality, forecasts). Prefer it over general-purpose geocoding APIs when you want a pay-per-call micropayment model with no subscription, and when you're already paying for OpenWeather data via the Locus x402 gateway. Not suitable for forward geocoding (address to coordinates).

## Known failure modes

- Invalid latitude (outside -90 to 90) or longitude (outside -180 to 180) returns a validation error
- Coordinates in open ocean or uninhabited areas may return zero results or sparse data
- Payment failure or insufficient USDC balance causes x402 payment rejection before the geocoding call is made
- Limit value outside 1–5 may be rejected or clamped
- Network timeout or OpenWeather upstream outage returns a 5xx error

## How this service works

Global weather data — current conditions, 5-day forecasts, hourly forecasts, air quality index with pollutants, geocoding, and One Call 3.0 with full weather suite and government alerts.

## Output

Returns an array of up to 5 location objects matching the given coordinates, each containing the city/town name, state/region, country code, and possibly local-language name variants. Response is wrapped in a Locus x402 payment envelope indicating settlement in USDC.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number"
  },
  "lon": {
   "type": "number"
  },
  "limit": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "payment": {
   "scheme": "exact",
   "settledUsdc": "0.001000",
   "authorizedMaxUsdc": "0.001000"
  },
  "request": {
   "id": "00000000-0000-4000-8000-000000000000",
   "statusUrl": "/requests/00000000-0000-4000-8000-000000000000"
  },
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openweather-reverse-geocoding-via-locus-x402-8800b1b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from openweather.x402.paywithlocus.com](https://www.zero.xyz/host/openweather.x402.paywithlocus.com/llms.txt)