canonical: https://jentic.com/apis/mon-voyage-pas-cher.com/mon-voyage-pas-cher-public-api # Mon-voyage-pas-cher.com Public API The Mon-voyage-pas-cher.com Public API answers geographic reference questions for travel planning. It lists airports, continents, and countries, finds cities from coordinates or from a text query, and returns the significant cities in an area. It also computes the distance between points, returns ground elevation, resolves a timezone, and gives sun position data. The data endpoints read an x-api-key header, while the OPTIONS handlers need no credential and exist for browser preflight. ## For AI agents Look up travel geography: list airports and countries, find cities from coordinates or text, and compute distance, elevation, timezone, and sun position for a location. ## Scope Serves geographic reference data for travel planning. Does not book flights or hotels, process payments, or manage user accounts. ## Capabilities - List airports and browse continents and countries - Find cities from a latitude and longitude, or from a text query - Return the significant cities for an area - Compute the distance between two points - Return ground elevation and the timezone for a location - Return sun position data for a place and time ## Use cases ### Agent Trip Geography A travel-planning assistant can resolve the geography behind a request before it books anything. The agent finds the cities near a coordinate, lists nearby airports, and computes the distance to each, so a request like 'what airports are near here' is answered from live reference data rather than the model's memory. Example prompt: Find the cities near a coordinate and list the airports serving them with distances ### Location Context Enrichment An itinerary agent can attach context to each stop: its timezone, elevation, and the country it sits in. It calls the timezone, elevation, and country endpoints for each coordinate, reads back the values, and enriches the itinerary, so each stop carries accurate local context without a human filling it in. Example prompt: For each stop, resolve the timezone, elevation, and country from its coordinates ### Daylight-Aware Planning A planning agent can schedule activities around daylight using the sun position data. It resolves the city and timezone for a location, then reads sun positions to know when it is light, so an outdoor plan is built around real daylight rather than a fixed assumption. Example prompt: Resolve a location's timezone and sun positions to schedule activities within daylight ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/airports` | List airports | | GET | `/cities/findcitiesfromlatlong` | Find cities from a coordinate | | GET | `/cities/findcitiesfromtext` | Find cities from a text query | | GET | `/distance` | Compute distance between points | | GET | `/elevation` | Return elevation at a coordinate | | GET | `/timezone` | Resolve the timezone for a location | ## Key resources - **Places** — Airports, continents, countries, and city lookups by coordinate or text - **Measurements** — Distance between points and ground elevation at a coordinate - **Time and sun** — Timezone resolution and sun position data for a location ## Why Jentic - **Setup:** Wiring the Mon-voyage-pas-cher.com Public API by hand means adding the x-api-key header to each data call and handling its many differently shaped geographic endpoints. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls the airport, city, and measurement operations. - **Permission scoping:** The API's operations are read-only geographic lookups, so a rule can allow only the ones your agent needs, such as airports and cities, and leave distance, elevation, and sun-position calls out of scope. You decide which operations are in scope, and the calls the agent makes are logged. - **Credential handling:** Your x-api-key is stored once, encrypted, by your own Jentic One instance and injected as the header on the data calls 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 coordinate' or 'get the timezone for a location', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **GeoNames** — Geographical database of place names, populations, and coordinates. - **OpenCage** — Forward and reverse geocoding built on open data. - **Amadeus** — Travel APIs for flights, hotels, and airport data. ## FAQ ### What authentication does the Mon-voyage-pas-cher.com Public API use? The data endpoints read an x-api-key header, per the OpenAPI spec, while the OPTIONS handlers need no credential and exist for browser preflight. Through Jentic the key is held by your own self-hosted instance and added to the data calls at execution time, so it never appears in the agent's prompt or logs. ### Can I find cities near a coordinate with this API? Yes. Call the find-cities-from-lat-long endpoint with a coordinate to get the nearby cities, or the find-cities-from-text endpoint to search by name. The significant-cities endpoint returns the notable cities for an area. ### What are the rate limits for the Mon-voyage-pas-cher.com Public API? The OpenAPI spec for the Mon-voyage-pas-cher.com Public API does not define rate limits. Check the provider's documentation for the allowances tied to your key before running high-volume lookups. ### Is there an MCP server for the Mon-voyage-pas-cher.com Public API? You don't need an MCP server to give your agent this API. Jentic connects it directly from the API Directory: import it, store the x-api-key once, and your agent calls the airport, city, and measurement operations without another server's tool definitions loaded into its context. ### Can I control which operations my agent can call on this API? Yes. Write a rule that allows only the lookups you need, such as airports and cities, and leave distance, elevation, or sun-position calls out of scope until you add them. You choose which operations are in scope, and the agent's requests are recorded. ### How do I find cities near a coordinate through Jentic? Search Jentic with an intent like 'find cities near a coordinate', and it returns the find-cities-from-lat-long operation with its input schema so the agent submits the coordinate and reads back the cities. To run it on your own infrastructure, install Jentic One from its GitHub repo.