Developers · Integrations

Drop it into the stack you already run.

Each guide is one middleware or edge file that looks up the visitor's IP, caches the answer, fails open, and on paid plans checks that a self-declared AI crawler really is one. No SDK to install.

01 · Where to call it

Pick the layer.

Same API, same response. What changes is how early you see the answer.

At the edge Cloudflare Workers
Before the request reaches your origin. Good for blocking unverified crawlers early and tagging requests for every backend behind it.
In the framework's proxy Next.js
Before routes render. Good for per-visitor content and redirects without touching each page.
As app middleware Express, Django, Laravel
Inside your app, next to sessions and auth. Good when only some routes need the data, such as sign-up or checkout.

02 · Every guide

Four rules they all follow.

  1. The key stays on the server. It is read from an environment variable or secret and never sent to the browser.
  2. The client IP comes from a source you trust. Each guide says which header or setting is safe on that platform.
  3. Answers are cached on your side. The same visitor costs one request, not one per page view.
  4. Failures fail open. A short timeout, and no visitor is blocked because a lookup was slow.

Start with a free key.

1.000 requests a day for location and network data. Every paid plan adds the bot flags and a higher daily limit, from 9,00 € a month (VAT included).