Enforce bria_call usage and prefer agent_api_token#42
Open
Levdavid1 wants to merge 2 commits into
Open
Conversation
- Reframe llms.txt reference to mandate bria_call for all API calls so User-Agent header is always applied - Prefer agent_api_token over api_token in credential loading - Store agent_api_token alongside api_token after introspection - Update bria_client.sh to read agent_api_token first Made-with: Cursor
Update the curl call in auth-device-flow.md and SKILL.md to pass client_type so the auth server provisions the correct api key type. Made-with: Cursor
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.
Summary
llms.txtreference to mandatebria_callfor all API calls (ensuresUser-Agent: BriaSkillsheader is always applied)agent_api_tokenoverapi_tokenapi_tokenandagent_api_tokento credentialsagent_api_tokenfirst, falls back toapi_tokenbria_callContext
Agents were sometimes
curl-ing Bria endpoints directly (bypassingbria_call), which omitted theUser-Agentheader and caused agentic calls to go uncounted in dashboards. This PR:bria_callusage soUser-Agentis always presentagent_api_tokenpreference so agent traffic uses a dedicated key typeDepends on bria-internal and spring PRs for the backend AGENT key type.
Test plan
api_tokenandagent_api_tokenbria_callreadsagent_api_tokenwhen presentbria_callfalls back toapi_tokenwhenagent_api_tokenis missingUser-Agent: BriaSkillsheader is sent on everybria_callMade with Cursor