• Building agents with the ADK and the new Interactions API Facebook Twitter LinkedIn Mail The landscape of AI development is shifting from stateless request-response cycles to stateful, multi-turn agentic workflows. • With the beta launch of theInteractions API, Google is providing a unified interface designed specifically for this new era-offering a single gateway to both raw models and the fully managedGemini Deep Research Agent. • For developers already working with theAgent Development Kit (ADK)and theAgent2Agent (A2A)protocol, this raises an exciting question:How does this new API fit into my existing ecosystem? • The answer is two-fold. • The Interactions API acts as both an alternative to the existinggenerateContentinference API endpoint and as a powerful primitive you can usewithinan existing agent framework. • In this post, we’ll explore two primary patterns for integration: Powering your ADK Agents:Using the Interactions API as the inference engine for your custom agents.

Article Summaries:

  • Google has launched a beta Interactions API that unifies access to raw Gemini models and the managed Gemini Deep Research Agent, targeting the shift toward stateful, multi‑turn agent workflows. The API can replace the traditional generateContent endpoint and serves as a powerful primitive inside existing Agent Development Kit (ADK) agents. By enabling use_interactions_api, ADK agents offload context management to the server, receive an interaction ID, and can poll asynchronously, reducing boilerplate and timeout risks. Additionally, the new InteractionsApiTransport maps the Agent‑to‑Agent (A2A) protocol directly onto the Interactions API, letting current A2A clients treat a Google‑hosted agent as any other remote agent without custom adapters.
  • Google has launched a beta Interactions API that unifies access to raw Gemini models and the managed Gemini Deep Research Agent, targeting the shift toward stateful, multi‑turn agent workflows. The API can replace the traditional generateContent endpoint or be used as a primitive inside existing Agent Development Kit (ADK) agents. By enabling use_interactions_api, ADK agents offload context management to the server, receive an interaction ID, and can poll asynchronously, reducing client‑side boilerplate. Additionally, the InteractionsApiTransport maps the Agent2Agent (A2A) protocol onto the Interactions API, letting existing A2A clients treat a Google‑hosted agent as a regular remote agent without custom adapters.

Sources: