Melaka travel data & tools

Plan a Melaka day that works.

Check opening windows, itinerary conflicts, costs and evidence before you go.

Start with your constraints

Build a candidate day

Enter the details the planner actually evaluates. The result keeps conflicts and missing evidence visible and does not make a booking.

Date and time
Party and budget
Preferences

Calculated in memory from the current reviewed dataset. No trip, inquiry, or booking is saved.

Current coverage

Bounded, reviewed travel coverage

27 reviewed places

Only places in the current reviewed, rights-cleared dataset revision are listed.

Versioned evidence

Every public field retains review, freshness, validity, resolution, source, and data-version context.

No booking claims

Results assess published constraints only. They do not confirm live operation, inventory, reservations, or safety.

Read the coverage and missing-data statement

For agents and developers

Six tools, one fact and rule layer

read-only

search_melaka_places

Search covered Melaka demo or verified place facts with deterministic filters and evidence-aware matching. Use it to discover stable place IDs. Do not treat missing evidence as a passed hard constraint or use it for live inventory.

GET /api/v1/places · 1 credit

read-only

get_melaka_place_facts

Retrieve rights-filtered facts, field evidence, schedules, offers, services, facilities, and revisions for one covered place ID. Do not use it to confirm live operation, ticket inventory, or a booking.

GET /api/v1/places/{place_id} · 1 credit

read-only

check_melaka_visit_window

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.

POST /api/v1/visit-window/check · 2 credits

read-only

get_melaka_weather_advisory

Return the configured Melaka-area weather advisory state, forecast coverage, spatial granularity, validity, and evidence. Do not interpret area forecasts as venue conditions or absence of warnings as safety.

GET /api/v1/weather/advisory · 1 credit

read-only

plan_melaka_day

Build a deterministic single-day candidate itinerary of at most eight stops from covered facts and explicit route assumptions. Use for a practical draft. It does not promise a globally optimal route or live availability.

POST /api/v1/itineraries/plan · 5 credits

read-only

validate_melaka_itinerary

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.

POST /api/v1/itineraries/validate · 3 credits

Evidence

Every public fact retains source groups, review status, validity, freshness, and permitted uses. A retrieved timestamp never substitutes for a human check.

Unknown

Missing price does not mean free. Missing routes do not become guessed walking times. Missing warnings do not mean safe.

Limits

Asmaliana is an independent project, not an official tourism body. Time-sensitive decisions still require independent confirmation.