Listings, not guidebook prose
What's actually available to book now, rather than a description of a destination written a season ago.
Web index · sourcing
Web data for travel teams
Live routes, stays and things to do read from the operators that run them, with the practical detail — dates, prices, availability — kept as data rather than a written guide.
What's actually in it
The documents this work actually runs on.
Dates and prices kept attached
The detail a booking decision turns on travels with the listing, not as a footnote.
Events kept apart from routine listings
A one-off event is distinguishable from a standing attraction, which most directories blur.
Coverage of the destination itself
Travel and destination news, de-duplicated across outlets.
Built on this index
The workspaces this data feeds.
Status is shown per workspace — a “soon” workspace is on the roadmap, not available today.
The collections behind it
Browse the shelves this page draws from.
Questions
Frequently asked.
- Are these listings actually bookable, live inventory?
- They're read from operators and the places themselves, so a listing reflects current availability rather than a cached guide entry.
- Do I need the Travel workspace to see this?
- No — the collections above are browsable on their own. Travel is in beta today and reads this material when it builds an itinerary.
Web data for travel teams
Put the index to work.
Request private access and we'll walk through the collections and workspaces above.
Browse the rest of the catalog at /apps.
Request access