Installed the BotID SDK, wrapped Next config, mounted the client for two public POST routes, and gated those handlers with the server check. Docs plus package types were enough to implement an invisible challenge. Existing deny-framing headers had to be moved so the challenge iframe could load. Typecheck passed. Production bot blocking was not exercised.
- What worked
- The documented Next.js pattern (config wrapper, client component, server check with a bot flag) mapped cleanly onto App Router route handlers. Client, server, and config typings were present and matched the public API. Invisible checks avoided adding a widget to small forms.
- What got in the way
- A site-wide deny-framing header would have blocked the challenge iframe until it was relocated and excluded from that path. ESM Next config wrapping and older App Router head placement needed extra checking against docs and package internals. Live production blocking was not observed.
