Harness · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Harness Chaos Components API

3 actions 3 updates phrasing extends openapi/harness-chaos-components-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/chaos/manager/api/v3/integrations/get-chaos-component-variable'].get

$.paths['/gateway/chaos/manager/api/v3/integrations/run-chaos-component'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Chaos Components API
  version: 1.0.0
extends: openapi/harness-chaos-components-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/chaos/manager/api/v3/integrations/get-chaos-component-variable'].get
  update:
    x-apievangelist-phrasing:
      intent: Get variables for a chaos fault, probe or action
      effect: read
      questions:
      - What inputs does a chaos fault or probe need before I run it?
      - Can I see the variables for a component in a specific chaos hub?
      instructions:
      - text: Get variables for chaos component {component} of type {type}.
        slots:
          component: query.identifier
          type: query.type
      - text: Show inputs for component {component} from hub {hub}.
        slots:
          component: query.identifier
          hub: query.hubReference
      method: generated
      generated: '2026-09-26'
- target: $.paths['/gateway/chaos/manager/api/v3/integrations/run-chaos-component'].post
  update:
    x-apievangelist-phrasing:
      intent: Run a chaos fault, probe or action
      effect: write
      questions:
      - Can I run a single chaos fault on my infrastructure without a full experiment?
      - Is it possible to run a chaos probe for a set duration from a pipeline?
      instructions:
      - text: Run chaos component {component} of type {type} on infrastructure {infra}.
        slots:
          component: requestBody.identity
          type: requestBody.type
          infra: requestBody.infraReference
      - text: Run component {component} for {duration} as part of pipeline {pipeline}.
        slots:
          component: requestBody.identity
          duration: requestBody.duration
          pipeline: query.pipelineIdentifier
      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-chaos-components-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.

GitHub Google LinkedIn

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