// the find
dabit3/gpt-travel-advisor
reference architecture for building a travel application with GPT3
A Next.js reference app showing how to wire OpenAI's completion API into a travel itinerary generator — you type in a destination and it returns points of interest and a day-by-day plan. It's meant to be read and copied from, not run as a product; useful for someone who wants a minimal example of calling OpenAI from Next.js API routes rather than a working travel tool.
The API routes (get-itinerary.ts, get-points-of-interest.ts) are small and readable, so the actual OpenAI call pattern is easy to lift into your own project. It mixes the old pages/api routing with the new app/ directory, which incidentally doubles as a working example of that Next.js migration if you're doing the same.
Dead since May 2023 — predates GPT-3.5-turbo and GPT-4 becoming the defaults, so the prompts and model name in the code are built for a model nobody calls anymore. There's no error handling or rate limiting shown in the README, and no indication the API routes handle malformed or empty OpenAI responses. The env var is literally named GPT_API_KEY for what's an OpenAI key, which is a small thing but signals the whole project was done quickly and never revisited. No tests, no discussion of cost (itinerary generation on GPT-3 pricing was not cheap per call), and the 'archive' folder with an orphaned get-locations.ts route suggests a feature was abandoned mid-build.