Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness Coverage Details API

3 actions 3 updates phrasing extends openapi/harness-coverage-details-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 3

$.info
$.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/details/savingsplans'].post
$.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/details/reservedinstances'].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 Details API
  version: 1.0.0
extends: openapi/harness-coverage-details-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: 2
- target: $.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/details/savingsplans'].post
  update:
    x-apievangelist-phrasing:
      intent: Get Savings Plans coverage details
      effect: read
      questions:
      - How much of my compute spend is covered by Savings Plans versus on-demand?
      - Can I break Savings Plans coverage down by instance family and region?
      instructions:
      - text: Show Savings Plans coverage for account {account_id} from {start} to {end} with routing {routing_id}.
        slots:
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
          routing_id: query.routingId
      - text: Get Savings Plans covered vs on-demand spend in regions {regions} for {account_id}, {start} to {end}, routing {routing_id}.
        slots:
          regions: requestBody.regions
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
          routing_id: query.routingId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/gateway/lw/api/accounts/{account_id}/v2/coverage/details/reservedinstances'].post
  update:
    x-apievangelist-phrasing:
      intent: Get Reserved Instances coverage details
      effect: read
      questions:
      - What percentage of my running hours are covered by Reserved Instances?
      - Which instance types are running mostly on-demand instead of on reservations?
      instructions:
      - text: Show Reserved Instance coverage for account {account_id} from {start} to {end} with routing {routing_id}.
        slots:
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
          routing_id: query.routingId
      - text: Get RI covered vs on-demand hours for instance types {instance_types} in {account_id}, {start} to {end}, routing {routing_id}.
        slots:
          instance_types: requestBody.instance_types
          account_id: path.account_id
          start: query.start_date
          end: query.end_date
          routing_id: query.routingId
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/harness-coverage-details-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.