Versioning and agent compatibility

The public API is versioned under /v1. Control and data origins are separate, and the data URL returned with an access token is authoritative for that token. The API description can document an endpoint before it ships; the API reference lists only operations you can call at launch.

Compatible clients

Use UTF-8 JSON and UTC RFC 3339 timestamps. Ignore unknown response fields, while validating the fields your application relies on. Monetary values carry both a six-decimal USD string and an exactly equal integer micro-USD value; preserve that equality rather than rounding through a binary float. Resource IDs are opaque and cannot substitute for account authorization.

Features not available at launch

Recording, signed large-file URLs, the accessibility tree, outgoing webhooks and forking a running computer are not available at launch. Their endpoints are not part of the public API reference and return 404 not_found if called. Honest limits lists what is and is not included.

Packages

The Python (computeengines) and TypeScript (@computeengines/agent-computers) SDKs and the cec command line are not installable yet; they will be available when the beta opens. See Status.

Compatibility window

The versioning contract allows additive changes within v1. A future v2 would have at least six months of overlap and use Deprecation and Sunset response headers. Supported agent versions are the current version plus the preceding two; unsupported versions return 409 agent_outdated. See the changelog.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.