Booking Hotel Price Benchmark — Market Rates by City

One call = one city benchmarked from Booking.com. Give it a city and get the local hotel market as structured data: indicative nightly price distribution (median, percentiles), review-score mix and a sample of the hotels behind the numbers. Built for hotels benchmarking their rates, revenue managers, OTAs and AI agents.

{
    "location": "Madrid",
    "resolvedCity": "Madrid, Madrid, Spain",
    "analysis": {
        "n": 12,
        "currency": "EUR",
        "priceBasis": "indicative-nightly",
        "median": 125,
        "p10": 74, "p25": 104, "p75": 180, "p90": 342,
        "reviewScoreAvg": null,
        "confidence": "medium"
    },
    "hotels": [
        { "name": "Catalonia Puerta del Sol", "price": 180, "currency": "EUR" }
    ],
    "meta": { "hotelsFound": 12, "hotelsAnalyzed": 12 }
}

Why this is different

Booking.com sits behind an anti-bot wall that blocks plain scrapers outright. This actor drives a real browser through Booking's own search flow and reads the structured price data Booking ships to its own front-end (not fragile HTML scraping), so every hotel comes with a clean numeric price and, where available, its review score. The result is a market benchmark, not a pile of listings:

• Indicative market prices. Prices are Booking's "from" nightly rates per hotel — the going market rate for the city, ideal for benchmarking. Date-specific quotes are on the roadmap (v1.1).
• Robust to redesigns. Prices come from Booking's data layer, not CSS classes that change weekly.

Use cases

• Rate benchmarking: a hotel checks where its price sits in the local p25–p75 band.
• Revenue management: schedule daily runs and track the city's median market rate over time (build your own rate history).
• Investor / OTA screening: batch-run cities and compare median and reviewScoreAvg.

Use with AI agents (MCP)

https://mcp.apify.com?tools=jdepablos/booking-hotel-price-analyzer

Your agent gets a "what do hotels cost in X on these dates?" tool with self-describing structured output — no pagination, no HTML, no anti-bot handling on your side.

Pricing

Pay per event: $0.12 per hotel-market scan (a full browser session against Booking's anti-bot wall, stats + hotel sample included). Scans that return no hotels are never charged. The price reflects the residential-browser cost of getting reliably past Booking's protection — still a fraction of a rate-shopping subscription.

FAQ

Where do prices come from? Booking.com's public city page — the "from" nightly rate per hotel. The output states the basis via priceBasis (indicative-nightly).

Which locales? booking.com (English) and booking.es (Spanish). Inventory is the same; display currency follows the locale.

How many hotels per scan? ~12 representative hotels from the city page — enough for a stable market median.

Is this affiliated with Booking.com? No. Data comes from publicly visible search results.