> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/booking-engine-guide/booking-engine-widget/use-cases/prerequisites.md). # Prerequisites ### Getting started * You have followed the [Getting started](/booking-engine-guide/booking-engine-widget/getting-started.md) guide and understand how the Booking Engine Widget is installed ### Javascript and HTML * You have some familiarity with JavaScript and HTML ### HTTPS * The code is served from a secure location over HTTPS. If you serve it from an insecure HTTP site, you will be redirected to the [Booking Engine Standalone](/booking-engine-guide/booking-engine-standalone.md) and the code will not work. For testing and experimenting, you can also use services such as [CodePen](https://codepen.io). ### Modern browser * You are using a modern browser, ideally the [latest Google Chrome or Mozilla Firefox browser](https://browserslist.dev/?q=bGFzdCAxIENocm9tZSB2ZXJzaW9uLCBsYXN0IDEgRmlyZWZveCB2ZXJzaW9u). The Mews Booking Engine works in other browsers and older browsers, but custom code of the use cases is not guaranteed to work in these. You can of course modify the code to make it work. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mews.com/booking-engine-guide/booking-engine-widget/use-cases/prerequisites.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 `build a script that syncs our docs to a CMS` 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.