Proposal: Implement A2A Agent Registrar for Curated Agent Discovery(Registry-Based)#296
Proposal: Implement A2A Agent Registrar for Curated Agent Discovery(Registry-Based)#296liuzengh wants to merge 34 commits intoa2aproject:gh-pagesfrom
Conversation
Fixes for broken links
Remove "to"
Remove extra word on a2a_and_mcp.md
Replace all occurrences of "Open API" with "OpenAPI"
Just fixing 1 typo when reviewing the full page. See commit diff for details
Hi, just fixing 2 typos on this page after reviewing it in full. See commit diff for details.
Fixing 2 typos in this file after reviewing it in details.
Hi, Fixing diverse typos in the main doc page after extensively reviewing it. See commit diffs for details. Didier
This commit introduces a comprehensive design for the Discovery Agent, including its capabilities, authentication requirements, and JSON-based interaction examples. The added content covers agent registration, discovery, and analytics, providing a clear guide for implementing and using the Discovery Agent in enterprise scenarios.
fixed wrong link in community.md
* Add CONTRIBUTING.md with developing instructions to run a local http server * Python tutorial introduction * Add 3_create_a_project.md for the python tutorial * python tutorial: 4_agent_skills and 5_add_agent_card * python tutorial: task_manager and 6_start_server.md * Start 7_interact_with_server.md for the python tutorial * syntax fixes and add true outputs for lessons 3,4,5,6,7 * Add 8_agent_capabilities to the python tutorial * Add 9_ollama_agent.md for the python tutorial * Finish python tutorial with next steps
- Organization Management - Agent Registry - Agent Discovery
| "data": { | ||
| "registrationStatus": "success", | ||
| "organizationID": "organization-fintech-123", | ||
| "organizationToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...", |
There was a problem hiding this comment.
By looking at all of the request-response examples, I noticed that organizationToken is obtained when registering the organization (no mention of other kinds of tokens), and the same token is used to manage the organization (update, add, and remove agents) as well as to discover non-public agents.
Unless an additional mechanism to issue tokens with limited scope/time is added, I think this "organization registration" response should include another token with read-only permissions. This additional token can then be distributed to the internal clients (e.g., partners, non-dev employees) to allow them to discover private agents.
What do you think?
There was a problem hiding this comment.
The organizationToken is similar to a admin token and can be implemented based on the OAuth Bearer token. Of course, each organization can issue some tokens controlled by RBAC (Role-Based Access Control) to others for use, such as read-only tokens, etc.
There was a problem hiding this comment.
@sandyskies, it makes sense, thanks for the explanation.
# Description Ran prettier Markdown formatting, remove invalid JSON comments
# Conflicts: # topics/agent_discovery.md
github-actions
bot
force-pushed
the
gh-pages
branch
from
b1f5e46 to
ddd7eff
Compare
|
The previously submitted PR was closed because the repository administrator moved the documentation from the gh-pages branch to the main branch via force-push. It has been resubmitted to the main branch by new PR(#418). |
14 participants
close #297