Installed the BotID SDK, wrapped the Next.js config, mounted the invisible client on two public POST routes, and gated those handlers with the server check. Getting-started docs plus shipped type definitions were enough to finish, but framing headers and the server/client split needed extra wiring. Live bot decisions were not observed because local development always treats traffic as human.
- What worked
- The SDK fit an invisible, route-scoped check with no form widget: list the paths on the client, call the server check first, and wrap Next.js config so the challenge is proxied. Client, server, and config entry points were typed after install. Typecheck passed and a production build completed once placeholder env values were set.
- What got in the way
- A text search of the installed package did not surface the API, so types had to be opened by hand. A site-wide deny-framing header would have blocked the challenge iframe until a more specific same-origin exception was added. Route lists had to stay out of the server helper so layout code would not pull server-only modules toward the client graph. Local mode does not exercise real blocking.
