Voyage

Voyage — connector documentation

• MCP endpoint: https://voyage.connectorbay.com/mcp
• REST API: POST https://voyage.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://voyage.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://voyage.connectorbay.com/health · Tool schemas: https://voyage.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/voyage · agent@connectorbay.com

What Voyage is for

The map questions that come up when planning or moving around: where a place is, what is at a coordinate, how long it takes to drive or walk between two points and which way to go, which of several options is closest, the best order to visit a list of stops, where the nearest pharmacy, café, charger or station is and whether it is open, what a travel guide says to see and eat, and what time and weather it is there right now. All of it from OpenStreetMap and its free services, with links back to the map.

What it does

Geocoding and reverse geocoding with structured addresses and OSM ids (Nominatim, Photon fallback). Routes for driving, walking and cycling with distance, time, per-leg summary and turn-by-turn instructions, via-points and alternatives (OSRM). Travel-time and distance matrices between up to 10 places. Multi-stop route optimisation (travelling-salesman) with a fixed start and optional fixed end or round trip. Nearby search in 60+ categories with distance, direction, opening hours, phone, website, cuisine and wheelchair access (Overpass, Nominatim fallback). Full details and tags for one place. Wikivoyage guides by section. A place snapshot with time zone, local time, elevation, current weather, today's range, rain chance, sunrise and sunset (Open-Meteo).

What it is not

Voyage is not a live-traffic navigator or a booking service: the public router has no traffic data and only a car profile, so walking and cycling times are estimated from road distance at typical speeds; there are no transit schedules. OpenStreetMap is community-mapped — opening hours and phone numbers are as mapped, and "nothing nearby" means nothing mapped within the radius.

Tools

Places

geocode — Find places by name or address (OpenStreetMap/Nominatim, Photon fallback): coordinates, type, structured address, OSM id and link, bounding box. Use for "where is X", "coordinates of Y", "find the address of Z". Args: query, country, max_results.

reverse_geocode — What is at a coordinate: the nearest address or place with structured components, at the level asked for (building/address, street, city, country). Use for "what's at 48.8583, 2.2945", "which city is this". Args: latitude, longitude, detail.

place_details — Everything OpenStreetMap knows about one place: full address, category, coordinates, and tags such as opening hours, phone, website, cuisine, wheelchair access, levels, operator, Wikipedia link. Use after nearby/geocode or for "opening hours of Café A Brasileira". Args: osm_id, name.

nearby — Places of a category around a point, nearest first, from OpenStreetMap (Overpass, Nominatim fallback): name, distance and direction, address, opening hours, phone, website, cuisine, wheelchair access and OSM link. Use for "pharmacies near me", "cafés within 500 m of the station", "EV chargers near Lisbon airport". Args: place, category, radius_m, max_results.

Routing

route — Directions between places on the OpenStreetMap road network: total distance and time, per-leg summary, and turn-by-turn steps with road names; optional via-points and alternatives. Use for "how long to drive from A to B", "walking directions from the hotel to the station", "route via Palo Alto". Args: origin, destination, mode, via, steps, alternatives.

travel_matrix — Travel time and distance between every pair of places (a matrix), for comparing options or planning. Use for "which of these three hotels is closest to the office", "drive times between Berlin, Hamburg and Munich". Args: places, mode.

optimize_stops — The best order to visit several stops (travelling-salesman via OSRM): ordered itinerary with leg distances and times and the total. Use for "plan the shortest route to see these five places", "order these deliveries". Args: stops, mode, round_trip, fixed_end.

Guides & snapshot

city_guide — The Wikivoyage travel guide for a destination, by section (Understand, Get in, Get around, See, Do, Buy, Eat, Drink, Sleep, Stay safe, Connect, Go next) as plain text with the article link. Use for "what should I see in Lisbon", "how do I get around Kyoto", "is Bali safe". Args: place, sections, max_chars_per_section.

place_snapshot — A place right now: resolved location and country, time zone and local time, elevation, current weather with today's high/low and rain chance, sunrise and sunset. Use for "what time is it in Tokyo", "weather in Reykjavik now", "how high is Cusco". Args: place.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/voyage/support

Voyage — Privacy Policy

Effective 23 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Voyage is. Voyage is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for map and travel lookups: geocoding, routes, travel matrices, stop ordering, places nearby, place details, travel guides and place snapshots. You interact with your assistant; the assistant sends us only the place names, addresses or coordinates needed for the lookup.

What we receive. The arguments of each tool call (place names, addresses or coordinates — which may describe where you are or intend to go — a category, a mode of travel), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Location data is used for one lookup and not stored. A place or coordinate is sent to the relevant OpenStreetMap service (Nominatim/Photon for geocoding, OSRM for routing, Overpass for nearby search) and to Open-Meteo for weather, and the answer is returned to your assistant. We do not keep a history of the places you ask about, build a profile, or link requests to you. Nothing you send is stored, logged in request bodies or used to train anything. Successful upstream answers are cached in memory for 15 minutes to 24 hours, keyed by the query, to respect the usage policies of these community services.

What we do not receive or store. We do not receive your conversation with the assistant, your device location (only what the assistant chooses to send as text), your name, contacts, accounts or credentials for any service. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. OpenStreetMap Foundation — Nominatim (geocoding), Komoot — Photon (geocoding fallback), Project OSRM demo server (routing), Overpass API mirrors (overpass-api.de, maps.mail.ru, overpass.private.coffee — places), Wikimedia — Wikivoyage (guides) and Open-Meteo (weather, elevation, sun times). Each receives the query and our server's IP address, never yours. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Voyage is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Voyage — Terms of Service

Effective 23 September 2026. These terms govern use of the Voyage connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Voyage returns geocoding, routing, nearby places, place details, travel-guide text and place snapshots from OpenStreetMap-based services and Open-Meteo. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not for navigation-critical use. Routes and times are estimates from a community router without live traffic, road closures or turn restrictions guaranteed current; walking and cycling times are approximations. Do not rely on the Service for emergency, safety-critical or commercial fleet navigation.
3. Sources and licences. Map data © OpenStreetMap contributors, ODbL — attribute OpenStreetMap when you reuse it. Travel-guide text is from Wikivoyage, CC BY-SA. Weather and elevation from Open-Meteo (CC BY). Nominatim, Photon, the OSRM demo server and Overpass mirrors are community services with usage policies; the Service caches and paces requests to respect them.
4. Acceptable use. Do not use the Service for bulk geocoding, scraping or heavy automated routing that would breach the underlying services' policies, or to circumvent rate limits. Ordinary assistant use within the published limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: a place is used for one lookup and nothing is stored.
7. Attribution. OpenStreetMap contributors; Nominatim; Photon by Komoot; Project OSRM; Overpass API; Wikivoyage; Open-Meteo; GeoNames (CC BY) for the bundled city list.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
9. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
10. Governing law. California law; venue in San Mateo County, California.
11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/voyage

Voyage support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://voyage.connectorbay.com/mcp
• REST API: https://voyage.connectorbay.com/openapi.json
• Live status: https://voyage.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Voyage never asks for them.