> ## 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 a repository's launch status (browser session) > Where a GitHub repository is on its way to a working app on Ankra (ankra-bjkszh.7): not connected, analysing, N decisions left in the Launch Plan, ready for approval, proving the setup pull request, proof failed, or live. The state the Ankra Chrome extension shows on GitHub, Vercel, Lovable and Claude Design pages. Every application the caller can see that builds the repository is listed, the one building branch first. Requires applications.read. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /org/applications/launch-status openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] 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: 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: 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: /org/applications/launch-status: get: tags: - Applications summary: Get a repository's launch status (browser session) description: >- Where a GitHub repository is on its way to a working app on Ankra (ankra-bjkszh.7): not connected, analysing, N decisions left in the Launch Plan, ready for approval, proving the setup pull request, proof failed, or live. The state the Ankra Chrome extension shows on GitHub, Vercel, Lovable and Claude Design pages. Every application the caller can see that builds the repository is listed, the one building branch first. Requires applications.read. operationId: get_repository_launch_status parameters: - in: query name: repository required: true schema: title: Repository type: string pattern: ^[A-Za-z0-9](?:[A-Za-z0-9-]{0,38})/[A-Za-z0-9._-]{1,100}$ description: The GitHub repository as owner/name; a trailing .git is ignored. - in: query name: branch required: false schema: title: Branch type: string maxLength: 255 description: Put the application that builds this branch first. responses: '200': content: application/json: schema: $ref: '#/components/schemas/ApplicationLaunchStatus' description: >- The repository's launch state, not-connected when no visible application builds it '403': description: The caller lacks applications.read '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error components: schemas: ApplicationLaunchStatus: type: object title: ApplicationLaunchStatus description: >- Where a GitHub repository is on its way to a working app. state is the state of the first application: the one building the requested branch, else the oldest. not-connected means no application the caller can see builds the repository; analysing that no App Contract is stored yet; decisions that the Launch Plan leaves decision_count questions to a person; ready that it leaves none; proving that the setup pull request's proof is queued or running; proof-failed that it failed or could not prove; live that a deployment reads Healthy under the readiness gate. required: - repository_owner - repository_name - state - application_id - decision_count - applications - is_truncated properties: repository_owner: type: string title: Repository Owner repository_name: type: string title: Repository Name state: type: string title: State enum: - not-connected - analysing - decisions - ready - proving - proof-failed - live application_id: type: - string - 'null' title: Application Id decision_count: type: - integer - 'null' title: Decision Count applications: type: array title: Applications items: $ref: '#/components/schemas/ApplicationLaunchStatusApplication' is_truncated: type: boolean title: Is Truncated description: More applications build the repository than one read judges (five). HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object ApplicationLaunchStatusApplication: type: object title: ApplicationLaunchStatusApplication description: >- One application that builds the repository, with its launch state and what it was judged from. required: - application_id - name - branch - state - launch_plan_status - decision_count - proof_headline - healthy_deployment_count - deployment_count properties: application_id: type: string title: Application Id name: type: string title: Name branch: type: string title: Branch state: type: string title: State enum: - not-connected - analysing - decisions - ready - proving - proof-failed - live launch_plan_status: type: string title: Launch Plan Status enum: - planned - not-extracted - unsupported-contract decision_count: type: - integer - 'null' title: Decision Count description: >- Decisions the Launch Plan leaves to a person, null when there is no plan. proof_headline: type: - string - 'null' title: Proof Headline description: >- The latest proof run's headline (proven, proving, proof failed: , not proven: ), null when no setup pull request was proven yet. healthy_deployment_count: type: integer title: Healthy Deployment Count deployment_count: type: integer title: Deployment Count ValidationError: properties: loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.