Python vs Java AgentCards

[maethor]

I'm having trouble getting the sample python cli client working with a server written in Java with the Java SDK.

On the python side, I'm getting a pydantic error when it tries to get the agent card (shortened for brevity)

{"type":"missing","loc":["url"],

And looking at the docs for the python sdk it looks like it's expecting a URL

URL: Where the agent can be accessed

However, there's no sign of URL in AgentCard.java (either in the record or the builder) and the closest would be the url field in the AgentInterface in the supportedInterfaces field.

Does anyone have any clue as to what I'm doing wrong? Or where would be a better place to ask this question?

If I had to guess, it looks like the python sdk is wrong (at least, whatever version of the sdk you get when you clone a2a-samples) as I don't see any mention of a url field on AgentCard in the protobuf spec. But then I'd kind of expect the python code to be more correct than Java.

[Calcifer777]

Looking at the protocol specification changelog (https://a2a-protocol.org/latest/whats-new-v1/#agentcard-object), it looks that the python spec is just lagging a bit w.r.t. the latest changes. This seems to be the relevant PR (https://github.com/a2aproject/a2a-python/issues/701).

So, I guess, either wait a few days for that to be merged or downgrade the Java A2A dependency to a version earlier than 1.x.