> ## 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. # Classify the service a stack profile runs > Asks the organisation's service_classification AI lane (the Quick tier, Claude Haiku, unless the organisation chose another model for the lane) what kind of managed service the profile's latest version runs: an engine applications connect to over a protocol Ankra supports (`protocol` set), an engine Ankra has no protocol for, an application or piece of infrastructure, or unclear. Only the profile's name and description and each add-on's name, chart, chart version, registry and namespace are sent; configuration values and manifests never are. The answer is validated before it is returned and cached per profile version for 24 hours, and every call is metered and gated by the monthly AI allowance. Model trouble is never an error status: `available` false with `unavailable_reason` says why no classification could be made (no_addons, allowance_exhausted, ai_unavailable or model_error). Requires profiles.read on a profile the caller can see. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/stack-profiles/{profile_id}/service-classification 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: 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/stack-profiles/{profile_id}/service-classification: get: tags: - Stack Profiles summary: Classify the service a stack profile runs description: >- Asks the organisation's service_classification AI lane (the Quick tier, Claude Haiku, unless the organisation chose another model for the lane) what kind of managed service the profile's latest version runs: an engine applications connect to over a protocol Ankra supports (`protocol` set), an engine Ankra has no protocol for, an application or piece of infrastructure, or unclear. Only the profile's name and description and each add-on's name, chart, chart version, registry and namespace are sent; configuration values and manifests never are. The answer is validated before it is returned and cached per profile version for 24 hours, and every call is metered and gated by the monthly AI allowance. Model trouble is never an error status: `available` false with `unavailable_reason` says why no classification could be made (no_addons, allowance_exhausted, ai_unavailable or model_error). Requires profiles.read on a profile the caller can see. operationId: classify_stack_profile_service_api_v1 parameters: - name: profile_id in: path required: true schema: type: string format: uuid responses: '200': content: application/json: schema: $ref: '#/components/schemas/StackProfileServiceClassification' description: The classification, or why none could be made '401': description: Unauthorized '403': description: 'Insufficient permission: profiles.read' '404': description: Profile not found '500': description: Internal server error security: - BearerAuth: [] components: schemas: StackProfileServiceClassification: type: object description: >- What kind of managed service a stack profile's latest version runs. When `available` is true every other member except `unavailable_reason` is present (null where it does not apply); when it is false only `unavailable_reason` is. properties: available: type: boolean description: Whether a validated classification was made. unavailable_reason: type: string enum: - no_addons - spec_unreadable - allowance_exhausted - ai_unavailable - model_error description: >- Only when available is false. no_addons: the latest version has no add-ons, and the model was not asked. spec_unreadable: the latest version's stored specification could not be read, so whether it has add-ons is unknown, and the model was not asked. allowance_exhausted: the monthly AI allowance or billing standing refused the call. ai_unavailable: no model can serve the lane for this organisation. model_error: the call failed or its answer did not validate. profile_version_id: type: string format: uuid description: The latest version, the one classified. verdict: type: string enum: - engine - unsupported_engine - application - unclear description: >- engine: a data engine applications connect to over a supported protocol (wire-compatible engines included). unsupported_engine: something applications connect to that Ankra has no protocol for. application: a tool people use or cluster infrastructure. unclear: the model could not tell. protocol: type: string nullable: true enum: - postgres - redis - nats - opensearch - s3 - victorialogs - victoriametrics - null description: >- The protocol applications connect over; set only for the engine verdict. engine: type: string nullable: true description: >- The engine's common name (for example PostgreSQL or Apache Kafka), at most 80 characters, for the two engine verdicts; otherwise null. addon: type: string nullable: true description: >- The name of the profile add-on that runs it, exactly as the profile spells it, or null. confidence: type: string enum: - high - medium - low reason: type: string description: One plain sentence, at most 280 characters. required: - available title: StackProfileServiceClassification securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.