Libraries

ACP exposes the same core platform through multiple integration surfaces. Most teams start with the JavaScript or Python SDK, then move to direct HTTP where they need lower-level control or custom transport.

JavaScript / TypeScript

Best for product integrations, web backends, Node services, and agentic applications built around ACP.

First-class client for projects, threads, agents, computers, files, schedules, and triggers.

Best choice when you want typed ACP primitives and event streaming.

Python

Best for data workflows, automation backends, internal tools, and teams already using Python for orchestration.

Python SDK mirrors the core ACP resource model closely.

Works well for scheduled jobs, research workflows, and backend automation.

Direct HTTP

Best when you need full transport control, custom clients, or direct access to the REST API from any language.

Use the API reference when you want exact request and response contracts.

Works for any runtime that can call HTTPS endpoints.

JavaScript / TypeScript

The JavaScript SDK is the fastest path to ACP. It gives you the high-level run() path for quick tasks and the lower-level clients for threads, agents, computers, files, schedules, and triggers.

Install the JavaScript SDK

Run with the JS SDK

Python

Use the Python SDK when ACP is part of a data pipeline, automation backend, or internal operations system. The Python surface is especially useful when scheduled work and stateful thread execution are part of an existing Python stack.

Install the Python SDK

Run with the Python SDK

Direct HTTP

ACP’s REST API mirrors the same platform model as the SDKs. Use direct HTTP when you need exact endpoint control, language-agnostic integration, or tight control over transport and authentication.

Create a thread

Continue in the API reference