Ship live agent-backed product runtimes.
Let humans or agents deploy always-available agent systems for APIs, embedded assistants, operational copilots, and workflow services that keep project context connected.
Start now
Deploy long-lived agent-backed services that stay available beyond a single thread or chat session.
Expose agent APIs, embedded assistants, operational copilots, and workflow runtimes as product surfaces.
Bind runtimes to web apps, functions, databases, auth modules, secrets, and project context.
Inspect deployments, logs, analytics, files, runtime config, and bindings from one resource surface.
Pricing
Agent runtimes are the live product surface for long-running agent systems, embedded copilots, and agent APIs.
| Agent runtime | 0.3 CT / live minute Billed while the runtime stays deployed and available. |
|---|---|
| Build computer | Normal computer usage applies The computer that prepares source files or project context keeps its own runtime pricing. |
| Connected resources | Normal resource usage applies Web apps, functions, databases, auth modules, and secrets keep their own pricing model. |
SDK functionality
The JavaScript and Python SDKs expose the full agent runtime lifecycle: creation, deployment, rollback, invocation, analytics, logs, bindings, files, context, runtime config, and secrets.
| Lifecycle | Create, list, get, update, and delete the resource through the product manager or the generic resources manager. |
|---|---|
| Deployments | Deploy, list deployment history, and roll back to a previous deployment from JavaScript or Python. |
| Invocation | Invoke live routes directly from the SDK for health checks, smoke tests, backend calls, and CI workflows. |
| Operations | Read analytics, request logs, runtime logs, runtime config, and deployed runtime state from one resource surface. |
| Bindings | List, create, update, and remove bindings to databases, auth modules, secrets, web apps, functions, and runtimes. |
| Files | List, read, write, upload, download, and delete files that belong to the deployed resource. |
| Secrets | List, create, read, update, and delete secrets scoped to the resource without checking values into source files. |
How to set it up
Start from the workflow that fits the product: script runtime infrastructure with the SDK, operate directly in Develop, or ask an agent to build and ship the service.
Via SDK
Create, deploy, invoke, inspect, bind, and update agent runtimes from JavaScript or Python.
On the platform
Create an Agent Runtime resource in Develop, choose the source computer and folder, connect dependencies, and deploy.
By agent
Ask a project agent to build the runtime, connect project resources, deploy it, and validate the live behavior.
How to deploy
A deployment turns runtime source in a computer or project workspace into a live agent-backed service endpoint.
| Define the runtime role | Decide whether the runtime is an embedded assistant, agent API, operational copilot, or workflow service. |
|---|---|
| Prepare source files | Create the runtime entrypoint, request contract, health route, and any local project instructions it needs. |
| Create the resource | Point the runtime at a source computer, source folder, and nodejs22 runtime. |
| Bind dependencies | Attach databases, auth modules, secrets, web apps, functions, and project resources the runtime needs. |
| Deploy and verify | Deploy the runtime, run a health check, invoke a representative payload, and document the live endpoint. |
How to manage
Agent runtimes are live product surfaces. Keep logs, analytics, bindings, context, runtime configuration, and source files visible as the system evolves.
| Analytics | Track requests, active usage, errors, latency, and runtime behavior over time. |
|---|---|
| Logs | Use request and runtime logs to debug prompt inputs, tool calls, dependency failures, and external APIs. |
| Runtime state | Inspect runtime configuration, context, source files, and deployed state when agents modify behavior. |
| Bindings | Review connected databases, auth modules, secrets, functions, and web apps before changing contracts. |
| Smoke tests | Invoke the runtime from the SDK after deployment and after every significant source or context change. |