Harden text and audio API for authenticated clients - #86
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
Deployment and integration documentation are in stacked PR #87. Merge this PR first, then retarget #87 to main. The combined changes passed local container startup, real Redis quota enforcement across HTTP/WebSocket, and real FFmpeg decoding smoke checks; live provider/model acceptance checks are documented separately. |
This branch was successfully deployed
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
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.
Summary
Migration
All analysis routes now require Authorization: Bearer . Configure SCAMSHIELD_API_KEYS with random tokens of at least 32 characters plus DEEPSEEK_API_KEY. Upgrade Redis to 7+. Clients sharing a token share its quota; browser extensions must use a user-authenticated backend rather than embed these tokens.
The deployment/docs PR will stack on this change and supply the production server settings required for transport-level WebSocket limits, Docker Compose, and rollout guidance.
Verification