# validate_melaka_itinerary

## Purpose

Validate up to eight structured stops against published windows, services, costs, constraints, and supplied transport estimates. Use for an existing itinerary. Free-text parsing, booking, and live operation checks are not supported.

## Input

See the operation `validate_melaka_itinerary` 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/itineraries/validate`
- MCP tool: `validate_melaka_itinerary`
- Internal metering: 3 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: validateMelakaItinerary -->