> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/fiscal-hosts/sponsor-agreement.md). # Agreement Templates **Note: This does not constitute legal advice in any way. Consult with a lawyer before entering into any contractual relationship.** ## Sponsorship Agreement Template Some Collectives form sponsorship relationships for which an agreement can make everything more clear and secure for all parties. We have developed this template for Collectives in Fiscal Hosts in the United States, but it may be useful for others. The entity forming a legal agreement with the sponsor is your [Fiscal Host](/help/fiscal-hosts/fiscal-hosts.md). Therefore, Collectives need someone from their fiscal host involved, and cannot enter into legal agreements on their own, as they are not an incorporated entity. ### [Google Doc: Host-Sponsor Agreement](https://docs.google.com/document/d/1XpvL_xvihB3T9CHf7dzqmCfb7nMxpPR2zhtnmiRyPaU/copy) ## Open Collective Terms Host Addendum When a Fiscal Host signs up with Open Collective, we provide this addendum to the standard terms and conditions to cover the extended services and relationship. ### [Google Doc: Host-Open Collective Agreement](https://docs.google.com/document/d/1zID7rcWhJ-2ENzL8PoT2iUPgMJPy5yvOO-ACUUW66lw/copy) --- # 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.opencollective.com/help/fiscal-hosts/sponsor-agreement.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.