Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness Coverage Overview API

2 actions 2 updates phrasing extends openapi/harness-coverage-overview-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Harness's API. It is a proposal applied on top of the contract, not a document Harness publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info
$.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/overview'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Coverage Overview API
  version: 1.0.0
extends: openapi/harness-coverage-overview-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 1
- target: $.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/overview'].post
  update:
    x-apievangelist-phrasing:
      intent: Get RI, Savings Plan and on-demand coverage
      effect: read
      questions:
      - How much of my compute spend is covered by reserved instances and savings plans versus on-demand?
      - Can I break down commitment coverage by region or instance type for a date range?
      instructions:
      - text: Get RI, SP and on-demand coverage for account {account_id} from {start} to {end}, routing {routing}, identifier {account}.
        slots:
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
          routing: query.routingId
          account: query.accountIdentifier
      - text: Show commitment coverage in regions {regions} for account {account_id} between {start} and {end}.
        slots:
          regions: requestBody.regions
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
      method: generated
      generated: '2026-09-26'