Functions

ACP functions are first-class SDK resources. Use them for invocation-based backend logic, product actions, and automation handlers that should not be billed as continuously deployed runtime the way a web app or agent runtime is.

Pricing

Function pricing in Compute Tokens

Functions are billed on active execution time, not simply for existing in your project. That makes them the lightest deployment surface when the workload is bursty or event-driven.

Function runtime

0.1 CT / active execution minute

Invocation-based billing, not a continuous always-on deployment rate.

What functions are for

Use functions when ACP should publish callable backend logic without turning the whole surface into a continuously running app. They work well for webhooks, lightweight APIs, transformations, and event handlers.

Functions are ideal for event-driven or bursty workloads.

Deploy from code already prepared in a computer or project workspace.

Use invoke() from the SDK when you want an end-to-end functional test.

Full function lifecycle in JavaScript

The function manager covers creation, deployment, invocation, observability, bindings, runtime inspection, and resource file operations.

These are the real SDK methods on client.functions.

Use bindings to connect functions to databases, auth, or agent runtimes.

Operate a function end to end

Full function lifecycle in Python

Python exposes the same function lifecycle for service backends, ETL jobs, and automation control planes.

Use client.functions when Python should operate the published backend surface directly.

The Python manager mirrors the same lifecycle operations as JavaScript.

Operate a function end to end