<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ritik Raj</title>
    <description>The latest articles on DEV Community by Ritik Raj (@chronos25).</description>
    <link>https://dev.to/chronos25</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F533739%2Fc5c5dfb2-b1bd-4d1a-8db5-e51e65dbf4f7.jpeg</url>
      <title>DEV Community: Ritik Raj</title>
      <link>https://dev.to/chronos25</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chronos25"/>
    <language>en</language>
    <item>
      <title>Agentic AI: Itinerary Planner</title>
      <dc:creator>Ritik Raj</dc:creator>
      <pubDate>Thu, 15 Oct 2026 17:24:54 +0000</pubDate>
      <link>https://dev.to/chronos25/agentic-ai-itinerary-planner-47c3</link>
      <guid>https://dev.to/chronos25/agentic-ai-itinerary-planner-47c3</guid>
      <description>&lt;p&gt;Building an AI-Powered Travel Itinerary Planner Using Ollama, Node.js, and React&lt;/p&gt;

&lt;p&gt;Introduction&lt;/p&gt;

&lt;p&gt;Travel planning is time-consuming — comparing routes, deciding daily activities, balancing pace, and estimating budgets.&lt;br&gt;
To solve this, I built an AI-powered travel itinerary planner that generates realistic, structured, and customizable travel plans based on user preferences.&lt;/p&gt;

&lt;p&gt;This article explains:&lt;/p&gt;

&lt;p&gt;What the system does&lt;br&gt;
How it was designed&lt;br&gt;
The technologies used&lt;br&gt;
Key engineering challenges and solutions&lt;br&gt;
How I Structured the System&lt;br&gt;
From the beginning, I knew one thing:&lt;/p&gt;

&lt;p&gt;The AI should not talk directly to the UI.&lt;/p&gt;

&lt;p&gt;So I designed the system like this:&lt;/p&gt;

&lt;p&gt;Press enter or click to view image in full size&lt;/p&gt;

&lt;p&gt;Each layer has one job:&lt;/p&gt;

&lt;p&gt;UI receives input and displays response data&lt;br&gt;
Listener controls logic, generates a custom prompt, and receives a response&lt;br&gt;
Ollama receives the prompt on model lamma3&lt;br&gt;
Why I Used Ollama (and Not OpenAI APIs)&lt;br&gt;
If you wanted:&lt;/p&gt;

&lt;p&gt;Local execution&lt;br&gt;
No API costs&lt;br&gt;
No data leaving my machine&lt;br&gt;
Full control over models&lt;br&gt;
That’s where Ollama came in. Checkout my stats-&lt;/p&gt;

&lt;p&gt;Press enter or click to view image in full size&lt;/p&gt;

&lt;p&gt;Ollama lets you run LLMs locally, inside Docker, and switch models easily.&lt;br&gt;
I tested models like:&lt;/p&gt;

&lt;p&gt;mistral&lt;br&gt;
quantized llama3&lt;br&gt;
This also forced me to deal with real-world constraints like memory limits, which honestly made the project better.&lt;/p&gt;

&lt;p&gt;Backend: The Real Workhorse&lt;br&gt;
The backend (Node.js + Express) does most of the heavy lifting. It calls Ollama, enforces strict JSON output, safely parses responses, validates the schema, and handles missing or partial data.&lt;/p&gt;

&lt;p&gt;A classic bug taught an important lesson: the AI returned perfect JSON, but I accidentally sent it as a string instead of an object 😄. Fixing it reinforced how critical backend validation is in AI systems.&lt;/p&gt;

&lt;p&gt;Frontend: Simple and Honest&lt;br&gt;
The frontend uses React and Material UI, focusing on clarity over flashiness. Each day of the itinerary is displayed as a card with morning, afternoon, and evening sections.&lt;/p&gt;

&lt;p&gt;Everything is rendered conditionally. If the AI skips a field, the UI adapts instead of crashing. This is how real AI products should behave.&lt;/p&gt;

&lt;p&gt;About Accuracy&lt;br&gt;
AI outputs aren’t “100% accurate.” Instead of pretending otherwise, this project defines accuracy as usability and completeness, not perfection. The system validates structure and stays transparent in the UI.&lt;/p&gt;

&lt;p&gt;Is This Agentic AI?&lt;br&gt;
Yes — functionally, but not hype-driven.&lt;/p&gt;

&lt;p&gt;It’s a goal-oriented, planner-style agent that reasons, plans, and produces structured output. It’s not a fully autonomous or multi-agent system yet, but it clearly demonstrates agentic behavior in a controlled, production-ready way.&lt;/p&gt;

</description>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>opensource</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
