Mux · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Mux Incidents API

4 actions 4 updates phrasing extends openapi/mux-com-incidents-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Mux's API. It is a proposal applied on top of the contract, not a document Mux publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info

$.paths['/data/v1/incidents'].get

$.paths['/data/v1/incidents/{INCIDENT_ID}'].get

$.paths['/data/v1/incidents/{INCIDENT_ID}/related'].get

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 Mux Incidents API
  version: 1.0.0
extends: openapi/mux-com-incidents-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: 3
- target: $.paths['/data/v1/incidents'].get
  update:
    x-apievangelist-phrasing:
      intent: List video quality incidents
      effect: read
      questions:
      - Are there any open playback incidents affecting my viewers right now?
      - Can I list incidents by severity or status?
      instructions:
      - text: List my incidents.
      - text: List {status} incidents with severity {severity}.
        slots:
          status: query.status
          severity: query.severity
      method: generated
      generated: '2026-09-26'
- target: $.paths['/data/v1/incidents/{INCIDENT_ID}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an incident's details
      effect: read
      questions:
      - What happened during a specific playback incident?
      - Can I look up one incident by its ID?
      instructions:
      - text: Show incident {incident_id}.
        slots:
          incident_id: path.INCIDENT_ID
      - text: Get the details of incident {incident_id}.
        slots:
          incident_id: path.INCIDENT_ID
      method: generated
      generated: '2026-09-26'
- target: $.paths['/data/v1/incidents/{INCIDENT_ID}/related'].get
  update:
    x-apievangelist-phrasing:
      intent: List incidents related to an incident
      effect: read
      questions:
      - Which other incidents seem connected to this one?
      - Is this playback incident part of a bigger pattern of related issues?
      instructions:
      - text: List incidents related to {incident_id}.
        slots:
          incident_id: path.INCIDENT_ID
      - text: Find incidents linked to incident {incident_id}, ordered by {order_by}.
        slots:
          incident_id: path.INCIDENT_ID
          order_by: query.order_by
      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/mux-com-incidents-api-phrasing-overlay"

All openapi overlays

curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.