Add Browser Keys customer doc (website-restricted frontend keys)#26
Merged
Conversation
New /auth/browser-keys page documenting the UI-API-key posture: restrict a key to your site's domains (exact + *. wildcard, up to 20), call it from the browser (Bearer or ?apiKey=, CORS verified live), per-key rate cap + rotation, and the forgeability caveat (quota-abuse threat model, not account compromise). Wired into rpcSidebar after auth/index and cross-linked from /auth. Notes that website restrictions are a paid-plan feature. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The indexing-surface audit enforces EN<->ru page parity; the new /auth/browser-keys page needs a ru counterpart or the ru site-graph is one page short (CI: "site-graph.json should contain 184 pages for ru, got 183"). Full translation following the RU glossary + terminology rules. Verified locally: audit:ru-terminology + audit:i18n:all clean, build + indexing audit green (184 ru pages). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying builder-docs with
|
| Latest commit: |
6f25b81
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://17afd828.builder-docs.pages.dev |
| Branch Preview URL: | https://browser-keys-docs.builder-docs.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New /auth/browser-keys page documenting the UI-API-key posture: restrict a key to your site's domains (exact + *. wildcard, up to 20), call it from the browser (Bearer or ?apiKey=, CORS verified live), per-key rate cap + rotation, and the forgeability caveat (quota-abuse threat model, not account compromise). Wired into rpcSidebar after auth/index and cross-linked from /auth. Notes that website restrictions are a paid-plan feature.