RevokeGPT documentation

RevokeGPT checks that a request comes from a person. Your page or app gets a token, your server sends it to siteverify, and you get back a score and the reasons behind it. You decide what to do with it.

Pick your path

1. Web page: add the JavaScript, React or Vue client.
2. Mobile app: iOS, Android, Flutter or React Native.
3. Server: verify the token with Node, Python, PHP, Go or Java, or use the WordPress plugin.
4. No code change in your app: put a firewall integration in front of it.
5. Coming from reCAPTCHA: migrate, usually a two-URL change.

How it works

The browser (or app) solves a small proof of work and sends signals to the RevokeGPT edge, which issues a single-use response token. Your server calls POST /v1/siteverify with your secret key and that token. The reply carries success, a score from 0 to 1 and a list of reasons. See scores and reason codes.

Every quickstart follows the same five steps:

1. Create a site in the dashboard and copy its site key (rgpk_...) and secret key (rgsk_...).
2. Add the client to your page or app.
3. Verify the token on your server.
4. Read the score and the reasons.
5. Run the go-live checklist.

Status

The SDKs are built and tested in the repository. Where a package is not published to its registry yet, its quickstart says so and shows the install-from-source step instead of a registry command.

The API host is https://api.revokegpt.com and the widget script is served from https://js.revokegpt.com.