> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/sdks/go-sdk/v2/samples.md). # Samples This section provides a guide to the core functionalities available in the SDK and how to use them effectively. It supports various license types, including online, offline, floating, consumption, and air-gapped licenses, as well as feature-specific controls. Each license type comes with its own set of methods for activation, validation, usage, and deactivation. In this guide, you'll see how to: * Initialize and configure the LicenseHandler * Activate and validate licenses both online and offline * Manage floating slots for licenses and features * Handle consumption-based licenses and features * Use air-gap-compatible activation and confirmation flows * Perform local checks without needing internet access * Retrieve and use license or feature metadata stored in local files --- # 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.licensespring.com/sdks/go-sdk/v2/samples.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.