Docs menuAll pages, quickstarts and this page’s contents

Quickstarts

Pick where your code runs. Every guide takes you from an API key to a scored signup, then to blocking the two things that actually cost you money: traffic that is not a real user, and one person opening many accounts.

The browser guides collect a device fingerprint on the page and score it on your server, so your secret key never reaches the browser. The server guides are the whole integration on their own if you already have the signals you need.

Web

Mobile

AndroidPlannedNo guide yet. The HTTP API works from any language today.iOSPlannedNo guide yet. The HTTP API works from any language today.React NativePlannedNo guide yet. The HTTP API works from any language today.FlutterPlannedNo guide yet. The HTTP API works from any language today.

Server

Node.js@kaidn/sdk, the server-side TypeScript client.PHPPHP 7.4+, installed with Composer or a single file.C#/.NETPlannedNo guide yet. The HTTP API works from any language today.GoPlannedNo guide yet. The HTTP API works from any language today.JavaPlannedNo guide yet. The HTTP API works from any language today.PythonThe kaidn client from PyPI, zero dependencies.

What every quickstart covers

The steps differ by stack, but the shape does not. Each one gets you an API key, installs the client, scores a real signup, then turns that score into a decision. Nothing asks you to understand the engine first.

If you would rather read than build, core concepts explains how a verdict is made in six ideas, and the API reference has every field and reason code. Missing your language? The HTTP API is one keyed POST and works from anything that can make a request.