Star-rating override: watching the listing tier you actually care about
min_stars=2 for budget hunters, min_stars=5 for luxury sniping. Here's how each setting changes what survives the filter.
Hotelglitch's default filter drops anything below a 3-star hotel_class. That's the right default for a price-error monitor — most users want real hotels, not hostels — but it's not a perfect fit for everyone. The `min_stars` param lets you re-tune.
The settings
- min_stars: 1 — admit literally everything with a star rating. Hostel + capsule alerts come back. Useful when you're hunting in a city where the budget tier is actually what you want (a Tokyo capsule deal IS often a real deal).
- min_stars: 2 — admits clean-but-no-frills 2-stars. Useful for road-trip-friendly chains (Days Inn, Super 8) on routes where you'd happily take a 2-star.
- min_stars: 3 — DEFAULT. Real hotels only. Filters most of the obvious garbage.
- min_stars: 4 — boutique + premium-chain only. Hampton stays in; Holiday Inn drops out.
- min_stars: 5 — luxury sniping. Four Seasons, Ritz-Carlton, Mandarin — when one of these mis-prices it's usually a website glitch, not a real fire-sale, but they DO happen.
What stays filtered regardless
Even with `min_stars: 1`, the type-filter still drops `vacation rental`, `apartment`, `guesthouse`, `homestay`, and `campsite`. These are incomparable to hotels for fare-watching purposes — an Airbnb-style vacation rental's price-per-night includes cleaning fees that flip the math. If you specifically want to watch one, list it as a target manually rather than relying on auto-discovery.
Reviews floor
The `reviews >= 50` filter is hard-coded — it drops new sublistings + listing-page noise. We haven't surfaced an override because in practice every legitimate hotel listing crosses 50 reviews within weeks of going live, and the filter has caught zero false-positives in the last quarter of operation.