LoginSign Up
← Back to all sparks
W

Wheelhouse

E-COMM
Velocity5.0

Wheelhouse spent July turning its pricing app into an API that other software can operate.

revenue-managementapi-firstmcpshort-term-rentalsportfolio-analyticspartner-ecosystem
◆Current state
Wheelhouse's revenue-management product is now fully addressable from outside its own interface. July closed every known gap between the app and the RM API, shipped an MCP server exposing 58 tools at parity with the UI, and named a first class of partners that read and write a customer's account programmatically instead of just consuming prices downstream. August opens with Scoreboards, one endpoint that returns the whole portfolio ranked by any of thirty-plus metrics over any window.
◆Where it's heading
The releases are converging on portfolio-scale questions answered in a single call — Scoreboards, segment aggregated metrics, neighborhood occupancy filters — which is exactly what an LLM client needs to be useful across hundreds of listings. The pricing engine itself gets narrower, more careful work: Historical Anchoring gains an anchor-source choice so discounted bookings don't become next year's floor, with the default left alone. Alongside these, a run of partner promotions occupies the same feed without changing the product.
◆Prediction
Expect more endpoints shaped like Scoreboards — one request, portfolio-wide, ranked — with the MCP tool list growing beside them, since each new aggregate immediately becomes a question someone can ask in a prompt.

◆Recent moves

  1. 4d ago

    Scoreboard Endpoint: Rank Listings by any KPI

    Scoreboards collapses portfolio analysis into one request: pick a metric from thirty-plus, a window, optional filters and an ordering, and every listing comes back ranked. It ships with matching MCP tools, so the same question works from a prompt — least-occupied two-bedrooms in November — without pulling each listing's data first. It is the natural next endpoint after July's stat expansion and API parity work.

  2. 15d ago

    OTAmiser: Free Audit Tool for Wheelhouse Users

    A co-marketing partnership: Wheelhouse and Otamiser cover the cost of a free Airbnb listing audit scoring title, photos, reviews and availability settings. Nothing changes inside Wheelhouse — it points customers at the ranking factors pricing alone cannot fix. Partner posts like this recur in the feed alongside actual releases.

  3. 28d ago

    RM API: Dynamic Sets, Segment Metrics, Notification Settings & Higher Rate Limits

    Dynamic Sets can now be built end to end over the API, segments expose rolled-up monthly metrics, notification settings become readable and writable, and the default rate limit rises to 60 requests a minute. Wheelhouse states this closes every known gap between the app and the RM API. Parity is the precondition for the MCP server and the partner integrations to be worth building against.

  4. 1mo ago

    Introducing Wheelhouse API Partners — Starting with IntelliHost

    IntelliHost is the first partner building directly on the RM API — reviewing the portfolio each morning, flagging underpriced dates, and pushing approved rate changes back into Wheelhouse from Slack. It marks a distinction Wheelhouse draws itself: earlier integrations pushed prices downstream to a PMS or OTA, while this one operates the account. The revenue and time-saved figures quoted are the partner's own.

  5. 1mo ago

    Historical Anchoring: New Anchor Source + Full 18-Month Protection

    Historical Anchoring gains a second anchor source — the last Wheelhouse-posted price at the time of booking rather than the final booked rate — so promo codes, wholesale net rates and group discounts don't quietly become next year's floor. Protection now spans the full 18-month horizon, and portfolio settings gain bulk copy and better grouping. Every account stays on the existing default, so this is an option rather than a change in behavior.

  6. 1mo ago

    New API Endpoints: History, Sync, Segments & Teams

    Base Price history, calendar day history with observed status and posted prices, listing sync triggers, and segment and team management all become API-callable, alongside a documentation cleanup that fixes mismatches with the implementation. The history endpoints matter most: a partner can reconstruct how pricing moved without keeping a shadow log of its own. Foundational plumbing for the integrations announced days later.