# After Check-in

> After Check-in helps travellers choose a stay and collect beach, dining and nightlife ideas into an editable trip in Dubai, Cancún, Miami Beach, Phuket, Koh Samui & Koh Phangan, Ibiza, Mykonos. Agents can create a ready-to-open itinerary link without an account or a write API.

Website: https://goaftercheckin.com/
Contact: contact@goaftercheckin.com

Traveler starting point: [Plan with your AI assistant](https://goaftercheckin.com/plan-with-your-agent) provides a copyable brief and explains what a useful, editable plan should contain. Use the [editorial method](https://goaftercheckin.com/about) and linked destination comparisons to understand recommendation limits.

## Create a ready trip link

- [Trip-link guide](https://goaftercheckin.com/trip-guide): Read this first. Exact v1 URL-fragment format, catalog fields, limits, local dates, runnable JavaScript, privacy and a complete working example.
- [Example JSON packet](https://goaftercheckin.com/trip-link-example.json): A complete example with real Cancún catalog IDs and illustrative March 2027 dates. It is not a booking or a verified programme for those dates.
- [JavaScript encoder](https://goaftercheckin.com/trip-link-example.js): UTF-8 to unpadded base64url; no authentication, writes or network calls.
- [Current site encoder and decoder](https://goaftercheckin.com/trip-sharing.js): Authoritative link implementation; imports trip-store.js for catalog validation.

Read the guide and fetch the selected destination's JSON before creating a link. Use exact catalog IDs, the user's requested dates and preferences, and confirmed=false for every stop. A valid URL opens a trip preview; the traveller chooses "Open my own copy" to save a new local trip. Describe it as an editable suggested itinerary, never a reservation. Return the full URL including its #trip= fragment, with a concise description of the stay, dates and proposed stops. Do not truncate or URL-encode the entire link.

## Destinations and public catalogs

- [Dubai planner](https://goaftercheckin.com/dubai) and [Dubai JSON](https://goaftercheckin.com/dubai-data.json): destinationId dubai; timezone Asia/Dubai.
- [Cancún planner](https://goaftercheckin.com/cancun) and [Cancún JSON](https://goaftercheckin.com/data.json): destinationId cancun; timezone America/Cancun.
- [Miami Beach planner](https://goaftercheckin.com/miami) and [Miami Beach JSON](https://goaftercheckin.com/miami-data.json): destinationId miami; timezone America/New_York.
- [Phuket planner](https://goaftercheckin.com/phuket) and [Phuket JSON](https://goaftercheckin.com/phuket-data.json): destinationId phuket; timezone Asia/Bangkok.
- [Koh Samui & Koh Phangan planner](https://goaftercheckin.com/samui-phangan) and [Koh Samui & Koh Phangan JSON](https://goaftercheckin.com/samui-phangan-data.json): destinationId samui-phangan; timezone Asia/Bangkok.
- [Ibiza planner](https://goaftercheckin.com/ibiza) and [Ibiza JSON](https://goaftercheckin.com/ibiza-data.json): destinationId ibiza; timezone Europe/Madrid.
- [Mykonos planner](https://goaftercheckin.com/mykonos) and [Mykonos JSON](https://goaftercheckin.com/mykonos-data.json): destinationId mykonos; timezone Europe/Athens.

Catalog arrays: stays, experiences, events.events, events.recurringPrograms and venues.venues. Read checked, validUntil, seasonStart, seasonEnd, verifiedForDatesThrough, status, entryNote, caveat, agePolicy and source URLs where present. IDs can appear in both experiences and venues. Do not infer live prices, availability, guest access, opening dates or event recurrence from a saved catalog entry; consult the linked operator when needed. Dated events belong only on their stated dates. Missing or stale evidence means uncertain, not confirmed.

Recurring programs use local daysOfWeek: numeric 1–7 means Monday–Sunday; some records use English weekday names or abbreviations. Match weekdays within the requested trip and all published date limits. Verify the actual night with the operator: recurrence is not a confirmed dated event. A recurring program id is not a valid planner stop refId. Use venueId only if it exists in stays, experiences or venues, otherwise refId:null with an honest customName. Read the program name from title or name, and its explanation/caveat from summary or confirmationNote. Read time, then publishedTime, then startTime/endTime as available; retain any uncertainty in the published wording and distinguish the starting weekday from an after-midnight end. Follow official or sources[].url for the recorded operator evidence. Put the program name and source caveat in the note and keep confirmed:false.

## Make a useful trip, not just a valid packet

1. Establish destination, local check-in/checkout dates, arrival/departure windows, adults, rooms, accommodation budget with currency and per-room/per-night or total basis, other spending, pace, room style, transport/mobility needs, nightlife preferences and noise tolerance. Ask for essential missing constraints; label assumptions. Do not ask for identity documents or booking references.
2. Compare two suitable stays and explain one tradeoff for each. Distinguish on-site parties, external venues and room-specific admission. Do not use a score as a substitute for fit, or infer prices/availability from the catalog.
3. Keep arrival light, allow rest after late nights, group stops by feasible routes and allow transfer buffers. Direct map distances are not route times. Check transport and return arrangements from current sources; leave timings tentative if unknown.
4. Read the operator's event date/time convention for after-midnight listings; do not silently move an event to the preceding evening. Item day/time is the actual local calendar date/time when established. The planner schedules stops on check-in-inclusive, checkout-exclusive dates; keep checkout travel or out-of-range after-midnight notes in the summary, not an invalid stop.
5. Verify scheduled events only for their published dates and season. Separate source-verified facts, unknowns and booking status: even a verified event remains confirmed=false unless the traveler later marks their own booking. Give an alternative or free-time idea when a night is unavailable or evidence is stale.
6. Separate accommodation, meals, tickets, transport and extras in the budget; distinguish current dated provider quotes from estimates and unknowns. These catalogs are curated stays and nightlife, not complete city coverage. Dining coverage varies by destination, and some dining places appear only in venues.venues. There is no live price feed. Research missing dining/daytime/transport details using current primary sources, or leave free-time placeholders. Never invent a catalog ID for outside research.
7. Return the full trip link plus the recommended stay, short daily outline, sources/check dates, budget uncertainties and practical checks before booking. Use exact catalog IDs, concise notes, and the technical guide's link limits. If unable to fetch current catalogs or encode a valid link, disclose that and return a plain itinerary rather than a fabricated link.

Combine experiences[] and venues.venues[] by exact ID: merge shared records and retain places present only in one array. Important hours, entryNote, transport or age conditions may exist only in the venue record, while experience admission appears in inclusions.Entry. Venue-only IDs are valid planner references, including Cancun dining places such as mextreme-cancun. Read both records and their source dates; do not let a generic label override a specific condition. verified_open is a historical snapshot, not proof of future operation. Expired validUntil or dates outside verified coverage require fresh operator confirmation or clearly tentative/unscheduled ideas. Some stays lack verified pins: confirm exact addresses and routes instead of estimating journey times from area names. Check boat transfers, seasonal boarding points and return services where relevant.

The packet supports 1–8 adults and 1–4 rooms, no more rooms than adults, and no children field. Do not encode children as adults, clamp a larger group, or silently omit travelers. Explain the limit and provide a plain itinerary with provider occupancy checks when the group cannot be represented.

See the [planning checklist](https://goaftercheckin.com/trip-guide#quality) for how outside-catalog ideas and local dates fit the packet.

## Sharing and storage

Trip links contain a readable base64url snapshot, not an encrypted or private record. Exclude personal, payment and booking-reference data. Anyone with a link can read the included notes. Trips save in the traveller's browser after acceptance; this is not account sync. Later edits do not update a previously shared link. The planner also offers Save file and Load file; its backup format is different from the share-link packet.

## Discovery

- [Sitemap](https://goaftercheckin.com/sitemap.xml)
- [Robots policy](https://goaftercheckin.com/robots.txt)

This file is a navigation aid for tools that choose to read it. It does not guarantee search indexing or agent support.