Back to all discussions

  •   8 days ago

[Q for Arize & Google team] Clarification required for using Google Agent Builder vs ADK for Arize track

Hello, thank you for organizing this hackathon! I needed some clarity regarding:
the overview pages says "Build a functional agent—powered by Gemini and Google Cloud Agent Builder" (specifically using Agent Builder)
But Arize track overview says "The visual Agent Builder alone is not supported for tracing integration. You must be able to instrument your code directly"

- Is it okay to use ADK + Cloud Run only and integrate with Arize
- Will not using Agent Builder risk/compromize my position in hackathon?

  • 2 comments

  • Manager   •   8 days ago

    Hi Aditya, great question — this is fully addressed in our Participant FAQ (https://rapid-agent.devpost.com/details/faq). Short answer: yes, building with ADK only (the code-first path) is fully supported and won't risk your eligibility. The Agent Builder requirement covers both the visual Studio console and the code-first ADK / Agent Runtime / Cloud Run path — they're equivalent. For the Arize track specifically, the ADK path is actually the recommended one because Arize's tracing requires code-owned instrumentation. See the "What agent architecture is required?" Q in the FAQ for the full breakdown.

  •   •   7 days ago

    Thank you for clarifying!

Log in or sign up for Devpost to join the conversation.