slug: altimate-ai provider: Altimate AI generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 24 edges: - tag: Databricks Cost spec_file: altimate-ai-databricks-cost-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.85 evidence: Get Databricks cost overview; Get cost breakdown by SKU; Get cost breakdown by workspace; Get total estimated cost for the year reason: Operations report, break down, compare and forecast cloud platform spend — IT financial management (IT spend visibility, showback, cost optimisation). - tag: Databricks Savings spec_file: altimate-ai-databricks-savings-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.85 evidence: '"Get overall savings summary", "Get overall savings estimate with projections", "Get tracked assisted savings"' reason: Endpoints quantify and track realised/projected savings on Databricks spend, which is squarely IT spend and cost optimisation (IT Financial Management). - tag: Dashboards spec_file: altimate-ai-dashboards-api-openapi.yml capability_id: BC-610.50 capability_id_l1: BC-610 capability_name: Analytics & BI Management confidence: 0.8 evidence: GET /business_intelligence/dashboards Fetch Dashboards; GET /business_intelligence/filters Get BI Report filters; schemas BIDashboardItem, DashboardRefreshActivity reason: Operations catalogue BI dashboards, their insights, refresh and access activity and user reports — management of the reporting/BI estate, i.e. Analytics & BI Management. - tag: Databricks Opportunities spec_file: altimate-ai-databricks-opportunities-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.8 evidence: '"Get oversized cluster opportunities", "Get idle clusters", "Get expensive queries", "Get serverless migration candidates"' reason: '''Opportunities'' here are cloud/warehouse cost-optimisation findings (idle and oversized clusters, expensive queries), not sales opportunities — this is IT spend and cost optimisation. The homograph with BC-410.30 Opportunity & Pipeline Management is explicitly rejected.' - tag: PERMISSION spec_file: altimate-ai-permission-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /permissions/ Role Add; PATCH /permissions/{role_uuid} Role Edit; schemas RolePermissionFull, PermissionsFull reason: Role and permission CRUD is access management. Mapped to Identity & Access Management; alternative reading as tenant-level RBAC plumbing keeps confidence at 0.8. - tag: SUMMARY_V2 spec_file: altimate-ai-summary-v2-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.8 evidence: GET /summary/v2/cost/compute Get Compute Summary; GET /summary/v2/cost/storage/estimate Get Storage Estimate Summary reason: Endpoints report cloud/warehouse cost by compute, storage, serverless, cloud and AI services plus savings estimates — technology cost visibility and optimisation, i.e. IT Financial Management. - tag: USER spec_file: altimate-ai-user-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /users/invite Invite User; POST /users/role_edit User Role Edit; schemas RolePermissionFull, PermissionsFull reason: User provisioning, invitation, onboarding, role and permission administration is identity and access management for the platform. - tag: ACCOUNT_COSTS spec_file: altimate-ai-account-costs-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.78 evidence: GET /account_costs/total Get Total Costs; GET /account_costs/chart; GET /account_costs/table reason: Cost reporting across warehouse accounts, matching the vendor's stated aim to 'optimize warehouse cost'. That is technology spend visibility and optimisation — IT Financial Management. - tag: CONTRACT spec_file: altimate-ai-contract-api-openapi.yml capability_id: BC-610.10 capability_id_l1: BC-610 capability_name: Data Governance Management confidence: 0.78 evidence: POST /registries/{registry_id}/contracts/definitions/validate Validate Contract Definition Dry Run; schemas PolicyDetail, Violation, ContractValidationResponse reason: These are data contracts held in registries, validated against policies with violations — data governance, not legal contract management. Homograph avoided; policy/violation schemas ground the data-governance reading. - tag: Business Intelligence spec_file: altimate-ai-business-intelligence-api-openapi.yml capability_id: BC-610.50 capability_id_l1: BC-610 capability_name: Analytics & BI Management confidence: 0.75 evidence: GET /business_intelligence/dashboards Fetch Dashboards; GET /business_intelligence/dashboards/access_activity ... daily counts for past 30 days; schemas TableauProject, BIDashboardItem reason: Operations inventory and analyse BI dashboards (Tableau), their insights, refresh and access activity, and user reporting — squarely analytics/BI delivery and stewardship. Some ambiguity as it leans toward BI governance, but Analytics & BI Management is the best fit. - tag: Lineage spec_file: altimate-ai-lineage-api-openapi.yml capability_id: BC-610 capability_id_l1: BC-610 capability_name: Information & Data Management confidence: 0.75 evidence: POST /lineage/upstream Post Upstream Tables; POST /lineage/connected Post Connected Columns; schemas ColumnLineageEdge, TableSchemaResponse, SchemaMetadata reason: Column- and table-level data lineage traversal across warehouse/dbt assets — metadata about data structures and flows, clearly Information & Data Management. Left at L1 because lineage straddles data governance and data architecture sub-capabilities. - tag: PAYMENT spec_file: altimate-ai-payment-api-openapi.yml capability_id: BC-4250.40 capability_id_l1: BC-4250 capability_name: Payment Collection & Dunning confidence: 0.75 evidence: POST /payment/checkout Create Checkout Session; POST /payment/downgrade Downgrade Subscription; GET /payment/plans/{tenure} Get All Plans reason: 'Handles the vendor''s own SaaS subscription commerce: checkout, credits/wallet, plan tiers, downgrades. Payment collection/checkout is the dominant surface, though plan and subscription-change operations also touch BC-4240, hence 0.75.' - tag: COMPUTE_POOLS spec_file: altimate-ai-compute-pools-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.72 evidence: GET /compute-pools/{pool_name}/daily-cost Compute Pool Daily Cost; schemas ComputePoolCostEntry, ComputePoolsDailyGraphPoint reason: Every operation reports cost of warehouse compute pools (summary, daily cost, metadata with cost) — cloud/IT spend visibility and cost optimisation, i.e. IT Financial Management. - tag: DBT_V4 spec_file: altimate-ai-dbt-v4-api-openapi.yml capability_id: BC-610 capability_id_l1: BC-610 capability_name: Information & Data Management confidence: 0.72 evidence: POST /dbt/v4/lineage Get Column Level Lineage; POST /dbt/v4/export-lineage; schemas ColumnLineageLink, ModelColumn reason: Operations compute and export column-level data lineage across dbt models — an information/data management concern (lineage documentation supporting governance and data architecture). Kept at L1 because the evidence does not clearly distinguish governance vs. data architecture sub-capability. - tag: DATABRICKS spec_file: altimate-ai-databricks-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.7 evidence: '''Get Databricks cost overview'', ''Get cost breakdown by SKU'', ''Get cost comparison between periods'', schema CostCategoryItem' reason: The visible operations are overwhelmingly cloud-platform spend visibility, cost trends, projections and breakdowns by workspace/SKU — IT spend and cost optimisation (showback) over Databricks infrastructure. Confidence tempered because the tag also carries cluster/job/warehouse operational endpoints that lean toward IT operations. - tag: DBT spec_file: altimate-ai-dbt-api-openapi.yml capability_id: BC-610 capability_id_l1: BC-610 capability_name: Information & Data Management confidence: 0.7 evidence: '''Dbt Docs Gen'', ''Get Column Level Lineage'', schemas DBTColumnLineageRequest, ColumnDescription, SourceTable' reason: Operations generate documentation for dbt models and compute column-level lineage across source tables — metadata, documentation and lineage of the data estate, which sits under Information & Data Management. Left at L1 because the evidence spans documentation, lineage and artefact ingestion without naming one sub-capability. - tag: DBT_MODELS spec_file: altimate-ai-dbt-models-api-openapi.yml capability_id: BC-610 capability_id_l1: BC-610 capability_name: Information & Data Management confidence: 0.7 evidence: '''Post Upstream Tables'', ''Post Downstream Tables'', ''Post Connected Columns'', ''Get Sql Lineage'', ''Get Table Schema Response'', schemas ColumnLineageEdge, SchemaMetadata' reason: Catalogue and lineage traversal over dbt models — upstream/downstream tables, connected columns, table schemas — which is metadata and data-structure management. L1 only, as the surface spans catalogue, lineage and schema without pinning a single sub-capability. - tag: Databricks Warehouses spec_file: altimate-ai-databricks-warehouses-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.7 evidence: '"Get total auto-tune savings across SQL warehouses", "Get warehouse cost trends by SKU", "Get realised savings range and estimated annual savings for a SQL warehouse"' reason: '''Warehouses'' means SQL compute warehouses, not physical logistics warehouses (BC-520.50 explicitly rejected). The dominant motive is cost/savings analysis of that compute, i.e. IT cost optimisation; some endpoints are pure infrastructure state, hence 0.7.' - tag: Knowledge Bases V2 spec_file: altimate-ai-knowledge-bases-v2-api-openapi.yml capability_id: BC-830 capability_id_l1: BC-830 capability_name: Knowledge Management confidence: 0.7 evidence: Upload With Kb Creation; Get Knowledge Base Documents; Query Knowledge Bases; schemas KnowledgeDocumentUploadResponse, KnowledgeQueryRequest reason: Document ingestion into knowledge bases plus retrieval queries over them — capture, curation and sharing of organisational knowledge. Kept at L1 since it spans capture, curation and retrieval. - tag: METABASE spec_file: altimate-ai-metabase-api-openapi.yml capability_id: BC-610.50 capability_id_l1: BC-610 capability_name: Analytics & BI Management confidence: 0.7 evidence: GET /metabase/dashboards Get Tenant Dashboards; POST /metabase/sync-dashboard-metadata reason: Operations manage BI dashboards (Metabase) and their metadata for tenants, which is analytics/BI delivery. Some of it is integration plumbing (JWT token generation), hence moderate confidence. - tag: SUMMARY spec_file: altimate-ai-summary-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.7 evidence: GET /summary/experimentation_savings Get Experimentation Savings; schema SummaryTotalSavingsResponse reason: Summary graphs, comparisons and insights over cost savings for warehouse spend correspond to IT spend/cost-optimisation reporting. Slight ambiguity because the surface is a generic reporting endpoint set. - tag: SUPERTOKENS spec_file: altimate-ai-supertokens-api-openapi.yml capability_id: BC-4230.50 capability_id_l1: BC-4230 capability_name: Tenant Identity Federation confidence: 0.7 evidence: POST /supertokens/update-tenant-saml Update Tenant Saml; POST /supertokens/configure/{provider} Configure Sso reason: Operations create tenants and configure per-tenant third-party/SAML SSO providers, which is federation of tenant identity providers in a multi-tenant SaaS. Some overlap with tenant provisioning (BC-4230.10). - tag: TABLES spec_file: altimate-ai-tables-api-openapi.yml capability_id: BC-610.10 capability_id_l1: BC-610 capability_name: Data Governance Management confidence: 0.7 evidence: PATCH /tables/{table_id} Update Table Metadata; POST /tables/custom/{table_id} Upsert Custom Table Tag; TableOwnerFilterResponse reason: 'Data-catalog surface: table/column metadata, tags, ownership, descriptions and access history — stewardship and cataloguing of data assets, i.e. data governance, consistent with the vendor''s stated ''enforce data governance''.' - tag: TEAMS spec_file: altimate-ai-teams-api-openapi.yml capability_id: BC-600.80 capability_id_l1: BC-600 capability_name: IT Financial Management confidence: 0.7 evidence: GET /teams/cost/graph Get Cost; GET /teams/cost/period-comparison; schemas DailyTeamSpend, TeamSpend reason: Operations attribute warehouse spend to internal teams and compare cost across periods — chargeback/showback and IT cost optimisation rather than HR team management.