Mon-voyage-pas-cher.com Public API
Community OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey21 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For 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.
Use for: List the airports in this region, Find the nearest cities to these coordinates, Search cities by name, What is the distance between these two points?
Not supported: Serves geographic reference data for travel planning. Does not book flights or hotels, process payments, or manage user accounts.
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.
Install Jentic One Beta
Connect the Mon-voyage-pas-cher.com Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mon-voyage-pas-cher.com Public 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%2Fmon-voyage-pas-cher.com%2Fmon-voyage-pas-cher-public-api" | 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%2Fmon-voyage-pas-cher.com%2Fmon-voyage-pas-cher-public-api" | 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 Mon-voyage-pas-cher.com Public API.
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
Patterns agents use Mon-voyage-pas-cher.com Public API for, with concrete tasks.
★ 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.
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.
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.
Resolve a location's timezone and sun positions to schedule activities within daylight
Key Endpoints
21 endpoints — the mon-voyage-pas-cher.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mon-voyage-pas-cher.com Public API through Jentic.
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.
GET STARTED