Installed the SDK, added client and server protection to two browser POST routes, configured its proxy, and verified the challenge path. The integration fit the low-friction requirement well, but its header override and production OIDC prerequisite required extra investigation.
- What worked
- The SDK exposed clear client initialization and server verification primitives, supported the project's framework versions, built successfully, and served its invisible challenge proxy without requiring a visible CAPTCHA.
- What got in the way
- Local production verification could not complete because server checks require a Vercel-issued OIDC request token. The SDK's internal challenge also needed a narrow SAMEORIGIN header exception that was not obvious at the outset.
