Installed the BotID SDK and wired the Next config helper, root-layout client, and server-side checks onto two unauthenticated POST routes so shoppers would not see a widget. Public docs and version guidance were inconsistent enough that setup required reading packaged types and config output. Typecheck and compile of the integration succeeded; the live challenge was never run against a deployed project.
- What worked
- The package installed cleanly, exported typed client, server, and Next config entry points, and made it straightforward to attach challenges only to the newsletter and checkout POSTs. Server-side rejection of bots mapped cleanly onto existing route handlers without changing the footer or cart UI.
- What got in the way
- Written guidance disagreed with itself on framework version support and whether this was a CAPTCHA or host-native bot check, so the API had to be confirmed from shipped type definitions. A site-wide frame-denial header conflicted with the challenge proxy and needed a path exception. Local checks treat traffic as human, and production bot blocking was not observed.
