Available Packages
| Package | Purpose |
|---|---|
aion-sdk | Starts local agent processes, the proxy, and developer tools such as aion serve and aion chat. |
aion-server | Hosts A2A-compatible HTTP endpoints for configured agents and loads framework server integrations. |
aion-server-langgraph | LangGraph server integration for execution, checkpointing, and request mapping. |
aion-server-adk | Google ADK server integration for execution, sessions, and request mapping. |
aion-api-client | API access and typed control-plane addressing models. |
aion-mcp | Authenticated MCP endpoints for Aion MCP servers. |
aion-agent-sdk | Shared authoring primitives for Aion-aware agents and framework-agnostic models. |
aion-adk | Google ADK model helpers for Aion’s model service. |
aion-authoring-adk | Google ADK MCP authoring helpers. |
aion-authoring-langgraph | LangGraph helpers for MCP, streaming, and event routing. |
Runtime Architecture
- Each configured agent runs in its own server process.
- A proxy server starts automatically and exposes unified routing at
/agents/{agent_id}/{path}. - Clients can call either direct agent endpoints or proxy endpoints.
Framework Support
- LangGraph authoring guidance lives in the dedicated
LangGraphsection. - LangGraph server integration details remain in
Framework Adapters, including checkpointing and message mapping. - Package-level API reference pages live under
Packages, includingaion-api-clientandaion-mcp. - ADK support focuses on
BaseAgentexecution with pluggable session backends. - Adapter discovery is plugin-based, allowing additional framework adapters over time.
Configuration Model
aion.yamldefines agent identities, import paths, framework targets, capabilities, and skills.- Environment variables provide API credentials, logging settings, and persistence settings.
- Runtime ports are allocated automatically unless explicitly configured via CLI options.