> ## Documentation Index
> Fetch the complete documentation index at: https://java.agentscope.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SDK and component selection

[简体中文](/v2/zh/service/integrations)

Before selecting an SDK, distinguish invoking a capability from connecting a runtime. An application calling an Endpoint needs an HTTP client, not runtime instrumentation.

| Goal                                    | Component                                    | Continue                                               |
| --------------------------------------- | -------------------------------------------- | ------------------------------------------------------ |
| Invoke an Agent, Team or Workflow       | HTTP client                                  | [Endpoints](/v2/en/service/endpoints)                  |
| Register a Java application             | `io.agentscope:agentscope-extensions-aistio` | [External Agents](/v2/en/service/external-agent)       |
| Connect a Python framework through ASDP | `aistio-sdk`                                 | [External Agents](/v2/en/service/external-agent)       |
| Connect DeepSeek Harness                | `@agentscope/dsh-aistio` plugin              | Configure the plugin, HTTP contract and ASDP addresses |
| Connect a local Coding Agent            | `agentscope` CLI and Runtime Host            | [Hosted Agents](/v2/en/service/hosted-agent)           |

## Packages and versions

Service, Java, Python and DSH packages have independent versions. Use `release-manifest.json` to select matching artifacts rather than copying the image version into every package manager.

```bash theme={null}
python -m pip install "aistio-sdk==$AISTIO_SDK_VERSION"
npm install "@agentscope/dsh-aistio@$DSH_AISTIO_VERSION"
```

Run these in the corresponding application with versions from the manifest. Installing the DSH npm package only supplies plugin files. Add it to your DSH profile and configure control-plane HTTP, ASDP gRPC and a reachable contract address. DSH retains provider login and application lifecycle.

## Verify transport and capabilities

Complete Service uses standalone HTTP; Java offers HTTP registration and contracts. ASDP integrations additionally need an enabled listener. Python automatic registration depends on ASDP, so disabling gRPC does not replace this prerequisite.

Verify catalog identity, then Sessions/history, then supported dispatch, cancellation and reporting. Extend custom frameworks through adapters; changing a framework name alone does not add capabilities. See [External Agents](/v2/en/service/external-agent) for code, credentials and connectivity.