> For the complete documentation index, see [llms.txt](https://docs.scry.finance/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scry.finance/docs/links/deprecated/licensing-and-perks.md). # Licensing and Perks At launch the contracts the node is fully open source and free to use. This license is represented by either a founder or license NFT and allows the holder full access to all contracts, tools, front end and node as they need. ### Perks for Founders * Special channels and roles in the Discord for discussion for internal comms. * Lifetime License to all contracts, tools, nodes, front end and all perks for holding a license. ### Perks for Licenses * Support for setting up your oracles, nodes, datasets, front ends and any needs for deploying and maintaining your oracles. * Access to specialised channels in the Discord * Whitelisting in the Scry front end and access to data explorer tools and health tools * Ability to have Scry run your oracles for you as long as gas is provided --- # 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.scry.finance/docs/links/deprecated/licensing-and-perks.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.