canonical: https://jentic.com/apis/wirefreethought.com/geodb-cities-api

# Wirefreethought GeoDB Cities API

GeoDB Cities is a comprehensive API for getting global city, region, and country data. It provides geolocation data including city populations, coordinates, currency info, and locale data. Data is sourced from WikiData. The API exposes 11 endpoints secured with apiKey authentication.

## For AI agents

Programmatically find cities, get city details. Covers 11 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Find cities
- Get city details
- Integrate GeoDB Cities API into automated workflows
- Query and filter GeoDB Cities API records by parameters
- Monitor GeoDB Cities API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the GeoDB Cities API to perform maps geolocation operations programmatically. The API provides 11 endpoints covering core functionality including find cities, get city details, find nearby cities.

Example prompt: Call GET `/geo/cities` to find cities

### Automated Geo Management

Automate geo operations by combining multiple GeoDB Cities API endpoints. Agents can get city details and then find nearby cities in a single workflow.

Example prompt: Call GET `/geo/cities/{cityId}` to get city details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call GeoDB Cities API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'find cities', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/geo/cities` | Find cities |
| GET | `/geo/cities/{cityId}` | Get city details |
| GET | `/geo/cities/{cityId}/nearbyCities` | Find nearby cities |
| GET | `/geo/cities/{cityId}/distance` | Get city distance |
| GET | `/geo/countries` | Find countries |
| GET | `/geo/countries/{countryId}` | Get country details |
| GET | `/geo/countries/{countryId}/regions` | Find country regions |
| GET | `/geo/adminDivisions` | Find administrative divisions |

## Key resources

- **Geo** — Geographic data endpoints for cities, countries, and regions
- **Locale** — Locale-related data including currencies and locales

## Why Jentic

- **Setup:** Wiring the GeoDB Cities API by hand means choosing between the RapidAPI host and the free-tier wirefreethought host, sending the X-RapidAPI-Key header, and paging through cities and countries yourself. Through Jentic you install once, import the GeoDB Cities API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** GeoDB puts the city and country ids in the URL path (`/geo/cities/{cityId}`, `/geo/countries/{countryId}`), so a rule can pin your agent to reading one city or country. You choose the operations it may call, so anything beyond the lookups you allow is not included unless you add it.
- **Credential handling:** Your GeoDB API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find cities near a location' or 'get the distance between two cities', and Jentic returns the matching GeoDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the GeoDB Cities API use?

The GeoDB Cities API uses an API key passed in the `X-RapidAPI-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I find cities with the GeoDB Cities API?

Yes. Use the GET `/geo/cities` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the GeoDB Cities API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I find cities through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'find cities'. Jentic returns the matching GeoDB Cities API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the GeoDB Cities API have?

The GeoDB Cities API exposes 11 endpoints covering geo, locale operations.

### Can I limit what my agent is allowed to do with the GeoDB Cities API?

Yes. Jentic One is self-hosted by you, so your own rules decide which GeoDB operations the agent may call and which stored credentials it may use. Because GeoDB puts the city and country ids in the URL path (GET `/geo/cities/{cityId}`, GET `/geo/countries/{countryId}`), you can pin the agent to reading a single city or country rather than browsing everything. You choose the operations it may run, so anything beyond the lookups you allow, such as finding nearby cities or listing country regions, stays off limits until you add it.