Skip to main content
POST
Deploy alignment infrastructure inside your own cloud or cluster

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Register a cloud environment or an existing cluster to run in.

Only the name, the mode and the cloud block are required. Every other section is accepted as given and stored verbatim, so an environment can pin any detail without the public schema enumerating every knob.

cluster_name
string
required

Name for this environment, used across status, logging and billing.

Example:

"prod-alignment-cluster"

mode
enum<string>
required

managed_provisioning builds a hardened Kubernetes environment from a clean cloud subscription. cluster_import deploys the alignment and serving stack into a cluster you already run.

Available options:
managed_provisioning,
cluster_import
cloud
Cloud · object
required

Provider, region and the stored credential reference. Determines which provisioning blueprints and identity paths are used.

cluster_import
Cluster Import · object | null

Kubeconfig reference, endpoint, namespace and node labels. Required when mode is cluster_import.

config
Config · object | null

Optional settings for gpu, networking, storage, iam, registry, operations, capabilities, compliance, overflow and notifications. Egress is restricted and traffic is private by default, and anything omitted resolves to auto.

Response

Bring your own cloud request accepted and recorded.

Acknowledgement of a bring your own cloud request.

cluster_id
string
required

Identifier of this environment.

cluster_name
string
required

Name given to the environment.

status
string
required

Request status.

message
string
required

Human-readable outcome of the request.