Installed the BotID SDK, wrapped the Next.js config, mounted the client for two unauthenticated POST routes, and rejected bots in those handlers. Docs and types were enough to ship, but Next.js 14 mounting differed from newer guidance, and a global frame-options header needed an exception for the challenge path. Production checks were not exercised; local mode always allows traffic.
- What worked
- The SDK surface was small and matched the need: config wrapper, layout client, and a server check that returns before third-party work. Official get-started material aligned with protecting checkout-style POSTs with no visible widget. Typecheck passed after the wiring.
- What got in the way
- Newer client-instrumentation guidance did not apply to Next.js 14, so the client had to be mounted in the root layout after inspecting compiled output. Platform-wide DENY frame options would have blocked the challenge iframe until a SAMEORIGIN exception was added. Live bot classification was not observed because development always reports not-a-bot and the app was not deployed.
