feat(seer): add validate_llm_proxy_key RPC endpoint#117885
Merged
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
Pass-through endpoint that always returns {"valid": true}. This
validates the custom auth hook → getsentry RPC flow for the llm-proxy
before adding real key validation logic.
Registered in seer_method_registry, accessible at:
POST /api/0/internal/seer-rpc/validate_llm_proxy_key/
AIML-2931
sehr-m
force-pushed
the
sehrm/llm-proxy-validate-key
branch
from
6c7895d to
7794f60
Compare
Verifies the endpoint is reachable via HMAC auth and returns
{"valid": true}.
AIML-2931
ellisonmarks
approved these changes
Jun 17, 2026
sehr-m
added a commit
that referenced
this pull request
Jun 23, 2026
## Summary
- Adds `validate_llm_proxy_key` to `seer_method_registry` in
`seer_rpc.py`
- Pass-through that always returns `{"valid": true}` — validates the RPC
flow before adding real key logic
- Accessible at `POST /api/0/internal/seer-rpc/validate_llm_proxy_key/`
- Authenticated via existing `SeerRpcSignatureAuthentication` (HMAC
shared secret)
## Context
The llm-proxy's custom auth hook will call this endpoint to validate API
keys on every LLM request (with caching). This PR proves the endpoint is
reachable and the contract works. Real key validation (new table,
subscription checks) comes next.
## Test plan
- [ ] Validated locally with mock getsentry returning `{"valid": true}`
— full flow works
- [ ] Existing seer RPC tests still pass
Linear: AIML-2931
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
2 participants
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
validate_llm_proxy_keytoseer_method_registryinseer_rpc.py{"valid": true}— validates the RPC flow before adding real key logicPOST /api/0/internal/seer-rpc/validate_llm_proxy_key/SeerRpcSignatureAuthentication(HMAC shared secret)Context
The llm-proxy's custom auth hook will call this endpoint to validate API keys on every LLM request (with caching). This PR proves the endpoint is reachable and the contract works. Real key validation (new table, subscription checks) comes next.
Test plan
{"valid": true}— full flow worksLinear: AIML-2931
🤖 Generated with Claude Code