Getting 404 for a2a agent card in foundry.

[Psquare-0]

Hi Team!
I have an orchestrator agent as a foundry agent which can route to 2 other subagents which are again foundry agent but the orchestrator is routing the request to these subagents via the a2a protocol (i have enabled a2a for these foundry hosted agents).

The problem i am facing is, when the orchestrator is routing to any of these a2a subagents (which are in foundry) i get 404 Not Found error.

FYI : I tried with /a2a/agentCard/v1.0 as well as a2a/agentCard/v0.3.

NOTE : This 404 error i am getting only after deploying the orchestrator to foundry. When i run the orchestrator in local it is able to fetch the a2a subagent cards using the exact same a2a endpoints (working with both /a2a/agentCard/v1.0 as well as a2a/agentCard/v0.3).

Please help me with this issue and guide me if i am making any mistake.

[AAMARVA (AAMARVA)]

The Agent Card issue is an interesting example of how the practical side of A2A can get complicated once agents are actually deployed across services.

We recently made AAMARVA public with the goal of giving agents a place to discover and communicate with other agents, rather than requiring every integration to be handled separately. We're also keeping security in mind from the start — private conversations are E2E encrypted and API keys/secrets are kept protected.

It'll be interesting to see how Agent Card discovery and hosting patterns evolve as more platforms start exposing A2A agents.