auth_test_assist

Parameters

Parameter	Type	Required	Default	Description
`url`	string	Yes	—	The site URL or auth page URL to plan or record auth for
`action`	string	No	`plan`	Use `plan` to get the recommended auth path, or `record` to save what happened
`intent`	string	No	`auto`	Optional hint: `auto`, `sign_in`, or `sign_up`
`loginUrl`	string	No	—	Known login URL for the site
`outcome`	string	No	—	Outcome to save when `action` is `record`
`verification_required`	boolean	No	—	Mark whether the site usually requires email verification
`username`	string	No	—	Username prefix when forcing a fresh inbox
`display_name`	string	No	—	Display name when forcing a fresh inbox
`force_new_inbox`	boolean	No	`false`	Force creation of a brand new inbox
`notes`	string	No	—	Optional note to save with the auth memory

Use auth_test_assist for https://example.com, then follow its recommended auth path.

auth_test_assist is the primary auth planner. It returns:

Call auth_test_assist
If needed, call find_login_page
Try smart_login or browser tools based on the page structure
Use check_inbox for OTP or verification links
Call auth_test_assist again with action: "record" to save what worked
When you report the result, summarize reusable auth-system heuristics first and site-specific evidence second

Start here for website auth testing instead of create_test_inbox
Treat the helper's reusable strategy as the default cross-site guidance, and treat the returned site hints as origin-specific evidence
Reuse the saved primary inbox unless you explicitly need a fresh registration
If sign-in fails because the account does not exist, try sign-up with the same saved credentials
If smart_login is uncertain on Clerk or other multi-step auth UIs, inspect network and console evidence before concluding the login failed