How chyavanrao7/ai_tripplanner_agent works
Main Backend Components
• FastAPI Server (main.py)
• Chat Session Manager (redis_chat_manager.py)
• Trip Planner Logic (trip_planner.py)
• Caching Utilities (caching_utils.py)
• Firecrawl Scraper Wrapper (tools_firecrawl.py)
• Requirements/runtime files (requirements.txt, runtime.txt)
• External Services:
– Google Gemini 2.0 AI API
– Redis (session store & cache)
– Firecrawl service (for web scraping)
– Upstream travel data APIs (Skyscanner, Booking.com)
Relationships and Data Flows
• Client → FastAPI endpoints
– Incoming HTTP requests from frontend or API clients
• FastAPI routes → Session Manager
– redis_chat_manager handles user context, conversation history in Redis
• FastAPI routes → Trip Planner
– trip_planner processes intents, preferences, builds itineraries
• Trip Planner ↔ Caching Utils
– caching_utils reads/writes API call results in Redis (to avoid repeated calls)
• Trip Planner → External Travel APIs
– Via tools_firecrawl, fetches real-time flight & hotel data
• Trip Planner → Google Gemini API
– Submits user prompts & context, receives AI-generated itinerary text
• Firecrawl Wrapper → Firecrawl Service
– Scraper sidecar or HTTP client to Firecrawl for web-scraping endpoints
• Redis
– Central store for session state, cache of API results, conversation memory
Architectural Patterns
• Modular service layer under FastAPI (separate files for chat management, planning, caching, scraping)
• Cache-aside pattern with Redis for external data
• Stateless HTTP API layer with Redis for state persistence
• Dependency injection of modules in FastAPI (via import in main.py)