Repository navigation
fix(zen): authenticate System One requests with bearer tokens - #59
Merged
Merged
Conversation
Zen's System One route reads Authorization rather than the x-api-key header used by the Messages route. Send the key as a bearer token while preserving model selection and permission failure behavior.
Merged
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.
Fixes #55. Use the authentication header Zen expects:
Models and permission behavior stay unchanged. Adds regression tests and a patch changeset.
Verification
npm run checknpm run smoke:packagenpm run smoke:opencodejev-1.13jev-1.13-freeRetry-After: 74037seconds; inference unverifiedOne paid request and two separately authorized free requests. No automatic retries or calibration claims.