none — No Device Binding
Any device can verify the key. No hwid field is needed in the request. This is the simplest option for software that does not need device-level restrictions.
hwid — Hardware ID Lock
Each device sends a machine fingerprint (hardware ID). The key auto-binds to the HWID on the first verification call. Subsequent calls from the same HWID are idempotent. A new HWID consumes an activation slot.
Generating a Hardware ID
Combine machine-specific values and hash them to produce a consistent, unique identifier. The goal is a string that stays the same across reboots but differs between machines.ip — IP Address Lock
The API auto-detects the caller’s IP address and binds it to the key. No hwid field is needed in the request. Each unique IP uses an activation slot.
IP locking is useful for server-side software (e.g. FiveM resources, web apps, bots) where the IP is stable. It is not recommended for end-user desktop software because consumer IPs change frequently.
Comparison
| Feature | none | hwid | ip |
|---|---|---|---|
| Device binding | No | Yes (machine fingerprint) | Yes (IP address) |
hwid field required | No | Yes | No |
| Best for | Simple key-only checks | Desktop software | Server-side software |
| Spoofing difficulty | N/A | Medium-High | Low (VPN/proxy) |

