25 July, 2026
We are developing a new API. It is called the Fingerprint API.
The Fingerprint API works as a plugin API for the Intelligence API. It collects signals from the client side and feeds them into your policies, giving you more context to make trust decisions during signup and authentication flows.
The Fingerprint API is a separate endpoint that you call from the frontend. It gathers information about the connecting client and returns a structured response. You then pass that response into the Intelligence API as part of your evaluation request.
This keeps the architecture clean. The Intelligence API remains the core decision engine. The Fingerprint API acts as an input layer, enriching requests with additional signals.
The first release starts with IPv4 and IPv6 based checks. This includes:
These checks help identify whether a connection is coming from a residential network, a known VPN provider, a hosting environment, or an anonymizing service. The signals give you more control over which signups you allow, which you flag for review, and which you block outright.
This is not the full scope of what the Fingerprint API will offer. It is only the first set of checks we are releasing. More IP-based checks will be added later, along with other types of signals beyond IP analysis.
The Fingerprint API will be available within a couple of weeks. We are in the final stages of development. When it launches, documentation will be published alongside the API so you can integrate it immediately.
IP-based signals are some of the most reliable indicators of signup risk. Disposable email addresses tell one part of the story. Connection type tells another. Together, they give you a fuller picture of whether a signup is legitimate.
The Fingerprint API is designed to plug directly into the Intelligence API, making it easy to use these signals without changing your core integration. You already have a policy engine. Now you will have more inputs to feed into it.
This is just the first step. Over time, the Fingerprint API will grow to include more detection capabilities across different signal types.
We will share more when the API is ready to use.