> ## 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 merge train lead time > How long the repository's merged pull requests took from ready to production over the last day and the last week: p50 and p90 with the count, each segment's spread (admission wait, queue, failed cars, the car that passed, merge, deploy), failed car runs by class, the merges not deployed or not recorded yet, and the three slowest with the segment that held each up. Recorded by the pipeline_lead_time maintenance loop. Requires pipelines.read. Read-only. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/pipeline-repositories/{repository_id}/merge-train/lead-time 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/pipeline-repositories/{repository_id}/merge-train/lead-time: get: tags: - Pipelines summary: Get a repository's merge train lead time description: >- How long the repository's merged pull requests took from ready to production over the last day and the last week: p50 and p90 with the count, each segment's spread (admission wait, queue, failed cars, the car that passed, merge, deploy), failed car runs by class, the merges not deployed or not recorded yet, and the three slowest with the segment that held each up. Recorded by the pipeline_lead_time maintenance loop. Requires pipelines.read. Read-only. operationId: getPipelineRepositoryMergeTrainLeadTimeToken parameters: - name: repository_id in: path required: true schema: type: string format: uuid responses: '200': description: The lead time per window. content: application/json: schema: $ref: '#/components/schemas/PipelineMergeTrainLeadTime' '401': description: Authentication required '403': description: Missing pipelines.read '404': description: No such pipeline repository in the organisation '422': description: Malformed repository id '500': description: Internal error security: - BearerAuth: [] components: schemas: PipelineMergeTrainLeadTime: type: object required: - repository_id - repository - deploy_signal - deploy_signal_is_proxy - windows - summary_lines properties: repository_id: type: string format: uuid repository: type: string description: owner/name. deploy_signal: type: - string - 'null' enum: - github_workflow - platform_deploy - null description: >- What the most recent record read as production: a deploy workflow run concluding (github_workflow) or the platform's deploy job succeeding on a production cluster (platform_deploy). Null while nothing is recorded. deploy_signal_is_proxy: type: - boolean - 'null' description: >- True when the signal is a deploy concluding rather than the workload rolling. Null with deploy_signal. windows: type: array items: $ref: '#/components/schemas/PipelineMergeTrainLeadTimeWindow' description: The last day, then the last week. summary_lines: type: array items: type: string description: >- One line per window as a person reads it: p50, p90, n, the merges not deployed or not recorded yet, and the slowest pull requests with the segment that held each up. description: >- How long the repository's merged pull requests took from ready (admitted to the merge train, or un-drafted if later) to production, per window. PipelineMergeTrainLeadTimeWindow: type: object required: - window - since - count - p50_seconds - p90_seconds - not_deployed - deploy_unknown - unrecorded - unknown_draft_state - is_truncated - segments - failed_cars - slowest properties: window: type: string enum: - 1d - 7d since: type: string format: date-time description: The earliest merge the window counts. count: type: integer description: The merges a deploy carried, the ones the percentiles are over. p50_seconds: type: - number - 'null' description: The median lead time, null when count is zero. p90_seconds: type: - number - 'null' description: The 90th percentile lead time, null when count is zero. not_deployed: type: integer description: Merges no deploy carried within 72 hours. They have no lead time. deploy_unknown: type: integer description: >- Merges no deploy is known to have carried within 72 hours, with a deploy after them that does not say what it deployed, such as a rollback. They have no lead time, and may have reached production. unrecorded: type: integer description: >- Merges not recorded yet: a deploy may still carry them, or the recorder has not read them. Neither deployed nor not. unknown_draft_state: type: integer description: >- Deployed merges whose draft history could not be read, so their ready time is their admission. is_truncated: type: boolean description: >- A listing behind the window was capped inside it: the counts are a lower bound. segments: type: array description: >- Every segment in order (admission_wait, queue, failed_cars, car, merge, deploy, roll) with its spread over the deployed merges that carry it. items: type: object required: - segment - count - p50_seconds - p90_seconds properties: segment: type: string enum: - admission_wait - queue - failed_cars - car - merge - deploy - roll count: type: integer p50_seconds: type: - number - 'null' p90_seconds: type: - number - 'null' failed_cars: type: object additionalProperties: type: integer description: >- The deployed merges' failed car runs by class, every class present: code, infrastructure, discarded, cancelled, unconcluded. slowest: type: array description: The three slowest deployed merges, slowest first. items: type: object required: - entry_id - pull_request_number - pull_request_title - merged_at - lead_seconds - dominant_segment - dominant_seconds properties: entry_id: type: string format: uuid pull_request_number: type: integer pull_request_title: type: string merged_at: type: string format: date-time lead_seconds: type: number dominant_segment: type: string description: The segment that took longest. dominant_seconds: type: number securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.