> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get who runs each environment > Who runs it: for each of the application's environments, the effective autonomy level (you_run_it, together, ankra_runs_it) in every area, the rule that decided it, and the limits. The stored organisation, application and environment layers apply first; where the organisation layer sets nothing it is seeded from existing settings (auto-remediation policy, Cost Autopilot tier, push-to-deploy) and seeded_from names which. read_state is partial when one of those seeds could not be read and unknown when the environments or the stored policy could not be read, in which case environments is empty and must be rendered as could-not-check, never as no environments. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/applications/{application_id}/autonomy openapi: 3.1.0 info: title: Ankra Platform API version: v1 description: >- The Ankra platform HTTP contract. The /api/v1 surface is the public, bearer-authenticated API used by the Ankra CLI, MCP clients and automation; send a personal or service API token as `Authorization: Bearer `. Browser routes under /org and /chat are served on api.platform.ankra.app (each declares that server); they and /oauth/access authenticate with the ankra_session cookie, and mutations also require the X-Ankra-CSRF header. Every operation declares the credential it accepts, and no operation is served without one. This document is published deliberately: it describes the contract only and carries no organisation data or credentials. Report security issues to security@ankra.ai (see /.well-known/security.txt). servers: - url: https://platform.ankra.app security: - BearerAuth: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: HPE Morpheus Credentials description: HPE Morpheus credentials and the capacity and quotas behind them. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Proxmox Credentials description: Proxmox VE credentials and the capacity and quotas behind them. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/applications/{application_id}/autonomy: get: tags: - Applications summary: Get who runs each environment description: >- Who runs it: for each of the application's environments, the effective autonomy level (you_run_it, together, ankra_runs_it) in every area, the rule that decided it, and the limits. The stored organisation, application and environment layers apply first; where the organisation layer sets nothing it is seeded from existing settings (auto-remediation policy, Cost Autopilot tier, push-to-deploy) and seeded_from names which. read_state is partial when one of those seeds could not be read and unknown when the environments or the stored policy could not be read, in which case environments is empty and must be rendered as could-not-check, never as no environments. operationId: get_application_autonomy_api_v1 parameters: - in: path name: application_id required: true schema: type: string title: Application Id responses: '200': content: application/json: schema: $ref: '#/components/schemas/ApplicationAutonomyResponse' description: Successful Response '404': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: Not found ("Application not found") security: - BearerAuth: [] components: schemas: ApplicationAutonomyResponse: type: object properties: application_id: type: string title: Application Id storage: type: string enum: - seeded - stored - unknown title: Storage description: >- stored: at least one stored layer (organisation, application or one of its environments) applies; seeded: every layer is read from existing settings; unknown: the stored layers could not be read, so read_state is unknown too. Per area, source.layer names the layer that decided it and seeded_from the setting a seed came from. read_state: type: string enum: - ok - partial - unknown title: Read State read_reason: type: string title: Read Reason unread: type: array items: type: string enum: - auto_remediation_policy - cost_autopilot_tier - deploys_on_push title: Unread environments: type: array items: $ref: '#/components/schemas/ApplicationAutonomyEnvironment' title: Environments layers: anyOf: - $ref: '#/components/schemas/ApplicationAutonomyStoredLayers' - type: 'null' description: >- What is stored for the application, the layers a write starts from. null when the stored layers were not read; no write may be built then. choices_take_effect_areas: type: array items: type: string enum: - keep_it_up - ship_changes - keep_it_safe - keep_costs_down - keep_it_current - fix_my_code title: Choices Take Effect Areas description: >- The areas whose stored choice Ankra honours today. The autonomous lane of each consults the stored levels before it acts, holding itself at a lower choice and never acting above its own setting, or, for keep_it_safe, acts only when a person asks, so every stored level already holds. A choice in any other area is stored and shown, but no lane acts on it yet. pause: $ref: '#/components/schemas/ApplicationAutonomyPauseSummary' description: >- Whether a person paused Ankra's autonomous actions for the application, as GET /org/applications/{application_id}/autonomy-pause answers it. Read on its own, so it is answered even when read_state is unknown; its own read_state is unknown, with paused null, when the pause could not be read. limits_editable: type: boolean description: >- The write supports transactional expected-layer comparisons. This is not a claim that automatic lanes enforce limits. required: - application_id - storage - read_state - read_reason - unread - environments - layers - choices_take_effect_areas - pause - limits_editable title: ApplicationAutonomyResponse DemoDetailError: description: >- The FastAPI-style detail envelope the demo routes use for 400/403/404/409/502 responses. properties: detail: type: string required: - detail type: object ApplicationAutonomyEnvironment: type: object properties: environment_id: type: string title: Environment Id name: type: string title: Name role: type: string title: Role environment_kind: type: string enum: - production - staging - preview - playground title: Environment Kind level: type: string enum: - you_run_it - together - ankra_runs_it title: Level is_custom: type: boolean title: Is Custom description: >- Stored policy layers resolve at least one area away from the headline. Platform readiness ceilings alone do not make the policy custom; their limits are reported separately. areas: type: array items: $ref: '#/components/schemas/ApplicationAutonomyArea' title: Areas limits: $ref: '#/components/schemas/ApplicationAutonomyLimits' inherited_limits: $ref: '#/components/schemas/ApplicationAutonomyLimits' description: >- Effective limits with this environment layer removed; used to review following the application again. required: - environment_id - name - role - environment_kind - level - is_custom - areas - limits - inherited_limits title: ApplicationAutonomyEnvironment ApplicationAutonomyStoredLayers: type: object properties: application: anyOf: - $ref: '#/components/schemas/ApplicationAutonomyStoredLayer' - type: 'null' description: The stored application layer; null when none is stored. environments: type: object additionalProperties: $ref: '#/components/schemas/ApplicationAutonomyStoredLayer' description: >- The stored environment layers only, keyed by environment id; an absent key is an environment with no layer of its own. title: Environments required: - application - environments title: ApplicationAutonomyStoredLayers ApplicationAutonomyPauseSummary: type: object properties: read_state: type: string enum: - ok - unknown title: Read State description: >- ok: the pause was read and paused answers it. unknown: the pause could not be read, so paused is null - an application whose pause Ankra cannot read is not an application nobody paused. paused: anyOf: - type: boolean - type: 'null' title: Paused description: >- Whether a person paused Ankra's autonomous actions for this application. Null when read_state is unknown, never false. paused_at: anyOf: - type: string format: date-time - type: 'null' title: Paused At paused_by: anyOf: - type: string - type: 'null' title: Paused By reason: anyOf: - type: string - type: 'null' title: Reason required: - read_state - paused - paused_at - paused_by - reason title: ApplicationAutonomyPauseSummary ApplicationAutonomyArea: type: object properties: area: type: string enum: - keep_it_up - ship_changes - keep_it_safe - keep_costs_down - keep_it_current - fix_my_code title: Area level: type: string enum: - you_run_it - together - ankra_runs_it title: Level source: $ref: '#/components/schemas/AutonomyRuleSource' seeded_from: anyOf: - type: string enum: - auto_remediation_policy - cost_autopilot_tier - deploys_on_push - type: 'null' title: Seeded From description: >- The existing setting the organisation layer read this area from; null when another rule decided it. For an area its ceiling capped, the setting the refused request came from. ceiling: $ref: '#/components/schemas/AutonomyCeiling' requested: $ref: '#/components/schemas/AutonomyAreaRequest' required: - area - level - source - seeded_from - ceiling title: ApplicationAutonomyArea ApplicationAutonomyLimits: type: object properties: monthly_cost_increase_cents: $ref: '#/components/schemas/AutonomyIntegerLimit' production_downtime_seconds: $ref: '#/components/schemas/AutonomyIntegerLimit' non_production_downtime_seconds: $ref: '#/components/schemas/AutonomyIntegerLimit' may_change_data: $ref: '#/components/schemas/AutonomyBooleanLimit' required: - monthly_cost_increase_cents - production_downtime_seconds - non_production_downtime_seconds - may_change_data title: ApplicationAutonomyLimits ApplicationAutonomyStoredLayer: type: object properties: level: anyOf: - type: string enum: - you_run_it - together - ankra_runs_it - type: 'null' title: Level areas: type: object additionalProperties: type: string enum: - you_run_it - together - ankra_runs_it description: >- Per-area levels keyed by area: keep_it_up, ship_changes, keep_it_safe, keep_costs_down, keep_it_current, fix_my_code. title: Areas limits: $ref: '#/components/schemas/AutonomyLayerLimits' widened_by_admin: type: boolean title: Widened By Admin required: - level - areas - limits - widened_by_admin description: >- One layer exactly as it is stored: the body a write of that layer starts from. title: ApplicationAutonomyStoredLayer AutonomyRuleSource: type: object properties: layer: type: string enum: - platform_default - organisation - app - environment - platform_capability title: Layer detail: type: string enum: - default - kind_level - layer_level - area - limit - ceiling title: Detail widened_by_admin: type: boolean title: Widened By Admin clamped: type: boolean title: Clamped clamped_layer: type: string title: Clamped Layer required: - layer - detail - widened_by_admin - clamped title: AutonomyRuleSource AutonomyCeiling: type: object properties: level: type: string enum: - you_run_it - together - ankra_runs_it title: Level reason: title: Reason type: string required: - level - reason title: AutonomyCeiling description: >- The most autonomy the platform can honour in the area today, and why. An area above it is held at it, with source.layer platform_capability. AutonomyAreaRequest: type: object properties: level: type: string enum: - you_run_it - together - ankra_runs_it title: Level source: $ref: '#/components/schemas/AutonomyRuleSource' required: - level - source title: AutonomyAreaRequest description: >- What the layers asked for in an area its readiness ceiling capped, and the rule that asked. Present only on a capped area. AutonomyIntegerLimit: type: object properties: value: type: integer title: Value source: $ref: '#/components/schemas/AutonomyRuleSource' required: - value - source title: AutonomyIntegerLimit AutonomyBooleanLimit: type: object properties: value: type: boolean title: Value source: $ref: '#/components/schemas/AutonomyRuleSource' required: - value - source title: AutonomyBooleanLimit AutonomyLayerLimits: type: object properties: monthly_cost_increase_cents: type: integer minimum: 0 title: Monthly Cost Increase Cents production_downtime_seconds: type: integer minimum: 0 title: Production Downtime Seconds non_production_downtime_seconds: type: integer minimum: 0 title: Non Production Downtime Seconds may_change_data: type: boolean title: May Change Data additionalProperties: false title: AutonomyLayerLimits description: >- A layer's own limits. An omitted limit is inherited from the layer above; lower is stricter, and false is stricter for may_change_data. securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.