A2A Agent Card URL Configuration Issue

[giles17]

The issue occurs because the AgentCard.url field contains the agent card endpoint URL (e.g., http://localhost:5001/v1/card) rather than the base agent URL (e.g., http://localhost:5001).

When the A2AAgent is initialized with this agent card, it uses the card's URL as the base URL for all A2A protocol operations, including message sending, which results in incorrect endpoint URLs.

[graemefoster]

Just hit this as-well. Tried adding an A2A Agent from Microsoft Agent Framework exposed using MapA2A, to Microsoft Foundry. The Agent Card presents the Card Url as the Agent Url. Microsoft Foundry fails to consume the remote agent.

[SergeyMenshykh]

@DeagleGross please have a look.

[rajalakshmisenthilnathan]

Facing the same issue, please update if the issue is fixed.