1. Install
google-adk, the Aion authoring toolkit and the A2A server. See
Installation for the other combinations.
2. Define an ADK Agent Module
Createagent_adk.py:
3. Configure aion.yaml
4. Optional: Add Control Plane Credentials to .env
.env only when running outside Aion-hosted deployments or when testing
local control plane connectivity. For more information, see
Environment Variables.
5. Start and Test
6. Optional: Reach for aion.adk.authoring
The agent above runs behind Aion as a plain ADK agent. Reach into
aion.adk.authoring when you want deeper Aion-aware protocol integration in
your agent code — helper APIs, and richer control over how responses are
buffered and mapped back into A2A. It ships with [adk-server], so it is
already importable.
7. Understand Message Mapping
Once the agent is running, Aion will:- accept inbound A2A requests from clients or distributions
- expose the full request through
ctx.aion_runtime_context.inbox - use the SDK response buffer first, then
a2a_outbox, then framework-native fallback to determine the outbound reply - return the final A2A response to the caller or distribution
Next Steps
How the adapter runs an ADK agent behind Aion:- Session Storage — database-backed or in-memory sessions
- Artifact Storage — file artifact backends
- Streaming and Artifacts — real-time text streaming and file artifacts
- Events Reference — A2A events emitted during execution