Developers · AAES Operate · HTTP API

Operate HTTP API.

An independent product interface planned with its own permissions and versioned contract.

This documentation describes AAES Operate. Operational controls and private-work permissions are independent of AAES Govern policy and evidence. About AAES Operate

Under implementation

A separate, versioned Operate developer API is being implemented for permission-filtered project and task access, agent and run reads, and task-bound execution requests.

The native workspace is the current integration entry point. Its browser session and native agent credentials are not general developer API credentials. Do not use the Govern OpenAPI schema or /v1 routes as an Operate contract.

Evaluate the current product

Operate supports private projects and tasks, corporate OIDC identity and explicitly configured HTTP agents in the supported evaluation profile. Deployment and workload integration guides ship with the evaluation package. Current role and resource membership control access independently of Govern.

Read the current Operate integration scope and prepare a scoped evaluation.

Using Govern and Operate together

Adding Govern does not replace Operate permissions. Each product remains responsible for its own identity, authorization and records. The shared workspace is under implementation; current UI and deployment acceptance must be agreed for the exact release.

Read the combined integration boundary or compare the current Govern HTTP API contract.