Data sources / Hotel demand curve
Hotel demand curve: sources and method
Forward nightly rates of a fixed panel of hotels per city for the next 90 nights, and the demand index derived from them.
- Row
- City × check-in night × snapshot day
- Key
- City slug
- Refresh
- Daily snapshots; each adds a pickup history.
Where it comes from
| Source | How we read it | Licence or basis |
|---|---|---|
| Public hotel rate listings | Public search result pages, no login, no booking | Prices businesses show to every visitor |
How the data is collected
- Each day we read the lowest public nightly rate (1 night, 2 adults) of the city’s panel for each of the next 90 nights.
- The demand index is the night’s rate over the city’s median night; flags mark spikes and soft nights.
Legal basis and collection rules
- Only pages and endpoints that answer an anonymous visitor: no login, no account, no credentials, tokens or keys of anyone else, no paywalled content.
- Before a source goes live we read its robots.txt and terms and record what they say. They are one of the signals we weigh for each source, together with whether the data is public without login and what the data is.
- Low request rates, only the pages and fields we need, and we slow down or stop when a site signals it.
Personal data
- None: rows are cities, nights and prices.
Details: privacy policy.
Quality and limits
- When too few panel hotels show a price, the row says so (basis "page" instead of "panel").
- A panel of the most-reviewed hotels, not every hotel in the city.
How to get it
Removal requests
If you run a source we read, or a record is about you or your business, write to hello@arcadiumdata.io with the source or the record (a domain or a URL is enough). We stop collecting it and remove it from the files, the API, the MCP tools and the data pages within 24 hours, and reply once it is done.