Remote
Connect AgentOS to remote agents, teams, workflows, A2A endpoints, and gateway instances.
| Example | Description |
|---|---|
| Remote Agent | Call an agent hosted on another AgentOS with RemoteAgent in single-shot or streaming mode. |
| Remote Team and Workflow | RemoteTeam and RemoteWorkflow use the native AgentOS protocol while returning typed Agno Team and Workflow outputs to the caller. |
| Call Agno and Google ADK Agents through A2A | The Agno peer uses entity-scoped REST routes while Google ADK uses JSON-RPC at the server root. |
| Compose AgentOS and A2A RemoteAgents in one Team | A local Team can coordinate remote members reached through different protocols. |
| Serve one AgentOS gateway over local and remote components | The gateway registers a local Agent alongside native AgentOS, Agno A2A REST, and Google ADK JSON-RPC components. |
| Authenticate a RemoteAgent run with a Bearer credential | Restart the native AgentOS backend with OS_SECURITY_KEY set, then pass that same value through RemoteAgent.arun(auth_token=...). |
| Serve an Agno Agent through the A2A REST interface | This server is the first-party A2A peer used by RemoteAgent. |
| Serve a Google ADK Agent through A2A JSON-RPC | Google ADK exposes one Agent as a standard A2A JSON-RPC application. |
| Serve Agents, a Team, and a Workflow for Remote* examples | This AgentOS is the native-protocol backend for the remote curriculum. |