# x402.forgemesh.io City Lat/Long Lookup

> x402.forgemesh.io City Lat/Long Lookup is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Resolves a place name to geographic coordinates (latitude/longitude), plus country, region, population, elevation, and timezone for up to five closest matches

## Facts

- Endpoint: POST https://x402.forgemesh.io/city-lat-long-lookup
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-forgemesh-io-city-lat-long-lookup-f82311b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aVRSYWRe2xa75Bs5hAb8p

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 x402-forgemesh-io-city-lat-long-lookup-f82311b3 -d '<json body>'
```

Example prompt: What are the latitude and longitude coordinates for Austin, Texas? I need the timezone and country too.

## When to prefer this

Use this endpoint when you have a human-readable place name and need to resolve it to coordinates before calling any geospatial API (weather, earthquakes, ocean data, etc.) — especially when you also need ancillary metadata like timezone, elevation, or population for the same lookup cost. Prefer it as a geocoding bridge step in multi-API workflows.

## Known failure modes

- Unrecognized or misspelled city name returns empty or low-confidence results
- Ambiguous place names may return unintended matches (e.g. 'Springfield' matches many cities)
- Very small or informal place names may not appear in the underlying dataset
- Network or payment failure returns a 402 or 5xx error

## How this service works

Resolve a place name to its geographic coordinates, along with country, region, population, elevation, and local timezone for the closest five matches. Built as the bridge between human-readable locations and any API that only accepts latitude/longitude — geocode once, reuse everywhere.

## Output

Returns up to five candidate matches for the given place name, each with latitude, longitude, country, region, population, elevation, and local timezone — enabling downstream APIs that require coordinate inputs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "city": {
   "type": "string",
   "description": "place name, e.g. Houston"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "results": [
    {
     "name": "Houston",
     "latitude": 29.76328,
     "timezone": "America/Chicago",
     "longitude": -95.36327,
     "population": 2296224,
     "country_code": "US"
    }
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-forgemesh-io-city-lat-long-lookup-f82311b3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)