> ## 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. # Choose the service behind an application's conventional connection names (browser session) > Requires the applications rollout flag, applications.deploy, and clusters.operate on the environment's cluster, all intersected with live token scopes. Chooses which managed service gives one application environment a protocol's conventional connection names (DATABASE_URL and the PG* names for postgres, REDIS_URL for redis, NATS_URL, OPENSEARCH_URL, S3_ENDPOINT and AWS_* for s3, ...), or, with instance_id null, that none does. Every service connected to the environment is always delivered under its own prefix (ORDERS_DB_DATABASE_URL); the conventional names belong to one service per protocol, recorded the first time a deploy delivers them, and never move by themselves. When that service stops serving the environment while another service of the protocol still does, the application's deploys are refused until a person chooses here; the instance read shows it as connection_delivery.holder_gone on the consumer. Nothing is deployed: the next deploy delivers the choice. A chosen service must be connected to the environment and speak the protocol. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json put /org/service-admission/connection-defaults 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: /org/service-admission/connection-defaults: put: tags: - Services summary: >- Choose the service behind an application's conventional connection names (browser session) description: >- Requires the applications rollout flag, applications.deploy, and clusters.operate on the environment's cluster, all intersected with live token scopes. Chooses which managed service gives one application environment a protocol's conventional connection names (DATABASE_URL and the PG* names for postgres, REDIS_URL for redis, NATS_URL, OPENSEARCH_URL, S3_ENDPOINT and AWS_* for s3, ...), or, with instance_id null, that none does. Every service connected to the environment is always delivered under its own prefix (ORDERS_DB_DATABASE_URL); the conventional names belong to one service per protocol, recorded the first time a deploy delivers them, and never move by themselves. When that service stops serving the environment while another service of the protocol still does, the application's deploys are refused until a person chooses here; the instance read shows it as connection_delivery.holder_gone on the consumer. Nothing is deployed: the next deploy delivers the choice. A chosen service must be connected to the environment and speak the protocol. operationId: setServiceConnectionDefaultSession requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ServiceConnectionDefaultRequest' responses: '200': description: The recorded choice and the names it governs. content: application/json: schema: $ref: '#/components/schemas/ServiceConnectionDefault' '400': description: Bearer token not provided or invalid authorization header '401': description: Authentication required '403': description: Insufficient permission or missing browser CSRF '404': description: >- The application or cluster is not accessible or absent, or rollout disabled '409': description: >- The service does not serve this application environment over this protocol '422': description: Invalid or ambiguous request '500': description: Internal error '503': description: Rollout availability could not be verified security: - SessionCookie: [] servers: - url: https://api.platform.ankra.app components: schemas: ServiceConnectionDefaultRequest: type: object additionalProperties: false required: - application_id - cluster_id - namespace - protocol - instance_id properties: application_id: type: string format: uuid cluster_id: type: string format: uuid description: The cluster the application environment runs on. namespace: type: string description: The application environment's namespace on that cluster. protocol: type: string enum: - postgres - redis - nats - opensearch - s3 - victorialogs - victoriametrics description: The wire protocol whose conventional names are chosen. instance_id: type: string format: uuid nullable: true description: >- The managed service that provides the names; it must be connected to the environment and speak the protocol. null chooses none: the application reads only each service's prefixed names. ServiceConnectionDefault: type: object additionalProperties: false required: - application_id - cluster_id - namespace - protocol - variables - instance_id - service_name properties: application_id: type: string format: uuid cluster_id: type: string format: uuid namespace: type: string protocol: type: string variables: type: array items: type: string description: The conventional names the choice governs. instance_id: type: string format: uuid nullable: true description: The chosen service; null when none was chosen. service_name: type: string nullable: true description: The chosen service's name; null when none was chosen. securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http SessionCookie: description: Browser session. Mutations also require X-Ankra-CSRF. in: cookie name: ankra_session type: apiKey ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.