# check_melaka_visit_window

## Purpose

Check whether an arrival and duration fit published schedules, exceptions, last entry, and known service status. Use before finalizing an itinerary. This is not a real-time opening, inventory, or booking confirmation.

## Input

See the operation `check_melaka_visit_window` in [OpenAPI](/openapi.json). Inputs are strictly schema validated. Unknown properties on structured POST requests are rejected where the schema is strict.

## Output

The shared response envelope contains a runtime request ID and timestamp, schema/data versions, data mode, result, source references, cache state, warnings, and permitted next actions. Business results use `feasible`, `infeasible`, or `needs_verification` where applicable.

## Endpoint and cost

- REST: `POST /api/v1/visit-window/check`
- MCP tool: `check_melaka_visit_window`
- Internal metering: 2 credits
- Business side effects: none

## Schema example

Production examples are schema placeholders only. Use the current verified revision and returned stable place IDs; do not infer operational facts from examples.

## Evidence and limitations

Only the rights-filtered public view is returned. Missing, stale, conflicting, restricted, or out-of-coverage data is explicit. Live operation, ticket inventory, booking, payment, inquiry, and safety are never confirmed.

<!-- schema-key: checkMelakaVisitWindow -->