SDKs
ACP documents the SDKs in the same product-first spirit used by platforms like Firebase: one language client, first-class managers for the core product surfaces, and a separate HTTP reference when you need raw transport control. That means you can work with threads, computers, web apps, functions, auth, databases, skills, and automation from one cohesive client instead of stitching together unrelated APIs.
Language SDKs
Use one typed Node and TypeScript client for threads, computers, web apps, functions, auth, databases, skills, and automation.
Use Python for ACP automation, research systems, background jobs, and backend control of threads, computers, resources, and data.
Product guides
ACP now exposes first-class product managers on the SDK itself. Instead of only using a generic resources manager, you can work directly with web apps, functions, auth, databases, and automation surfaces.
Create and resize ACP computers with Lite, Standard, Power, and Desktop profiles from the SDK.
Create, deploy, inspect, and operate published web apps from the SDK.
Create, deploy, invoke, and inspect backend functions from the SDK.
Provision auth modules and manage auth users from the SDK.
Manage databases, collections, and documents from one SDK surface.
Publish always-on agent runtime surfaces and operate them through the SDK.
Publish skills and drive ACP with schedules, triggers, and orchestrations from the SDK.
Capability map
| Surface | JavaScript | Python | Notes |
|---|---|---|---|
| run(), threads, computers, files | Yes | Yes | Core ACP execution, stateful threads, streaming, and workspace state. |
| computer profiles: Lite / Standard / Power / Desktop | Yes | Yes | Named computer sizing presets with profile metadata and runtime pricing. |
| webApps, functions, auth, runtimes | Yes | Yes | First-class product managers over deployed ACP resources. |
| databases, collections, documents | Yes | Yes | Database lifecycle plus nested collection and document CRUD. |
| skills, schedules, triggers, orchestrations | Yes | Yes | Automation and capability surfaces without dropping to raw HTTP. |
| direct HTTP | N/A | N/A | Use the generated API reference for exact transport-level contracts. |
Reference split
Use these SDK guides when you want to understand ACP as a product surface. Move to the API reference when you need exact request and response schemas, raw HTTP transport control, or language-agnostic integration.