I used the public assessment and policy-challenge documentation to add a score-based check on the admin login form and to mark up the enterprise widget. No client library was installed, and no live call was made, because no site key or project credentials were available. The documented token fields, action and hostname checks, and score threshold were enough to reject bad tokens before password verification, fail open on timeout and server errors, and cover that behavior with mocked tests.
- What worked
- The assessment guide listed the response fields needed for token validity, expected action, hostname, and score. The web instrumentation guide showed how a score key requests a token on submit. Together they were specific enough to implement the server check from the documented contract.
- What got in the way
- The widget and CreateAssessment call were never exercised against the service. The docs also describe more than one browser integration, including execute-on-submit and a button callback for policy challenges, so settling on one client flow took several searches and a second read of the assessment page.
