Operator is the Ωmegas /v1 machine surface: cloud browser devices, the
tasks that drive them, live view with human takeover, usage
metering, webhooks, and the audit trail.
Preview status, stated plainly — Operator is in a closed preview and is not
generally available. API keys are minted per organization by the Ωmegas team
and shown exactly once.In the current preview build, device provisioning, sleep and wake, live-view
session minting, task execution, and task cancellation were exercised end to
end against live infrastructure: a real browser was provisioned through this
API, driven by a submitted task, and returned its result. Webhook delivery to
a receiving endpoint and usage attribution have not passed that bar yet, and
these pages do not claim they have. The rest of the surface is documented from
the same OpenAPI contract the server is checked against, as the contract an
integration can be built against.
The shape of the product
A device is a cloud browser your organization holds: created, slept, woken,
and deleted through the API, egressing from the provider’s datacenter
addresses. A task is a natural-language instruction submitted against one
device. While a task runs, its steps stream as events; when it hits a login,
a captcha, or a two-factor wall, it parks as needs_human and waits for a
person, who can watch the browser live and take over the controls under a
separately scoped permission.
Operator events reach you two ways: signed webhook deliveries your receiver
can verify offline, and the audit trail at GET /v1/audit, which holds the
same records under the same ids for everything that happened while you were
not listening.
What is documented here
- Authentication and scopes: the key format, the
scope table, and the credential-custody rules the client enforces.
- Tasks and event streams: submitting, reading, streaming,
and cancelling, including the routing fact most integrations trip over.
- Live view and takeover: watch and control sessions,
the takeover lease, and why watching genuinely cannot type.
- Webhooks: signature verification, replay handling,
and what your response codes do to your endpoint.
- Errors and conventions: the error taxonomy,
idempotency, and pagination.
- Limits, stated plainly: properties of what ships
today, not a roadmap.
- The API reference in the sidebar is generated from the OpenAPI document
the Rust API is checked against, so it cannot drift from the deployed
contract.
A zero-dependency TypeScript client (omegas-operator) exists and informs
much of these pages; it is not on a public registry yet. Examples are
therefore shown against the raw HTTP surface, with client snippets where the
client’s behaviour is itself the point.
Request API access
Access is granted per organization, and keys are shown exactly once at mint.
There is no self-serve signup. If your organization wants to build against the
preview, reach the team through an existing Ωmegas channel or through
github.com/OmegaAgent.
