Travel Price Drop and Visa Reminder

Goal

Best fit

• - Use when the user wants flight or hotel price tracking.
• Use when the user needs visa, passport, or document timelines.
• Use when the user wants a clear reminder schedule.

Not fit

• - Avoid when the user asks to book or pay.
• Avoid when the user wants scraped data from restricted sites.
• Avoid when legal or visa advice is requested.

Quick orientation

• - references/overview.md for workflow and quality bar.
• INLINECODE1 for access and token handling.
• INLINECODE2 for optional integrations and templates.
• INLINECODE3 for async event handling.
• INLINECODE4 for intake questions and output formats.
• INLINECODE5 for common issues.
• INLINECODE6 for safety and privacy guardrails.

Required inputs

• - Origin, destination, and date range with flexibility.
• Budget or target price thresholds.
• Traveler nationality and passport expiry date.
• Reminder preferences and timezone.

Expected output

• - Price watch plan with thresholds and alert cadence.
• Visa or document checklist with due dates.
• Draft reminder messages.
• Summary of assumptions and data sources.

Operational notes

• - Use only official or user-provided data sources.
• Flag that price data can be delayed or incomplete.
• Do not provide legal advice; cite official sources only.

Security notes

• - Do not request payment details or account credentials.
• Avoid sharing personal travel documents.

Safe mode

• - Monitor and draft reminders only.
• No booking or payment actions.

Sensitive ops

• - Booking, paying, or handling visas directly is out of scope.