Changelog
Dated, factual notes on what changed. Entries are added when something ships, not on a schedule.
2026-10-06: hotel coordinates
The property rows from POST /v1/hotels/search and the POST /v1/hotels/by-name answer now
carry latitude and longitude: WGS84 decimal degrees from Booking.com's own data, read from
the same page as the price, so no extra request. Hotel Sant'Angelo in Rome reads
41.9057575, 12.4724811. Both are null when Booking.com publishes no position, and on a
by-name answer for a hotel that was not found. The two MCP servers pass them through on
search_hotels and find_hotel_by_name.
2026-08: the new flightpowers.com
The apex domain now serves this site; the consumer product moved to demo.flightpowers.com.
- New marketing site on
flightpowers.com: homepage with a live agent demo (real searches, per-visitor and daily caps), endpoint pages for both APIs, free tools,/mcp, use cases, and this changelog, replacing 13 indexable URLs across two domains. - Every canned example on the site is a captured run labelled with its capture date; pricing renders from data parsed off the live RapidAPI listings on a stated date.
llms.txtis generated from the same config that renders the pages.- The old consumer blog posts moved with the consumer product and 301-redirect to
demo.flightpowers.com/blog. The story behind the rebuild: Rebuilding flightpowers.com.
2026-08-25: developer site
developers.flightpowers.com goes up: home, /flights-api, /hotels-api, and this page.
Every page is rendered to static HTML at build time. The sitemap is generated by walking the
route tree, so a new page is announced to search engines the moment it exists. The previous
sitemap on flightpowers.com was a hand-maintained file and had gone stale.
Nothing about the APIs themselves changed in this entry.