Data sources

What goes in, what comes back out, and what it costs.

myrevai is an analysis layer, not a booking engine. It reads the booking data your property already produces and the public market around it, then hands back recommendations, forecasts and reports. Every external source is listed here with the limits we hold it to — including the ones that cost money on each call.

Inbound
PMS · channel manager · API · CSV
Market
Multiple online sources · event search
Outbound
Recommendations · forecasts · exports
Not included
Reservations, inventory, payments

Your data, in

Four ways to get your bookings into the engine.

None of them require replacing what you run today. The fastest path is usually a CSV on the first call and a proper sync once you have decided it is worth it.

Channel manager sync

Two-way connectivity through a channel manager keeps bookings, rates and availability aligned with the OTAs you already sell on.

Booking.com · MakeMyTrip · Agoda · Airbnb · Expedia · Goibibo · Yatra · Cleartrip

REST API

Push bookings, room types, rates and cancellations directly. The same endpoints the product uses internally, documented and versioned.

Authenticated per account · JSON · webhook callbacks

CSV import

A booking export is enough to start. Ninety days of history produces a usable confidence score on the first run.

Bookings · rates · channels · commission

PMS data

Room inventory, rate plans, charges and guest records, so occupancy and ADR are computed on real inventory rather than an assumed room count.

Room types · inventory · charges · guests

Market intelligence, in

The external calls, and the leash on each one.

These sources are metered because they are billed. We publish the limits so you know what a refresh costs before you ask for one.

Live competitor rates

Live competitor pricing and availability for your city and dates — the backbone of myEDGE AI and of the comp-set signal inside aiREV.

250 refreshes / month · 8 / day · 7-day cache

Event and festival search

Local events, festivals and seasonal trends near the property, used to raise or hold rates around specific dates rather than whole months.

Refreshed daily · cached per city

Language models

Routed by purpose through a single gateway — one model for conversation, others for revenue and competitive analysis.

Per-account daily budget · three-level kill switch

Exchange rates

Competitor prices arrive in USD. Rates are fetched and cached so a comp-set average is never a mixed-currency artefact.

Cached daily

Analysis, out

Recommendations you can act on wherever you sell.

myrevai does not take reservations, hold inventory or process payments — your PMS, channel manager and booking engine keep doing all of that. What it produces is a dated rate recommendation per room type, which you approve and then apply in whichever system owns your rates.

Where a two-way connection exists, approved recommendations can be pushed straight through as a rate update. Otherwise they export, or you pull them from the API into your own tooling.

Outbound

Rate recommendations

Fixed or percentage, scoped to a room type and a date range, with the reason and confidence attached. Approve, then apply in the system that owns your rates.

Offer suggestions

Targeted at the specific soft dates the forecast exposes, with a validity window and minimum-night rules — not a blanket sale.

Reports and exports

Metrics, channel margin and profit tables, for accountants and investors who want the raw grid.

API reads

Pull recommendations, metrics and forecasts into your own tooling if you would rather not use ours.

When a source is unavailable

Degrade, don't fabricate.

External services fail, quotas run out, and new properties have no history. What the product does in those moments says more about it than what it does on a good day.

Competitor data missing

The comp-set signal falls back to manually entered competitor rates, then to a neutral multiplier. It is never invented, and the dashboard says the data is unavailable.

A refresh fails

The last good competitor data is retained rather than wiped, and the staleness of what you are seeing is shown alongside it.

No history yet

A new property is told it does not have enough data for a health score, instead of being shown a confident number derived from nothing.

Data age shownStale flaggedLast good data retainedSource named on every figure

Tell us where your bookings live.

We will confirm whether it syncs today, needs the API, or is simply a CSV away — usually in one call.