A large sculpted blue code symbol on an ivory plinth stands before a miniature destination, with a blue path connecting places and activities.

Overview

GoVisit strives to make it super easy for developers building travel-planning and destination-navigation apps with modern agentic tech stacks to access relevant insights about destinations, places, and activities, then turn those discoveries into bookable experiences in their own products.

Combine GoVisit’s published destination, place, and activity context with your app’s planning, navigation, and booking flows. GoVisit provides published discovery information, not reservation transactions or live prices and availability. Your app can make selected options bookable through its own booking integrations and relevant links when they are present in published content. Activity lists are page-local and are not live schedules.

Choose how to build

WebMCPBrowse browser tools and 21 stateless HTTP endpoints, with contracts and examples.Agent skillsInstall GoVisit skills in Claude Code or Codex to call WebMCP tool capabilities through the HTTP API.Coverage and reliabilityUnderstand result scope, freshness, request limits, errors, and version fields.

The use of GoVisit developer tools is subject to the GoVisit Data Use License, which explains permitted travel-planning use, attribution, and restrictions on bulk collection, resale, and marketplace use.

Start with the published contracts

The WebMCP manifest publishes tool availability and machine-readable contracts. The Agent Skills discovery index lists canonical packages and SHA-256 digests. Check the relevant index before installing or updating an integration; each reference explains the tool’s current availability and examples.

Use search and page context through HTTP

The two search endpoints accept query, language and supported geographic constraints. The 19 page endpoints add a required pagePath to the matching WebMCP tool arguments. Use a pathname from a canonical published GoVisit link; page language and scope follow that path. Both access methods execute the same tool handlers.

For example, discover a candidate with Search places, take the pathname of its canonical profile URL, then call Get place visit facts. You can read destination context, published category and collection members, destination activities, documentation sections and article FAQs in the same way. Each capability has its own Agent Skill.

// profileUrl is a canonical profile URL returned by search_places.
const pagePath = new URL(profileUrl).pathname;
const response = await fetch("https://govisit.ai/api/tools/v1/get_place_visit_facts", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ pagePath })
});
const facts = await response.json();
if (!response.ok) throw new Error(`${response.status}: ${facts.error}`);

Page readers use GoVisit's existing public page caches. They require no browser session, cookies or authentication. Supply the path without an origin, query, fragment or cache-refresh flag. Website information, current traveler location and blog search/read remain browser-only.

Design for useful travel decisions

Search results are candidates, not proof that a place meets every requirement. Read the returned canonical profile and cite its published facts.
Respect completeness, warnings, truncation, and release metadata when returned. A missing result is not proof that something does not exist.
Page-local lists—including activities—are not global inventories. Distance is geographic distance, not travel time.
Browser page readers need the matching GoVisit page context. Search HTTP requests use explicit language and geographic inputs; page HTTP requests resolve context from pagePath. Neither inherits a browser session or traveler location. GoVisit does not infer the traveler’s current location.

For result coverage, freshness, errors, request limits, and compatibility, see Coverage and reliability.