Hello DEV: a Swiss antibot for forms

Antisy is an anti-bot for web forms: one script tag on your page, one call from your server, and a verdict that is either allow or deny.

The tag loads a script that fills a hidden antisy-token field while the visitor fills in the form. The visitor sees nothing and is asked nothing.

<script src="https://api.antisy.com/v1/i/l.js"
        data-site="YOUR_PUBLIC_ID" defer></script>

When the form arrives, your server sends the token to POST /v1/siteverify with your secret and reads one field, success. It is true if and only if verdict is allow. Anything else is a refusal, and your form shows a generic message.

curl -sS --max-time 3 https://api.antisy.com/v1/siteverify \
  -d secret="$ANTISY_SECRET" \
  --data-urlencode response="$ANTISY_TOKEN"

That is the whole integration: no library to install, and nothing but allow or deny comes back. We will write about why in a later post.

Where things stand. Antisy Sàrl is a company in Geneva, entered in the commercial register since 8 October 2026. The API and the dashboard have been in service since 27 October 2026, hosted at Infomaniak in Geneva. Access is by waiting list. The pilot started on 9 November 2026 on our own forms, so we are our own first test. No customer is in production yet, and we publish no detection rate.

Antisy only defends. It never sends traffic to a system that is not yours.

I will use this account for what we learn while building it: what breaks, what we fix, and the parts of the documentation we had to rewrite after trying them. Next up: what your form should do when our API is down, and what happened when we ran our own WordPress guide in a real WordPress.

If you run forms that robots keep filling in, I would like to hear what you use today and what annoys you about it.

Waiting list and documentation: https://antisy.com/en