> 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/purchasing-a-license.md). # Purchasing a License The Scry License NFTs are simply a NFT which gives the holder the right to access and usethe contracts, tools, node and frontend freely for their project. You can simply mint an NFT at \ and have the 1y fee included in the mint (theres no extra fee for minting, you are simply purchasing 1y in advance during mint). The NFT allows you to specify a github user for us to give access to the node, as well as allow you to pull your oracle addreess into our frontend for access to the explorer and health tools, as well as allowing you and your users to check out your data and feeds. The price will be determined by the Scry Founder after launch once the Founder allocation has been minted. You can renew your license for any amount of time at the current price for as long as you want. If you do not renew, anyone can burn your license, making you need to mint a new one and losing access to the github node as well the right to use the contracts in production . --- # 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/purchasing-a-license.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.