feature: AgentCards offering incorrect URL

[esnible]

Feature Description

The agent cards are offering an incorrect URL. Typically "url":"http://0.0.0.0:8000/".

Kagenti ignores this but other A2A clients, such as the A2A inspector use the URL.

It isn't possible for this to be fixed entirely in the agent implementation, because agents don't know where they are deployed. Kagenti knows. (A separate issue will be opened for that.)

Proposed Solution

Kagenti should supply env vars to each agent, so that agents can advertise the correct agent endpoint.

Want to contribute?

• I would like to work on this issue.

Additional Context

I asked Claude, and it said the common pitfalls with Agent Card URLs are

• Hardcoding 0.0.0.0 — works locally but breaks remote discovery
• Hardcoding localhost — works in dev but breaks in Docker/k8s where the caller is on a different host
• Mismatch between card URL and actual endpoint — if the url in the card doesn't match where your server actually listens, clients will fail to connect