> ## 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. # List what Ankra did on its own > What Ankra did on its own across every application, newest first: auto-remediation runs on an application's placements, Cost Autopilot actions the autopilot approved itself on an application's cluster, and build fixes the automatic lane sent. Each action is one item naming every application it was on, with who acted, the rule that allowed it and whether it can be undone. At most 20 actions; a source with more is named in capped_sources and a source that could not be read in unavailable_sources. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/applications/autonomous-actions openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - 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: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - 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: 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: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - 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: OVH Credentials description: OVH credentials and SSH keys. - 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: 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/autonomous-actions: get: tags: - Applications summary: List what Ankra did on its own description: >- What Ankra did on its own across every application, newest first: auto-remediation runs on an application's placements, Cost Autopilot actions the autopilot approved itself on an application's cluster, and build fixes the automatic lane sent. Each action is one item naming every application it was on, with who acted, the rule that allowed it and whether it can be undone. At most 20 actions; a source with more is named in capped_sources and a source that could not be read in unavailable_sources. operationId: list_autonomous_actions_api_v1 responses: '200': content: application/json: schema: $ref: '#/components/schemas/ApplicationAutonomousActionsResponse' description: Successful Response components: schemas: ApplicationAutonomousActionsResponse: type: object properties: actions: type: array items: $ref: '#/components/schemas/ApplicationAutonomousAction' title: Actions capped: type: boolean title: Capped description: True when more actions exist than the response carries. capped_sources: type: array items: type: string enum: - remediation_runs - autopilot_actions - build_fixes title: Capped Sources description: Each source that had more actions than it returned. unavailable_sources: type: array items: type: string enum: - remediation_runs - autopilot_actions - build_fixes title: Unavailable Sources description: >- Each source that could not be read. An empty actions list beside one is not "Ankra did nothing". required: - actions - capped - capped_sources - unavailable_sources title: ApplicationAutonomousActionsResponse ApplicationAutonomousAction: allOf: - $ref: '#/components/schemas/ApplicationTimelineEvent' - type: object properties: applications: type: array items: $ref: '#/components/schemas/ApplicationAutonomousActionApplication' title: Applications description: >- Every application the action was on, by name. A Cost Autopilot action stops or resizes a whole cluster, so it names every application installed there. required: - applications title: ApplicationAutonomousAction ApplicationTimelineEvent: properties: id: title: Id type: string kind: type: string title: Kind status: type: string title: Status occurred_at: title: Occurred At type: string cluster_name: anyOf: - type: string - type: 'null' title: Cluster Name namespace: anyOf: - type: string - type: 'null' title: Namespace commit_sha: anyOf: - type: string - type: 'null' title: Commit Sha ref: anyOf: - type: string - type: 'null' title: Ref url: anyOf: - type: string - type: 'null' title: Url message: anyOf: - type: string - type: 'null' title: Message verdict: anyOf: - type: string - type: 'null' title: Verdict pr_number: anyOf: - type: integer - type: 'null' title: Pr Number duration_seconds: anyOf: - type: integer - type: 'null' title: Duration Seconds reason: anyOf: - type: string - type: 'null' title: Reason description: >- Why the platform wanted a platform_build (first_onboard, push, retry, demo, pipeline), or the decision kind of an autopilot_action (off_hours_schedule, right_size, right_size_rollback); null on every other kind. component: anyOf: - type: string - type: 'null' title: Component description: >- The repository component a platform_build built; null when the build was not for one component and on every other kind. actor: anyOf: - type: string enum: - ankra - person - type: 'null' title: Actor description: >- Who took the action: ankra when Ankra acted on its own, person when someone started it. Null where the source does not record it, which says nothing either way. rule: anyOf: - type: string - type: 'null' title: Rule description: >- The setting that allowed an action Ankra took on its own: auto_remediation_policy, cost_autopilot_tier, auto_fix_builds or deploys_on_push (a deploy the push-to-deploy loop started). Null where the event records none. undo: anyOf: - $ref: '#/components/schemas/ApplicationTimelineUndo' - type: 'null' title: Undo description: >- Whether an action Ankra took on its own can be put back from Ankra, and how or why not. Null where the event does not say; release undo is the client's own rule. required: - id - kind - status - occurred_at title: ApplicationTimelineEvent type: object ApplicationAutonomousActionApplication: type: object properties: id: title: Id type: string name: title: Name type: string required: - id - name title: ApplicationAutonomousActionApplication ApplicationTimelineUndo: type: object properties: available: type: boolean title: Available reason: type: string title: Reason description: >- How to put it back, or why it cannot be put back from Ankra yet, as a sentence shown as is. required: - available - reason title: ApplicationTimelineUndo ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.