GetFlight blog.
Product notes from building a Bitcoin checkout and AI-native flight booking app, backfilled from the project history.
Why GetFlight starts with ordinary search, comparison, passenger details, payment, confirmation, and booking management.
How GetFlight added sitemap, robots, canonical metadata, and structured page descriptions for public booking pages.
Why GetFlight records lifecycle changes alongside the current booking status.
How GetFlight carries request IDs through responses, booking events, payment metadata, and booking calls.
Why GetFlight keeps public flight search unauthenticated while booking and payment tools require OAuth account connection.
How account authorization keeps AI-native booking tied to traveler approval.
How GetFlight expanded from fare selection into service choices and richer booking review.
How Bitcoin and Lightning checkout fit into the normal airline booking lifecycle.
Why booking recovery and clear customer status matter when paid flight booking needs follow-up.
Why GetFlight moved raw fare-search responses out of D1 and into object storage.