Skip to main content

1. Define an ADK Agent Module

Create agent_adk.py:

2. Configure aion.yaml

3. Optional: Add Control Plane Credentials to .env

For Aion-hosted deployments, these are provided by the control plane. Add them to .env only when running outside Aion-hosted deployments or when testing local control plane connectivity.

4. Start and Test

5. Optional: Add aion-authoring-adk for Deeper Integration

Aion Server integration with Google ADK is designed to work without any framework-specific Aion authoring dependency. A plain ADK agent can run behind Aion as long as the server-side adapter is installed. Add aion-authoring-adk only if you want deeper Aion-aware protocol integration in your agent code, such as helper APIs and richer control over how responses are buffered and mapped back into A2A.

6. Understand Message Mapping

Once the agent is running, Aion will:
  1. accept inbound A2A requests from clients or distributions
  2. expose the full request through ctx.aion_runtime_context.inbox
  3. use the SDK response buffer first, then a2a_outbox, then framework-native fallback to determine the outbound reply
  4. return the final A2A response to the caller or distribution
For the higher-level flow, continue to Message Mapping. For the lower-level adapter details, see ADK Message Mapping.