docs: Clarify opt-in WBA access and improve discovery

[AnnaXWang]

Description

The WBA guide leads with a test-key extension tutorial and doesn't explain who can request the managed WBA token. Add WBA to the title and description, lead with selective opt-in access for Startup and Enterprise plans, and link to the access instructions from the anti-detection overview and stealth guide.

Explain how verifiable identity can reduce challenges and retries on participating sites while preserving site access policies. Keep the test-key and own-key instructions as separate options. Move the complete Bot Anti-Detection navigation group from Advanced to the start of Intermediate without changing page URLs.

Testing

• mint broken-links passes.
• mint dev starts; all three edited pages return HTTP 200 with the new content.
• The rendered request-access heading matches the new cross-links.
• Navigation JSON is valid and all existing navigation entries are preserved.
• git diff main...HEAD --check passes; full diff reviewed.

Existing SDK examples are unchanged and were not executed. Search indexing will occur after publication; hosted search wasn't tested locally.

Implementation checklist

No sample app, CLI, or API changes.

---

Note

Low Risk
Documentation and navigation-only changes with no runtime, API, or SDK behavior impact.

Overview
Documentation updates clarify KERNEL’s Web Bot Auth (WBA) token as a selective, opt-in capability for Startup and Enterprise customers (not default, not automatic with stealth), with a new Request WBA access flow and cross-links from the bot-detection overview and stealth pages.

The WBA guide is reframed to lead with managed-token access and benefits (verifiable identity, fewer challenges on participating sites, site policy limits), while keeping test-key and bring-your-own-keys paths and noting that the public test key does not enable KERNEL’s production identity.

docs.json moves the full Bot Anti-Detection section (including nested Proxies and WBA) from Advanced to the start of Intermediate for easier discovery; page URLs are unchanged.

^{Reviewed by Cursor Bugbot for commit 69e885e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 25, 2026, 4:24 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Risk: Very Low. Approved.

The change is limited to public documentation and sidebar order:

• browsers/bot-detection/overview.mdx, stealth.mdx, and web-bot-auth.mdx update copy about opt-in Web Bot Auth access and add cross-links. No code samples, APIs, or runtime behavior change.
• docs.json moves the existing Bot Anti-Detection navigation group from Advanced to the start of Intermediate. The same page paths stay in place; URLs are unchanged. The JSON still parses.

No application logic, auth, permissions, infrastructure, or schema changes. No CODEOWNERS file, so code owner review is not required. No prior approval on this PR.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Plan details in page intro

Low Severity

The frontmatter description and the paragraph before Request WBA access include plan gating and how to request the managed token. Those details belong in that subsection so the intro stays a high-level orientation on what WBA is.

 

^{Triggered by learned rule: Keep page descriptions and intros high-level — push details into subsections}

^{Reviewed by Cursor Bugbot for commit 01a39b5. Configure here.}

[cursor]

Risk: Very Low. Re-checked after the branch update. Existing approval stands; not approving again.

The pull request diff against main is still documentation and sidebar order only:

• browsers/bot-detection/overview.mdx, stealth.mdx, and web-bot-auth.mdx change copy about opt-in Web Bot Auth access and add cross-links. No code samples, APIs, auth logic, or runtime behavior change.
• docs.json moves the existing Bot Anti-Detection group from Advanced to the start of Intermediate. The same page paths stay in place.

The new commit (9397bfb) only merges main into this branch. Those files are already on main and are not part of this pull request’s unique diff. Risk does not increase, so the prior approval is left in place.

No CODEOWNERS file is present, so code owner review is not required.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[dprevoznik]

LGTM - left one suggestion, but otherwise 🚢 it

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9397bfb. Configure here.}

[cursor]

WBA access policy duplicated

Low Severity

The overview and stealth pages restate WBA opt-in rules, plan eligibility, and access caveats instead of briefly pointing to the canonical Request WBA access section. Those details can drift if the request process changes.

Additional Locations (1)

• browsers/bot-detection/stealth.mdx#L13-L16

 

^{Triggered by learned rule: Single source of truth — no deep content duplication across pages}

^{Reviewed by Cursor Bugbot for commit 9397bfb. Configure here.}

[cursor]

Risk: Very Low. Re-checked after the latest commit. Existing approval stands; not approving again.

The new commit (69e885e) changes one word in browsers/bot-detection/web-bot-auth.mdx: “automate” to “access” in the request-access sentence. The rest of the pull request is unchanged and still limited to public documentation and sidebar order:

• overview.mdx, stealth.mdx, and web-bot-auth.mdx update copy about opt-in Web Bot Auth and add cross-links. No code samples, APIs, auth logic, or runtime behavior change.
• docs.json moves the existing Bot Anti-Detection group from Advanced to the start of Intermediate. The same page paths stay in place.

Risk does not increase, so the prior approval is left in place. No CODEOWNERS file is present, so code owner review is not required.

  

_{Sent by Cursor Automation: Assign PR reviewers}