AI integration workflow
Experience a real activation in your own software, following one workflow from preparing licenses to AI-assisted integration.
১. পণ্য তৈরি
Sign in to the console and open Development & integration → Quickstart. Enter your software name to create a product, or select an existing one. Confirm that it is the software you want to integrate.
২. নীতি তৈরি
On the same page, click New policy. Choose perpetual, fixed-term, or trial licensing, set the device or floating-seat limit, and configure features, heartbeat, offline use, meters, and version rules as needed. Match feature IDs to actual operations in your software.
For example, use pdf_export for PDF exports. If you configure feature quotas, AI integrates the actual metering rules. Perpetual licenses need no duration; set the duration for fixed-term and trial licenses when issuing them.
3. Create and save your first-activation license
Click Create a license. Before issuing it, the page explains that this key is for you to experience the first activation of your own app after integration. It is separate from the prompt and will not be activated automatically by AI.
After creation, the final step shows the product name, license prefix, and full key. Copy the key separately or download the license text. For existing licenses, use the full key you saved earlier; management lists show only its prefix.
The key is saved temporarily in the current browser tab for your account and workspace. It remains available after refresh or returning from another console page, for up to 24 hours. Signing out or clearing the saved key removes it. Download the license text for long-term safekeeping.
4. Copy the English prompt and let AI integrate
Choose your software's language and platform, and optionally describe features to protect or other requirements. Open the project in an AI coding tool, click Copy English prompt, and paste it so AI can modify the project, run checks, and report the results.
The generated prompt covers SDK installation, public product settings, first-activation input, credential recovery after restart, real business entry points, heartbeat and offline use, devices or seats, feature metering, version limits, errors, and acceptance checks. Web apps must enforce licensing on a trusted backend.
The full key is kept separately for you. The prompt asks AI to implement an activation screen or interactive CLI, where you paste the key yourself and see activation succeed.
5. Activate your own software yourself
- Run your integrated software and find its activation screen or interactive CLI input.
- Return to Quickstart, click Copy activation key beside the prompt, then paste it into your own app and submit.
- Confirm that your app shows activation success, then try a real protected feature.
- Restart your software and confirm that its license restores without entering the key again.
How do I verify that AI completed the integration?
Review the changed files, feature mapping, run commands, and actual test results. Buttons, shortcuts, menus, background jobs, and server routes must enforce authorization at the real business boundary. Ungranted features must not execute, and offline use must follow the policy.
Perform the first activation manually. Automated tests can use local mocks; AI should distinguish mocked tests from completed live verification. Before release, also verify the device, floating-seat, metering, or version rules your app uses.