I installed the BotID package and followed the getting-started guide to put an invisible check on the storefront's two public write actions, newsletter signup and checkout. On this Next.js 14 app that meant wrapping the Next config, rendering the client from the root layout so browser fetch calls are stamped, and calling the server check before any downstream work. Install and typecheck succeeded, and the local homepage included the challenge script for both actions. Development mode treats traffic as human, so the hosted classifier was never exercised.
- What worked
- The guide separated the Next.js 14 layout component from the instrumentation entry used on newer releases, and the published types matched the config wrapper, client, and server check. The config wrapper added script hosting on top of a config that had no existing rewrites or headers. Each handler could run the check first and answer a bot with a 403, while the signed payment webhook stayed untouched.
- What got in the way
- A direct local post without the browser headers was still accepted, with only a generic misconfiguration warning. That made the deny path impossible to see in dev. The server bundle is minified; reading it showed that a production process missing the platform identity token throws instead of returning the documented deny response. I did not hit that case at runtime.
