API Evangelist conversational phrasing for Densify / Kubex Public Cloud Cloud Analysis API

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Densify / Kubex Public Cloud Cloud Analysis API
  version: 1.0.0
extends: openapi/densify-cloud-analysis-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/analysis/aws'].post
  update:
    x-apievangelist-phrasing:
      intent: Start AWS collection with access keys (legacy)
      effect: write
      questions:
      - Can I start AWS data collection with an access key and secret instead of an IAM role?
      - What does the older AWS start-analysis endpoint take?
      instructions:
      - text: Start AWS data collection for account {accountNumber} with the legacy access-key endpoint.
        slots:
          accountNumber: requestBody.accountNumber
      - text: Begin collecting Amazon Web Services usage with key {accessKey} and secret {secretKey}.
        slots:
          accessKey: requestBody.accessKey
          secretKey: requestBody.secretKey
      method: generated
      generated: '2026-10-01'
- target: $.paths['/analysis/azure'].post
  update:
    x-apievangelist-phrasing:
      intent: Start Azure collection with access keys (legacy)
      effect: write
      questions:
      - Is there a simpler endpoint to start Azure collection with just an account number and keys?
      - What fields does the legacy Azure start-analysis call accept?
      instructions:
      - text: Start Azure data collection for account {accountNumber} via the legacy start endpoint.
        slots:
          accountNumber: requestBody.accountNumber
      - text: Launch a Microsoft Azure usage analysis on connection {connection}.
        slots:
          connection: requestBody.connection
      method: generated
      generated: '2026-10-01'
- target: $.paths['/analysis/gcp'].post
  update:
    x-apievangelist-phrasing:
      intent: Start GCP collection with access keys (legacy)
      effect: write
      questions:
      - Can I start GCP data collection with an access key pair rather than a service account?
      - What does the older GCP start-analysis endpoint expect?
      instructions:
      - text: Start GCP data collection for account {accountNumber} through the old start call.
        slots:
          accountNumber: requestBody.accountNumber
      - text: Trigger Google Cloud usage collection for connection {connection} on the original endpoint.
        slots:
          connection: requestBody.connection
      method: generated
      generated: '2026-10-01'