Metered Licensing

Aspose.OCR for .NET Plugins use a metered key to activate licensed plugin functionality. This licensing mechanism applies the plugin license and keeps your application compliant with licensing terms.

Billing clarification

For Aspose.OCR for .NET Plugins, metered keys do not add a separate usage-based charge for API calls. The product may maintain internal consumption counters when a metered key is used, but plugin customers are not billed separately for the number of API calls.

Key Features of the Metered Licensing Model

  • Single Plugin Licensing: Each application instance can only license one plugin. If you attempt to access features outside the licensed scope, your application will automatically switch to trial mode so users can evaluate those features separately.
  • Trial Mode: Experience the plugin before applying a license. This mode allows you to assess the software before purchase.

To purchase licenses, visit the Aspose Purchase Portal .

How to Implement Metered Licensing in .NET

Follow this step-by-step guide to configure the Metered class for your plugin licensing needs:

  1. Instantiate the Metered Class: Create an instance of the Metered class.
  2. Set Your Keys: Use the SetMeteredKey method to enter your public and private keys.
  3. Perform Processing Tasks: Execute the necessary tasks using the plugin.
  4. Monitor Consumption: Utilize the GetConsumptionQuantity method to track the total number of API requests consumed.

Example of Metered Licensing Implementation

Here’s a practical example demonstrating how to set your metered keys:

Metered license = new Metered();  
license.SetMeteredKey("<your public key>", "<your private key>");

For additional examples and detailed usage, refer to the Plugin Licensing Use Examples in C# .

Benefits of Metered Licensing for .NET Developers

Choosing a metered licensing solution offers several advantages:

  • Cost-Effective: Activate the licensed plugin without an additional per-API-call charge for plugin usage.
  • Scalability: Use the licensed plugin as your application requirements evolve.
  • Transparency: Consumption APIs can expose internal metered-license counters when needed.
  • Flexibility: Explore additional features in trial mode before making a purchase decision.

Comparing Licensing Models

When considering your options, treat metered licensing for Aspose.OCR for .NET Plugins as a key-based plugin licensing mechanism. It should not be interpreted as a separate usage-based billing model for API calls.

Security Considerations

Keep in mind the .NET metered licensing security considerations to ensure that your application remains compliant and secure while utilizing the licensing model.

Conclusion

Use metered licensing to activate Aspose.OCR for .NET Plugin functionality in your application. For plugin usage, API call counters are internal and do not create an additional usage-based charge.

 English