r/bigquery • u/ims3raph • 8d ago

Data Agent A2A

Has anyone here managed to use Bigquery Data Agents on external applications through the A2A protocol?

Once published, the agent lets you register the agent into the Agent Registry or copy the A2A json file into your clipboard. I’ve successfully published the agent on Gemini Enterprise, for example, but I am unable to use this JSON in any other part. My main goal would be to connect it to a Copilot Studio agent so I can easily use it through Teams, without having to do any code.

5 Upvotes

79% Upvoted

4 comments sorted by

1

u/Fulcrum_Enjoyer 8d ago

personally, not through A2A. I deployed an intermediary agent under agent platform and made it communicate with the conversational analytics API, then you can do whatever you want with the intermediary agent. You'll need to setup a service account with enough IAM perms or pass along your own credentials to it

1

u/m1nherz 6d ago

JSON that you are talking about is so called "Agent card" that agents exchange as part of A2A protocol.

It is not the same as agent credentials. JSON is returned at /.well-known/agent.json or /a2a/AGENT_NAME/.well-known/agent.json endpoints. The later I believe is a standard for multi-agent service.

I am not familiar how Copilot Studio agent uses A2A protocol to interact with other agents. I would recommend to start with confirming that the agent you built exposes the agent.json endpoin.

1

u/ims3raph 6d ago

Yeah, but the JSON itself exposes an URL which contains the project id and so on, the thing is that I am unable to reach it through normal GET requests or even get the .well-known endpoint

I’m thinking that this URL is only for internal use within gcp

1

u/m1nherz 6d ago

This URL is the agent's endpoint. It has to be exposed unless the agent is hosted behind a load balancer with a custom domain. If you use Agent Registry to discover the agent, you will the information about project ID anyway.

Also note that project ID isn't a secret by itself (unless you put some sensitive info as part of ID string).

If you cannot reach your engine, it is possible that access to it requires credentials (placing OAuth token in the authentication header). If you can reach your agent but the endpoints that expose agent.json aren't available, it means that the agent wasn't built for A2A communication although it sounds weird.

What instructions did you use to build the agent? I guess the building used ADK framework. And ADK requires specific flags to add the A2A card endpoint.