GeoDB Cities API

Name: GeoDB Cities API API
Brand: GeoDB Cities API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey39 EndpointsREST

For Agents

Search cities, countries, regions, and administrative divisions with population, coordinates, and nearby-place lookups for autocomplete and store-locator use cases.

Connect the GeoDB Cities API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GeoDB Cities API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GeoDB Cities API API.

Search cities filtered by name prefix, country, minimum population, and radius

Look up details for a specific city including population and coordinates

List countries and the administrative divisions within each

Find nearby cities or administrative divisions within a distance from a point

GET STARTED

Start building with GeoDB Cities API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for GeoDB Cities API, keeping it validated and agent-ready.

GeoDB Cities API is a curated geographic database covering countries, regions, administrative divisions, populated places, and time zones, distributed via the RapidAPI marketplace under the wft-geo-db host. Each city record carries population, latitude/longitude, elevation, and Wikidata IDs, with nearby-city and distance-radius search built in. The API is intended for autocomplete UIs, store-locator features, and AI agents that need to look up places without licensing a full GIS dataset. Authentication uses a RapidAPI key passed as the `X-RapidAPI-Key` header.

Use Cases

Patterns agents use GeoDB Cities API API for, with concrete tasks.

★ City Autocomplete in Sign-up Forms

Web and mobile sign-up flows often need a city autocomplete that returns the right city the moment the user starts typing. GeoDB Cities supports prefix search with country and minimum-population filters so you can show only the cities relevant to your audience and avoid surfacing tiny villages. A typical autocomplete fires after 3 characters and returns the top 5 matches.

Call `GET /geo/cities?namePrefix=San&minPopulation=100000&limit=5` and render the returned city names in the dropdown.

Store Locator Nearby Search

Retailers powering 'stores near me' features need to map a user's city to nearby populated places to determine which store catchment to query. GeoDB exposes nearby-cities and radius search around a coordinate so the locator can resolve the user's input city to a list of neighbouring cities with population thresholds.

Call `GET /geo/locations/{locationId}/nearbyCities?radius=50&limit=20` and feed the returned city IDs into the store catchment query.

Travel App City Browser

Travel and itinerary apps let users browse cities by country and admin region. GeoDB's hierarchical endpoints (countries → admin divisions → cities) return the structured navigation tree, with each city carrying population, elevation, and a Wikidata ID for cross-linking to other data sources like images or articles.

Call `GET /geo/countries/{countryCode}/regions/{regionCode}/cities` to render the city list under a chosen region.

AI Agent Location Resolution

An AI travel or logistics agent often needs to resolve a freeform city mention to a canonical place ID with coordinates. Jentic exposes GeoDB's prefix and radius search behind intent-based discovery, and stores the RapidAPI key in the vault so the agent never embeds it in prompts.

Search Jentic for 'find city by name', load the GeoDB `/geo/cities` schema, and execute it with namePrefix='Lyon' to resolve the canonical city record.

Key Endpoints

39 endpoints — geodb cities api is a curated geographic database covering countries, regions, administrative divisions, populated places, and time zones, distributed via the rapidapi marketplace under the wft-geo-db host.

METHOD

PATH

DESCRIPTION

GET

/geo/cities

Search cities with prefix, country, and population filters

GET

/geo/cities/{cityId}

Fetch a specific city's details

GET

/geo/cities/{cityId}/dateTime

Get local date and time for a city

GET

/geo/countries

List countries

GET

/geo/countries/{countryId}

Fetch a specific country

GET

/geo/adminDivisions

Search administrative divisions

GET

/geo/adminDivisions/{divisionId}/nearbyCities

Cities near an administrative division

GET

/geo/cities

Search cities with prefix, country, and population filters

GET

/geo/cities/{cityId}

Fetch a specific city's details

GET

/geo/cities/{cityId}/dateTime

Get local date and time for a city

GET

/geo/countries

List countries

GET

/geo/countries/{countryId}

Fetch a specific country

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The RapidAPI `X-RapidAPI-Key` is stored encrypted in the Jentic vault (MAXsystem) and applied to the request header at execution time. Agents receive scoped session references — the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'find city by name' or 'list nearby cities') and Jentic returns the matching GeoDB operation with its query schema.

Time to first call

Direct GeoDB integration: 2-3 hours for RapidAPI account setup, key wiring, and pagination. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Geocodio API

Geocodio focuses on US/Canada address geocoding with rich enrichment fields.

Choose Geocodio when the input is a street address rather than a city name and you need US Census enrichment.

Alternative

LocationIQ API

LocationIQ provides global forward and reverse geocoding plus map tiles.

Choose LocationIQ when you need full address geocoding or map rendering rather than a city catalogue.

Alternative

PositionStack API

PositionStack is a forward and reverse geocoding API with global coverage.

Choose PositionStack when you need lat/long resolution from address strings rather than city-level metadata.

Complementary

GeoNames API

GeoNames is a free geographic database with extensive feature codes and translations.

Pair GeoNames when you need feature-code level data (mountains, lakes, postal codes) beyond GeoDB's populated-place focus.

FAQs

Specific to using GeoDB Cities API API through Jentic.

What authentication does the GeoDB Cities API use?

GeoDB Cities is distributed via RapidAPI and authenticates with the `X-RapidAPI-Key` header tied to your RapidAPI account subscription. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at execution time.

Can I search cities by minimum population with the GeoDB Cities API?

Yes. `GET /geo/cities` accepts `minPopulation` and `maxPopulation` query parameters along with `namePrefix` and `countryIds`, so you can return, for example, only cities above 500,000 people that match a prefix.

What are the rate limits for the GeoDB Cities API?

Rate limits depend on the RapidAPI plan tier you subscribe to. The free tier is typically 1 request per second with a daily quota, while paid plans raise both the per-second and monthly quotas. RapidAPI returns standard quota headers on each response.

Can I find cities near a specific coordinate with the GeoDB Cities API?

Yes. Use `GET /geo/locations/{locationId}/nearbyCities` or the location-coordinate variants to find populated places within a configurable radius, with optional minimum-population and country filters.

How do I look up a city through Jentic?

Run `pip install jentic`, then use Jentic's search with the query 'find city by name'. Jentic loads the `/geo/cities` operation schema and your agent executes it with the chosen `namePrefix` and population filter — the RapidAPI key is applied automatically.

Does the GeoDB Cities API include Wikidata IDs?

Yes. Each city, region, and country record includes a `wikiDataId` field, letting you cross-reference GeoDB results with Wikidata-linked datasets such as images, descriptions, or related entities.