feat: Add publisher authorization discovery API #54
+668
−0
Conversation
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
Implement two approaches for discovering which publishers have authorized an agent: 1. "Pull" approach: fetch_agent_authorizations() - Check publisher adagents.json files in parallel to see which ones authorize your agent, extracting property IDs and tags. 2. "Push" approach: ADCPClient.list_authorized_properties() - Ask the agent directly what publishers it represents (already existed, now documented). Add AuthorizationContext class to encapsulate authorization info (property IDs, tags, raw property data). Includes comprehensive tests covering success, failure, filtering, and connection pooling scenarios. Resolves #53 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Remove separate AUTHORIZATION_DISCOVERY.md file and integrate content into README as a subsection under Publisher Authorization Validation. Keeps documentation consolidated in a single location. 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Nov 18, 2025
* feat: Add publisher authorization discovery API Implement two approaches for discovering which publishers have authorized an agent: 1. "Pull" approach: fetch_agent_authorizations() - Check publisher adagents.json files in parallel to see which ones authorize your agent, extracting property IDs and tags. 2. "Push" approach: ADCPClient.list_authorized_properties() - Ask the agent directly what publishers it represents (already existed, now documented). Add AuthorizationContext class to encapsulate authorization info (property IDs, tags, raw property data). Includes comprehensive tests covering success, failure, filtering, and connection pooling scenarios. Resolves #53 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * docs: Move authorization discovery to README Remove separate AUTHORIZATION_DISCOVERY.md file and integrate content into README as a subsection under Publisher Authorization Validation. Keeps documentation consolidated in a single location. 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
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
Implement two approaches for discovering which publishers have authorized an agent:
fetch_agent_authorizations()checks publisheradagents.jsonfiles in parallel to extract property IDs and tagsADCPClient.list_authorized_properties()asks the agent what it's authorized forAdds
AuthorizationContextclass to encapsulate authorization info with comprehensive tests.Test Plan
🤖 Generated with Claude Code