Airbnb Competitor Watch

Airbnb Competitor Watch 🔍

🤖 Run as MCP Tool in Claude Code, Cursor & Windsurf

This Actor is 100% compatible with Model Context Protocol (MCP). Connect it directly to your AI Agent:

Hosted (OAuth, no token in the config):

{
  "mcpServers": {
    "airbnb-competitor-watch": {
      "url": "https://mcp.apify.com?tools=titan_coder/airbnb-competitor-watch"
    }
  }
}

Local (stdio):

{
  "mcpServers": {
    "airbnb-competitor-watch": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "titan_coder/airbnb-competitor-watch"
      ],
      "env": {
        "APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Know the moment a competitor drops their price — before your guests do.

Every morning, get a one-glance answer to the three questions every Airbnb host asks themselves: Am I priced right? Who just got cheaper than me? Who went unavailable? No spreadsheets, no manually opening 20 tabs — just a clean digest and a dataset you can plug anywhere.

Why hosts use this

• See price moves the day they happen. Every competitor listing is checked against your exact dates. A price drop, a price hike, a listing going unavailable — you see it the next morning, not weeks later when your bookings quietly slow down.
• Know your rank, not just a number. For every stay, you get your position among comparable listings and how far you sit from the median — so "am I overpriced?" has an actual answer.
• Pay only for real answers. One event, check-delivered, billed only when a check comes back with a price or a confirmed unavailability/minimum-stay result. Errors, retries, and blocked attempts cost nothing. No run fee, no hidden per-diff charge.
• Set it and forget it. Attach an Apify Schedule once; get a digest every day with what changed, plus an optional webhook for Slack/Telegram/your own dashboard.

How it works

1. Give it your listings and up to 30 competitors (or let it default to the next 8 weekends automatically).
2. It checks price and availability for each listing × stay combination, the same way a browser would.
3. It compares today's result to yesterday's, ranks your listing among comparable competitors, and writes one row per delivered check to a dataset.
4. You get a short digest (and an optional webhook) summarizing what changed.

What you pay for

One event only — check-delivered. A check = listing × stay (check-in/check-out) × guests × currency that returned either a price or a confirmed unavailability / minimum-stay restriction. Errors, blocks, retries, and unchecked pairs are free. No run fee, no extra charge for the diff, digest, or webhook. Each saved row is charged exactly once — idempotent per monitor and observation — so re-running never double-bills you.

What it does NOT promise

Occupancy or bookings ("unavailable" ≠ booked), the full breakdown of fees/taxes beyond what Airbnb itself shows, search-ranking position, automated price changes, or coverage of Booking.com/Vrbo. If Airbnb changes its page structure, we aim to fix it fast — but we don't guarantee a repair time.

Нужен ваш прокси

Этому сайту требуется прокси для предотвращения блокировок (HTTP 401/403/429/капча):

• Apify Proxy (RESIDENTIAL): включите {"useApifyProxy": true} — трафик списывается напрямую с вашего баланса Apify.
• Собственные прокси (BYO): укажите список ваших прокси в proxyConfiguration.proxyUrls (http://, https://, socks5://).
• Автор актора за прокси не платит и не закладывает расходы на трафик в стоимость запуска. Если прокси не настроен или недоступен, актор безопасно завершает работу без списания средств.

Input

Output

• Dataset — one row per delivered check: status (priced / unavailable_for_requested_stay / minimum_stay_restriction), total price for the stay, change vs. yesterday (changeType, deltaPct), and your rank among comparable listings (rankAmongPriced, medianPriced, deltaVsMedianPct).
• Key-value store — digest (a short human-readable summary, ≤3,500 characters) and coverage (how many checks were answered, with reasons for anything skipped). With historyMode=daily, also a full run archive and baseline for tomorrow's comparison.
• Run status — a clear FAILED reason on bad input, a busy/locked monitor, or answered-coverage below 50% (rows already saved stay saved and billed — you never lose data you paid for).

Scheduling

Save it as a Task and attach an Apify Schedule (daily works well). The Actor itself doesn't self-schedule.

Limits

Up to 35 listings × 30 stays (≤1,050 checks per run); one retry per check on transient errors; an early stop after 20 consecutive failures so a bad run doesn't burn your budget; a light request pace designed to be a good citizen.

A note on the source

Data comes from Airbnb's public listing pages, fetched the same way a browser does. Airbnb's Terms of Service restrict automated access — use this at your own discretion and within the limits that make sense for your account.