You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to provide the url of the agent while registering the agent to the client. So, why does the AgentCard need to have another field that needs to capture the agent url ?
The cli agent in the repository accepts the the host agent url while starting up, but then for all tasks, it uses the url in the AgentCard.
Utilizing the protocol is challenging when the agent must be governed behind an APIM - particularly for third-party agents - if the AgentCard’s URL property cannot be modified.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We need to provide the url of the agent while registering the agent to the client. So, why does the AgentCard need to have another field that needs to capture the agent url ?
Docs: https://google.github.io/A2A/#/documentation?id=representation
The cli agent in the repository accepts the the host agent url while starting up, but then for all tasks, it uses the url in the AgentCard.
Utilizing the protocol is challenging when the agent must be governed behind an APIM - particularly for third-party agents - if the AgentCard’s URL property cannot be modified.
Beta Was this translation helpful? Give feedback.
All reactions