Two engines, deliberately. B2B builds a price up from Cost-to-Serve; B2C starts at a published rate card and moves it between a cost floor and a market ceiling. Same fleet, opposite direction. Pick the customer you are quoting for.
Daily, weekly and monthly vehicle rental booked by a person. Priced by a revenue-management engine: cost sets the floor, the market sets the ceiling, and demand moves the rate between them.
Vehicles on contract to an organisation — staff transport, school routes, municipal fleets. Priced per vehicle per month over a contract term.
Both are proof-of-concept models. Every coefficient behind them is a stand-in until the operator's fleet, finance and market data are loaded, so a figure from either console is a worked example rather than a signable quote.
Integrating rather than clicking? POST /api/price is the B2B contract
endpoint and POST /api/b2c/price is the B2C booking endpoint — different engines,
different request shapes. /docs is the schema, with
every endpoint callable. Neither console prices anything itself; both render what the API
returns.