Skip to main content
简体中文 External Agents keep your application’s process, framework and deployment while joining the catalog, Session diagnostics and collaboration. They are neither Service-started Managed Agents nor necessarily Runtime Host providers.

Choose a transport

The standard Service Compose/Helm deployment runs standalone HTTP without ASDP. Python instrument() couples automatic registration to its ASDP connection; start_grpc=False is not a complete HTTP registration path. Ask the administrator for an ASDP-enabled Kubernetes-native Aistio deployment and its real gRPC address when using this integration. Verify three separate levels: catalog visibility, Session functionality and work dispatch. An observation-only adapter does not acquire task execution merely by registering.

Java HTTP integration

Add the published extension version to your application:
This fragment assumes an existing agent. Supply deployment environment variables; the control plane must reach AGENT_CONTRACT_URL:
Use an administrator-provided trusted workload/bootstrap credential for first registration and a registration credential for an existing identity where appropriate. Do not distribute internal component tokens to browsers or ordinary callers. Available contract history and commands depend on the adapter. For event streaming, install adapter middleware while building the Agent and configure ASDP.

Python with ASDP

Install the SDK version selected for your release:
The fragment assumes an existing framework target. Adapters include AgentScope, OpenAI Agents, LangChain and ADK; supported methods differ.
AISTIO_CONTROL_GRPC is host:port, not an HTTP Gateway URL. Use a distinct instance key per replica and stable identity across its restarts. Persist the event journal for recovery.

Execute Issue and Team work

The adapter needs a real task entry point, such as Python FrameworkAdapter.handle_agent_task or Java AgentTaskStarter. Isolate each Attempt, read injected context, use task-scoped credentials for comments and Artifacts, and report success, failure or cancellation through the protocol. A final message is not an Attempt completion report. Never report another execution with a stale generation or credential. Coordinators must explicitly complete or fail their Run node; see Team collaboration.

Extend and verify

Implement Python FrameworkAdapter and pass it through adapter= to add context, messages, commands or task execution. Advertise only implemented capabilities. Java provides FrameworkAdapter and AgentScopeAdapter extension points. Verify registration and restart identity, an application-side conversation, history, contract reachability, supported task dispatch, failure and cancellation. Container localhost, one-way networking, incorrect gRPC ports and inaccurate capabilities are common integration problems. Related: SDK selection · API reference.