tPj2UdZddlmZmZddlmZmZmZddlm Z ddl m Z m Z ddl mZddlmZmZddlmZmZmZmZdd lmZeZeed <Gd d e ZGd de Zej;ddgeegeeefdedede fdZy)a FastAPI routes for the A2A registration flow. Today this exposes a single endpoint, ``POST /v1/a2a/discover``, used by the LiteLLM UI when an admin registers a new A2A agent: the UI hands us the upstream agent's base URL, we fetch its well-known card, and we return the raw card so the UI can render the agent's skills/capabilities and let the admin pick which ones to expose through the proxy. The actual merge into a LiteLLM-fronted card happens when the agent is saved via ``POST /v1/agents``. )AnyFinal) APIRouterDepends HTTPException) JSONResponse) BaseModelField)verbose_proxy_logger)LitellmUserRolesUserAPIKeyAuth)AGENT_CARD_WELL_KNOWN_PATHSAgentCardDiscoveryError DiscoveryModefetch_well_known_card)user_api_key_authrouterceZdZUedddj edZeed<ee jdZ e ed <ed d Z e eefd zed <y ) DiscoverAgentRequest.zpBase URL of the upstream agent. Behavior depends on ``discovery_mode``: ``well_known_fallback`` (default) tries z, zq under this URL in order; ``langgraph_platform`` hits ``/.well-known/agent-card.json?assistant_id=`` instead.) descriptionurlzHow to locate the upstream card. ``well_known_fallback`` for pure A2A agents (try standard paths); ``langgraph_platform`` for LangGraph Platform deployments where the card is shared across assistants and disambiguated by a query parameter.)defaultrdiscovery_modeNz{Mode-specific parameters. ``langgraph_platform`` requires ``{'assistant_id': }``. ``well_known_fallback`` ignores this.params)__name__ __module__ __qualname__r joinrrstr__annotations__rWELL_KNOWN_FALLBACKrrdictr`/home/oem/CyberBrain26-unified/.venv/lib/python3.12/site-packages/litellm/proxy/a2a/endpoints.pyrrs  Kyy4567J J C %*11  %NM %* P%FDcNT !r$rc,eZdZUeed<eeefed<y)DiscoverAgentResponser agent_cardN)rrrrr r"rr#r$r%r'r'=s HS#Xr$r'z/v1/a2a/discoverz[beta] A2A Agents)tags dependenciesresponse_modelrequestuser_api_key_dictreturncK|jtjk7rtdd|j t |j |j |jd{}t|j |d d S7#t$r}tdt|d}~wt$r+}tjd|tdd |d}~wwxYww) u Fetch the upstream agent's well-known card so the UI can show the admin which skills/capabilities the agent exposes. Only proxy admins can call this — the UI uses it during agent registration, and we don't want arbitrary keys probing internal URLs. Example: ```bash curl -X POST "http://localhost:4000/v1/a2a/discover" \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{"url": "https://upstream-agent.example.com"}' ``` iz6Only proxy admins can discover agent cards. Your role=) status_codedetail)rrNiz)Unexpected error during A2A discovery: %sizDiscovery failed: )rr(zapplication/json)content media_type) user_roler PROXY_ADMINrrrrrrr Exceptionr exceptionr)r,r-cardexcs r%discover_agent_cardr:Bs2""&6&B&BBLM^MhMhLij  P1 KK"11>>    48%  #>CH== P&&'RTWX6H4NOOPsF8C$/B *B +B /C$ B C!B** C!6&CC!!C$N)__doc__typingrrfastapirrrfastapi.responsesrpydanticr r litellm._loggingr litellm.proxy._typesr r litellm.proxy.a2a.discoveryrrrr$litellm.proxy.auth.user_api_key_authrrr rr'postr:r#r$r%rEs 55*%1A C 9<I   +,-(  )00A(B( !(%((  (r$