Mashape GeoDB Cities API
64
AI ReadinessAI-Aware (B)64/100
Community OpenAPI document · agent-readyMaps GeolocationPlaces SearchapiKey39 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Search cities, countries, regions, and administrative divisions with population, coordinates, and nearby-place lookups for autocomplete and store-locator use cases.
Use for: Find cities in Germany with more than 500,000 residents, Get the population and coordinates for the city named 'Lyon', List all administrative divisions in California, Find every populated place within 50km of latitude 40.71, longitude -74.00
Not supported: Does not handle full-address geocoding, routing, or map tile rendering - use for city, country, and administrative-division lookups only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmashape.com%2Fgeodb-cities" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmashape.com%2Fgeodb-cities" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
Retrieve the local time and timezone for a given city
Convert between place IDs and Wikidata IDs
Use Cases
Patterns agents use GeoDB Cities 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
GET
/geo/adminDivisions
Search administrative divisions
GET
/geo/adminDivisions/{divisionId}/nearbyCities
Cities near an administrative division
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
GeoDB Cities API
- AI-Aware (B)64/100
73
Foundational Compliance61
Developer Experience & Jentic Compatibility54
AI-Readiness & Agent Experience94
Agent Usability50
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
90%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
16%
Example Density
How richly the API is illustrated with examples.
76%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
54
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
65%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GeoDB Cities API by hand means registering on RapidAPI, sending the X-RapidAPI-Key header on every call, and pointing at the wft-geo-db.p.rapidapi.com host. Through Jentic you install once, import the GeoDB Cities API from the API Directory, store the RapidAPI key once, and your agent calls it.
Permission scoping
GeoDB puts the resource id in the URL path (/geo/cities/{cityId}, /geo/countries/{countryId}), so a rule can pin your agent to one city or country and its nearby lookups. You choose the operations it may call, and since this surface is read-only, it fetches place data without any write access unless you add it.
Credential isolation
Your RapidAPI key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find a city by name' or 'list nearby cities', and Jentic returns the matching GeoDB operation with its query schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic 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.
FAQs
Specific to using GeoDB Cities 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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the GeoDB Cities API?
Yes. Because you self-host Jentic One, your own rules decide which GeoDB operations and credentials the agent may use, so you can allow only the city and country lookups it needs, such as GET /geo/cities and GET /geo/countries. Since GeoDB puts the resource id in the URL path (for example /geo/cities/{cityId} or /geo/countries/{countryId}), you can pin the agent to a single city or country and its nearby lookups. The whole surface is read-only, so the agent fetches place data without any write access.
GET STARTED