Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.cryptolens.io/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers important aspects of the platform that we recommend to review before you publish your application.

​
Expiry date is not enforced by default

The expiry date is not enforced by default and it will still be possible to activate a license even when the expiry date has passed. However, there are two ways to enforce it: either by setting up automatic blocking of expired licenses (if you will be using Key.Activate method) or by checking if the Block property inside the License Key object is True (if you are calling Key.GetKey or using offline licensing). You can find more information here.

​
Machines are not activated by default

If you plan to use node-locking or floating licensing, where the goal is to track machines, it’s important that each license that you issue sets the Maximum number of machines parameter to a value greater than 0. For example, if you would like to limit the license to 2 machines, Maximum number of machines should be set to 2.

​
Access token should have minimal scope of permissions

When you are ready to publish your application with Cryptolens, it’s important to ensure that access tokens that are used inside the application that is distributed to the client have as few permissions as possible. Normally, the access token used in the client application should only have Activate permission. Some data that is returned can also be masked if this is needed. Please review this article.

​
Verify AI-generated implementations

If a coding agent helped implement the integration, ask it to review the implementation before you ship. If you installed the Devolens skill bundle, use the license-key-verification skill and paste this into the same chat session: 
Use the license-key-verification skill to review the Devolens/Cryptolens integration in this project against:
- https://help.cryptolens.io/llms-full.txt
- https://app.cryptolens.io/docs/api/v3/llms-full.txt

Check that:
- the RSA public key or signed response is verified where the SDK/API supports it;
- the product id, license key, and access token are not hardcoded unless clearly intended;
- the access token permissions match the API methods actually called;
- IsOnRightMachine or equivalent machine-binding checks are only required when the license has maximum number of machines greater than 0;
- offline fallback stores a signed activation response or license file, not the access token;
- API errors are surfaced or logged clearly enough to diagnose access-token, product-id, permission, and subscription issues.

Report any issues with file paths, severity, and the exact change needed.