> For the complete documentation index, see [llms.txt](https://docs.cinelaunch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cinelaunch.io/agreement-types/rent-a-system-agreement.md). # Rent-a-System Agreement In a rent-a-system agreement, a producer licenses certain film rights to a distribution company, typically a studio, for a **limited term**, but the distribution company is **not required to pay an advance** to the producer to either finance production or take delivery of the film. ### In fact, in some cases the producer pays all distribution expenses relating to the film. In exchange for the absence of fixed payments by the distribution company, the distribution company agrees to a **very low distribution fee,** and the remaining revenues are remitted to the producer. In essence, the **distribution company avoids any risk** of loss relating to the film, particularly if the distribution company does not pay distribution expenses, and the producer bears the full risk and reward of the success or failure of the film. Because of the absence of financial commitment by the distribution company, and the limited upside from the low fee, distribution companies have little incentive to adequately market and push a rent-a-system film, so **such films often flop.** --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cinelaunch.io/agreement-types/rent-a-system-agreement.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.