> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/live-booking-calendar-lbc-and-live-odds-lo/live-booking-calendar-lbc-and-live-odds-lo.md). # Live Booking Calendar (LBC) and Live Odds (LO) Our Live Booking Calendar (LBC) is designed to help you manage subscription schedules and book live events with ease. It provides an interface for planning and scheduling events across most Live Betradar services—including Live Odds, Live Data, BetPal, and the full Live Channel portfolio (Online, Retail, Trading, and Promotion Premium). With a powerful set of tools, the LBC lets you stay fully in control: schedule subscriptions, coordinate matches, and manage all your bookings in one place, quickly and efficiently. The Live Odds (LO) service is a fully automated in-play betting solution. It delivers real-time odds and settlements across a wide range of sports and markets. As the industry’s most widely used in-play betting service, Live Odds is fully integrated in Sportradar's Unified Odds Feed, helping you stay competitive with speed, accuracy, and reliability. To discover the main features of the Live Booking Calendar and get step-by-step guidance on using the Live Odds service, visit our [Live Booking Calendar ](/live-booking-calendar-lbc-and-live-odds-lo/video-tutorials/live-booking-calendar-lbc.md) & [Live Odds Video tutorials.](/live-booking-calendar-lbc-and-live-odds-lo/video-tutorials/live-odds-lo.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sportradar.com/live-booking-calendar-lbc-and-live-odds-lo/live-booking-calendar-lbc-and-live-odds-lo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.