canonical: https://jentic.com/apis/mon-voyage-pas-cher.com/mon-voyage-pas-cher-main

# Mon-voyage-pas-cher.com Public API

Jentic publishes the only available OpenAPI specification for Mon-voyage-pas-cher.com Public API, keeping it validated and agent-ready. The API exposes geographic reference data and travel utility endpoints including airports, cities, continents, countries, distance calculations, elevation lookups, sun position calculations, and timezone resolution. It is positioned as a free utility layer for travel-tech projects that need a single source for static geographic data and lightweight geo-math operations. Endpoints are read-only and return structured JSON for direct consumption by travel comparison or itinerary tools.

## For AI agents

Look up airports, cities, countries, distances, elevations, sun positions, and timezones via a single travel-utility geographic API.

## Scope

Does not handle flight pricing, hotel booking, or payment processing - use for free travel-utility geographic lookups only.

## Capabilities

- List airports worldwide for travel itinerary building
- Find cities by latitude/longitude or by free-text search
- Calculate the great-circle distance between two coordinate pairs
- Resolve the timezone for a given coordinate pair
- Look up sunrise, sunset, and other sun positions for a coordinate and date

## Use cases

### Travel Itinerary Distance and Timezone Calculations

Build flight or road-trip itineraries that show the distance between waypoints and the local timezone for each stop. Calling GET /distance with two coordinate pairs returns the great-circle kilometres, while GET /timezone resolves the timezone string used to format local arrival times. Suitable for travel-comparison sites adding contextual stop information without hitting Google's metered APIs.

Example prompt: Call GET /distance with the origin and destination lat/long pairs, then GET /timezone for the destination to format local arrival time.

### City Search for Travel Booking Forms

Power city search-and-suggest fields in travel booking forms with the cities/findcitiesfromtext endpoint, which accepts a partial query and returns matching cities. The latitude/longitude variant complements it for nearest-city lookups when starting from a current GPS reading. Useful for travel comparison sites that want a free first-party city dataset rather than negotiating with a places API vendor.

Example prompt: Call GET /cities/findcitiesfromtext with the user's partial query to populate a city dropdown, then GET /cities/findcitiesfromlatlong to confirm a selection by GPS.

### Sunrise and Sunset Display for Trip Pages

Show the local sunrise, sunset, and other sun position data on trip detail pages so travellers can plan activities around daylight. The sun_positions endpoint accepts a coordinate and date, returning the times in a single response. Practical for travel content sites adding contextual local-condition data without licensing a paid astronomy API.

Example prompt: Call GET /sun_positions with the destination coordinate and travel date to retrieve sunrise and sunset times for display.

### Agent-Driven Travel Data Lookups

AI agents building travel itineraries call this API through Jentic to fetch distances, timezones, and sun positions without holding the x-api-key in their context. Jentic's spec is the only structured definition for the API, so schema-aware agents rely on it for tool selection.

Example prompt: Search Jentic for 'calculate the distance between two cities', load GET /distance, and execute with the lat/long pairs.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /airports | List airports worldwide |
| GET | /cities/findcitiesfromtext | Search cities by free-text query |
| GET | /cities/findcitiesfromlatlong | Find cities near a coordinate pair |
| GET | /countries | List countries |
| GET | /distance | Calculate great-circle distance between two coordinates |
| GET | /elevation | Look up elevation at a coordinate |
| GET | /sun_positions | Retrieve sunrise, sunset, and sun-position times |
| GET | /timezone | Resolve the timezone string for a coordinate |

## Key resources

- **airports** — List airports worldwide for itinerary planning
- **cities** — Find cities by name, coordinate, or significance
- **continents** — List continents and continent-level metadata
- **countries** — List countries and country-level reference data
- **distance** — Calculate great-circle distance between coordinates
- **elevation** — Look up elevation at a coordinate
- **sun_positions** — Retrieve sunrise, sunset, and sun-position times for a coordinate and date
- **timezone** — Resolve the timezone string for a coordinate

## Why Jentic

- **Setup:** Wiring the Mon-voyage-pas-cher.com API by hand means setting the x-api-key header and coding each geographic lookup call, from airports to distance to timezone, yourself. Through Jentic you install once, import the Mon-voyage-pas-cher.com API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Mon-voyage-pas-cher.com API takes its lookup inputs as query parameters rather than path resources, so you limit the agent to the operations it needs, such as distance or timezone lookups. All listed operations are read-only, so the agent gets only the queries you allow.
- **Credential handling:** Your Mon-voyage-pas-cher.com 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 'calculate the distance between two cities', and Jentic returns the matching distance, timezone, or city-search operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HERE Maps API** — Enterprise mapping platform with global geocoding, routing, and places coverage
- **OpenCage Geocoding API** — Forward and reverse geocoding API built on OpenStreetMap data
- **GeoNames API** — Worldwide geographical database for names, codes, and feature lookups

## FAQ

### Why is there no official OpenAPI spec for Mon-voyage-pas-cher.com Public API?

Mon-voyage-pas-cher.com does not publish an OpenAPI specification through its own developer portal. Jentic generates and maintains this spec so that AI agents and developers can call Mon-voyage-pas-cher.com Public API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Mon-voyage-pas-cher.com Public API use?

The API uses an API key sent in the x-api-key request header. Through Jentic, the key is held encrypted in the credential vault and injected at request time so the secret never enters agent context.

### Can I calculate the distance between two cities with this API?

Yes. Call GET /distance with two latitude/longitude pairs and the API returns the great-circle distance. To convert city names to coordinates first, call GET /cities/findcitiesfromtext on each city name to retrieve the centroid coordinates.

### What are the rate limits for the Mon-voyage-pas-cher.com Public API?

The OpenAPI spec does not document explicit rate limits. As a free travel-utility API, treat it as best-effort; pace requests, cache static lookups (countries, continents, airports), and avoid issuing thousands of distance calls in tight loops.

### How do I look up sunrise and sunset times through Jentic?

Run pip install jentic, search for 'get sunrise and sunset times', load GET /sun_positions, and execute with the destination latitude, longitude, and date. Jentic returns the structured sun-position object ready for display.

### Is the Mon-voyage-pas-cher.com API free?

The API is positioned as a free travel-utility layer at https://api.mon-voyage-pas-cher.com - confirm with the provider for any production or commercial-use terms before scaling up traffic. There is no publicly listed paid tier in the spec.

### Can I limit what my agent is allowed to do with the Mon-voyage-pas-cher.com Public API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's read-only operations the agent may call, so you can allow only the lookups it needs, such as GET /distance or GET /timezone, while withholding GET /airports, GET /cities/findcitiesfromtext, or GET /sun_positions. Every endpoint takes its inputs as query parameters and returns data without changing anything, so a scoped agent can read only the queries you permit. The x-api-key is stored by your own instance and injected at request time, so the agent never sees the credential.