A proposed connection layer
A proposed optional connection layer for supported RateHighway data and services. This page describes an architectural direction, not a released capability.
Status. Vibe Connect is proposed. Nothing on this page should be read as a commitment about access, entitlement, pricing, production availability, integration support, data rights or timing. Where a detail has not been decided, this page says so.
API-first, MCP-native
The API is the stable service contract. MCP is the agent-facing layer that makes approved API capabilities understandable to AI coding agents.
MCP should not replace the API. MCP should expose approved API capabilities intelligently to agents.
The layers
Four layers on a supported foundation. Each has a different job and a different rate of change.
VibeLab Modules
Ready-made and customisable user-facing applications. What an operator actually opens.
RateHighway Agent Interface / MCP
Makes approved RateHighway capabilities understandable to AI coding agents, described around business jobs rather than endpoints.
RateHighway APIs
Stable, versioned programmatic access to approved data and services. The contract everything else depends on.
VibeLab Data Standard
Common car rental data concepts, so that two tools built by different people mean the same thing by the same word.
RateMonitor Elite
Supported revenue-management and pricing capabilities where an operator uses it. RME remains the pricing engine.
The objects every tool keeps re-inventing
A standard would define the objects a car rental revenue management tool needs, and the meaning behind each one rather than only its field name.
No formal industry adoption is claimed for any of this. It is standards work under consideration.
What a governed connection would require
Reading authorised data and writing a live price are different products with different guarantees. They should not arrive together.
Where things stand
Vibe Connect as a product
A direction under consideration. No launch, entitlement or pricing is defined.
Access and permissions
Who may connect, to what, under which agreement, remains undecided.
Data standard version 1
A deliberately narrow first version is under discussion: rate shop data, fleet and utilisation, reservations and booking pace, and pricing actions.