Web apps

The SDK manages ACP web apps directly. That means creation, deployment, invocation, analytics, bindings, runtime inspection, and file operations all live on the same product-shaped manager instead of being scattered across generic server helpers.

Pricing

Web app pricing in Compute Tokens

Web apps are billed as a deployed resource surface. The rate applies while the web app stays live, separate from the computer cost that produced the source code.

Web app runtime

0.25 CT / minute

Billed while the web app stays deployed and live.

What web apps are for

Use web apps when ACP should publish an interactive product surface rather than just complete a thread. Typical use cases include dashboards, internal tools, authenticated portals, AI chat apps, and project-backed frontend experiences.

Create from a source path inside a persistent computer or project workspace.

Deploy explicitly and then inspect logs, analytics, runtime state, and bindings from the same manager.

Use bindings to connect the app to auth, databases, and published agent runtimes.

Full web app lifecycle in JavaScript

The JavaScript manager covers the full product lifecycle from creation to cleanup, including deployment, invocation, runtime inspection, bindings, and file operations.

These are the real SDK methods on client.webApps.

Use this as the reference lifecycle when you need exact control over a deployed web app.

Operate a web app end to end

Generate the AI chat web app starter

Full web app lifecycle in Python

Python exposes the same web app lifecycle for backend services, scheduled jobs, and automation control planes.

Use client.web_apps when Python should manage the deployed app surface directly.

The Python examples mirror the same operations as the JavaScript client.

Operate a web app end to end

Generate the AI chat web app starter