Guides: protect a form from spam bots with Antisy
Three guides to put Antisy on a form that already exists, against spam bots: in PHP, with Next.js, in a WordPress site. Each one takes up the examples from the documentation, without a dependency. Access is by waiting list. The API and the dashboard (in French) have been in service since 27 October 2026, hosted at Infomaniak in Geneva; no customer is in production yet.
As of .
Protect a PHP form from bots: Antisy guide
A verification file in PHP and cURL, a contact form handler, and the secret in the environment of the server.
Protect a Next.js form from bots: Antisy guide
The tag in the layout, a POST form, a route that calls the Node function of the documentation, and the nonce-based CSP policy.
Protect a WordPress form from spam bots: Antisy guide
No plugin: a tag in the head, the PHP function of the documentation, and two WordPress hooks, for comments and for a hand-written form.
Before you start
The three guides do the same thing: a tag in the page, a hidden antisy-token field that the script fills in on submission, a call from your server to POST /v1/siteverify with your secret, and a response allow or deny. What changes is where each piece is plugged in.
None of them needs a plugin or a package: the verification is an HTTP call, which the examples of the documentation make without a dependency. For another language, or to understand each step, the documentation remains the reference.
See: Documentation: step-by-step guide · Documentation: verify a token · Documentation: quick start