Installed the BotID package, wrapped the Next.js config, mounted the client helper, and called the server check on two unauthenticated POST handlers so real users never see a widget. Official get-started docs plus package types were enough to wire it. Live dashboard enablement and production bot scoring were not exercised.
- What worked
- The SDK matched the App Router pattern: a config wrapper to proxy the challenge script, a client component that tags fetch calls, and a server check that returns whether the request is a bot. Client, server, and config type definitions were present. Install and typecheck succeeded, and the production compile included the integration without BotID-specific errors.
- What got in the way
- Package exports were not obvious from the top-level readme, so types had to be inspected in the published dist files. A site-wide deny-framing header would conflict with the challenge iframe unless a more specific same-origin rule is added. Local dev treats traffic as human, and the hosted detector was not turned on or scored against real bots in this session.
