That's assuming that you require license validation with every request though, when in reality you really only need that information periodically. If you're usi

That's assuming that you require license validation with every request though, when in reality you really only need that information periodically. If you're using Keygen alongside your own API, then that information can be cached and requested when needed. It would be integrated the same way you would integrate something like Stripe; you request information when required, and keep your own records up to date via webhook events. For example, a desktop app would really only need to validate a users license after they have successfully logged in after booting the app; you likely wouldn't need to validate the license again for at least 24 hours, and that's assuming you wanted to perform periodic license validations for long-running sessions.