# WenToGo

> Deterministic travel timing. WenToGo scores exact trip dates against researched weather, crowd, price and event data, then tells you which dates would have been better.

Every score comes from a versioned data export rather than a language model, so
the same URL returns the same answer for the same data version. Dates are ISO
`YYYY-MM-DD` and inclusive. Country, destination and month segments are
lowercase slugs such as `japan`, `tokyo` and `april`. Substitute your own into
the patterns below; the live list of every country and destination is at
https://wentogo.com/countries/.

## Answer a dated question

- `/trip/{country}/{destination}/{start}/{end}`: how good those exact dates are, what drags the score down and which nearby windows beat them. Example: https://wentogo.com/trip/japan/tokyo/2027-04-01/2027-04-08
- `/where-to-go/{start}/{end}/`: the destinations worth visiting in a fixed window, ranked. Example: https://wentogo.com/where-to-go/2027-04-01/2027-04-08/
- `/where-to-go/{country}/{start}/{end}/`: the same question narrowed to one country.
- `/compare/{country}/{destination}/vs/{country}/{destination}/{start}/{end}/`: two destinations over one window, side by side.

## Browse without dates

- https://wentogo.com/countries/: every country and destination covered.
- `/countries/{country}/`: the destinations covered in one country.
- `/countries/{country}/{destination}/`: one destination across the whole year.
- `/countries/{country}/{destination}/{month}/`: one destination in one month.
- https://wentogo.com/best-in/: the best destinations month by month. Use `/best-in/{month}/` for a month and `/best-in/{month}/all/` for its full ranking.

## When to use WenToGo

- You have fixed dates and need a defensible verdict on them: score,
  what drags it down, and better nearby windows (`/trip/...`).
- You have a window and want destinations ranked for it (`/where-to-go/...`).
- You are choosing a month rather than a date (`/best-in/`, month pages).

## Machine-readable description

- https://wentogo.com/openapi.json (OpenAPI 3.1) describes the one JSON
  endpoint, `GET /api/trip/{country}/{destination}/{start}/{end}`. Fair
  use is enforced across every `/api/` path at 20 requests every 10 seconds
  per client, then 429. Browsing the pages above is not limited. Cache responses
  by request and `source_version` to avoid repeat calls.

## About

- https://wentogo.com/about/: who builds this, how the scores are made and
  where the evidence lives.
- https://wentogo.com/blog/: why the site judges dates rather than places.
- https://wentogo.com/contact/: one channel for corrections. No inbox, on
  purpose.
- https://wentogo.com/privacy/: what we collect, which is very little.

## Machine-readable files

- https://wentogo.com/.well-known/ai-catalog.json: a selected catalogue of
  agent-facing resources, for registries that index them.
- https://wentogo.com/.well-known/api-catalog: the RFC 9727 API catalog, one
  linkset entry for the trip API pointing at its OpenAPI description, its
  documentation and its no-auth metadata.
- https://wentogo.com/auth.md: there is no login. No page or endpoint needs a
  key, a token or an account, and there is no authorization server to
  discover.
- https://wentogo.com/.well-known/oauth-protected-resource: RFC 9728 resource
  identification and documentation metadata. The no-auth contract is stated
  in `auth.md`, not inferred from omitted metadata fields.

## Notes

- Send `Accept: text/markdown` to receive Markdown from the homepage, country
  and destination overviews, `/best-in/`, `/blog/`, `/privacy/`, and the
  `/compare/` landing. Destination-month and dated result pages remain HTML.
- Dated pages under `/trip/`, `/where-to-go/` and `/compare/` are computed per request and marked `noindex`, so they are absent from the sitemap by design. They are still yours to fetch and cite.
- Canonical browse pages carry trailing slashes and redirect if you drop one. Dated `/trip/` URLs take either form.
- Every `/api/` path returns JSON, including errors: an unknown or withdrawn API path answers 404 with the structured `NOT_PART_OF_PUBLIC_API` error body rather than an HTML page.
- No MCP server is offered. A tool endpoint would bill every agent question as a Worker invocation against a free-plan daily cap, so the agent surface is deliberately this file, the pages above and the JSON API in openapi.json.
- An unknown country or destination returns 404. A malformed or unusable date window returns 400. Neither case guesses an answer.
- Everything indexable is listed in https://wentogo.com/sitemap-index.xml.