# Mintlify Starter Kit

- [Omnibeds: how the platform is built and how it works](https://demo-travel.webbinghub.io/docs/index.md): Omnibeds connects a travel agency to several hotel suppliers at once. This guide explains its layers, its pipelines and the rules that keep them safe.
- [Run Omnibeds locally and check a change](https://demo-travel.webbinghub.io/docs/quickstart.md): Start the Omnibeds app on your machine, apply database migrations, and run the type, lint, unit, end-to-end and live supplier checks before you commit.
- [The layers of Omnibeds and how a request moves through them](https://demo-travel.webbinghub.io/docs/architecture/layers.md): Omnibeds is split into screens, a typed client, routes, commands, domain services, supplier adapters and data. Follow one request through every layer.
- [Commands: every action with its risk and its checks](https://demo-travel.webbinghub.io/docs/architecture/commands.md): Each Omnibeds action is a command with a name, a risk level and an input schema. Learn the checks execute() runs, the risk levels, and how to add one.
- [Data: migrations, agency scope and transactions](https://demo-travel.webbinghub.io/docs/architecture/data.md): How Omnibeds stores its data in Postgres: numbered migrations, every query scoped to one agency, several writes as one transaction, and two-way trip links.
- [Front end: screens call the server through one typed client](https://demo-travel.webbinghub.io/docs/architecture/front-end.md): Omnibeds screens call commands with api(name, input, doing). See how the typed client works, how errors come back, and how big pages are split.
- [Search pipeline: from one query to one merged list](https://demo-travel.webbinghub.io/docs/pipelines/search.md): How Omnibeds searches every supplier at once: time limits, retries, circuit breakers, the cache, selling prices, streaming, and merging the same hotel across suppliers.
- [Booking pipeline: price check, guests, review, confirmation](https://demo-travel.webbinghub.io/docs/pipelines/booking.md): How Omnibeds books a room: the supplier confirms the price, every guest is named by the supplier's rules, the agent reviews, and unconfirmed bookings go to reconciliation.
- [Quote lifecycle: from draft to booking](https://demo-travel.webbinghub.io/docs/pipelines/quotes.md): How an Omnibeds quote moves from draft to priced, sent, accepted and converted, how prices are re-checked, and what the client's link shows and hides.
- [Trips and saved travellers: one journey from search to booking](https://demo-travel.webbinghub.io/docs/pipelines/trips.md): How an Omnibeds trip ties a client's travellers, quotes and bookings together: searching for a trip, filling guests from saved travellers, and two-way links.
- [After booking: live view, traveller changes, rebooking, price drops](https://demo-travel.webbinghub.io/docs/pipelines/after-booking.md): What Omnibeds does once a booking exists: the live supplier view, changing travellers, rebooking for a new party, the price-drop watch, cancelling and documents.
- [Reconciliation and the scheduled jobs](https://demo-travel.webbinghub.io/docs/pipelines/jobs.md): How Omnibeds finishes bookings a supplier hasn't confirmed, and what each scheduled job does: frequent checks, the daily quote job, exchange rates and hotel content.
- [Supplier adapters: one contract for every supplier](https://demo-travel.webbinghub.io/docs/suppliers/adapters.md): Every Omnibeds supplier, real or simulated, implements one adapter contract. See its methods, how each supplier keeps state, data modes, and the rules for adding one.
- [Confidential suppliers and presenter mode](https://demo-travel.webbinghub.io/docs/suppliers/confidential.md): Some suppliers' terms make their data confidential. See what Omnibeds hides outside presenter mode, where the check runs, and the rules for code and fixtures.
- [Hotelbeds integration: rules, flow and mapping](https://demo-travel.webbinghub.io/docs/suppliers/hotelbeds.md): The Hotelbeds APItude rules Omnibeds follows: signature auth, one search filter, child ages, rateKeys, the 40-call daily stop, booking, cancelling and how its data maps to ours.
- [LiteAPI integration: rules, flow and mapping](https://demo-travel.webbinghub.io/docs/suppliers/liteapi.md): The LiteAPI rules Omnibeds follows: two hosts, a prebook before every booking, the per-second pace, outdated-offer codes, holder-only name changes and how rates map to ours.
- [RateHawk integration: rules, flow and mapping](https://demo-travel.webbinghub.io/docs/suppliers/ratehawk.md): The RateHawk ETG v3 rules Omnibeds follows: search limits, stored content, hotel page and prebook, the five-call booking, name rules, async status, cancelling and mapping.
- [Errors, traces and supplier health](https://demo-travel.webbinghub.io/docs/operations/errors-and-logs.md): Every Omnibeds failure answers in one format with a plain reason and, when unexpected, a trace id. See the error codes, the Inspector, retention and the Health page.
- [How Omnibeds is tested](https://demo-travel.webbinghub.io/docs/operations/testing.md): The four kinds of Omnibeds tests: unit tests with an in-process database, boundary tests that guard the layers, end-to-end tests of real screens, and live supplier tests.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.