Installed the BotID package on a Next.js 14 app by wrapping config, mounting the client in the root layout, and calling the server check on two anonymous write handlers before side effects. The get-started guide matched that version, including the layout mount. Confirming header handling meant reading the package types and server bundle. A global framing deny rule would block the challenge iframe, so that path had to be excluded. Install, typecheck, and the production build succeeded. Local dev always treated callers as human and still rendered the challenge script. Live classification runs only on the platform and was not exercised.
- What worked
- The get-started guide named the config wrapper, layout client, and server check for this framework version, and install plus typecheck succeeded. The dev server HTML included the challenge script for the protected routes, and the check can reject a request before downstream side effects.
- What got in the way
- The challenge iframe needs a same-origin framing policy, but a sitewide deny header wins over the SDK setting, so the challenge path had to be carved out by hand. Local development always reports a human verdict, and calls without the client headers logged a misconfiguration warning. A local production-mode check failed closed without the platform identity token, so real classification stayed unverified.
