Edge Impulse · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Edge Impulse Post Processing API

5 actions 5 updates phrasing extends openapi/edge-impulse-postprocessing-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 5

$.info

$.paths['/api/{projectId}/post-processing/{postProcessingId}'].get

$.paths['/api/{projectId}/post-processing/{postProcessingId}'].post

$.paths['/api/{projectId}/post-processing/{postProcessingId}/samples/{sampleId}'].post

$.paths['/api/{projectId}/post-processing/{postProcessingId}/samples/{sampleId}/classify'].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 Edge Impulse Post Processing API
  version: 1.0.0
extends: openapi/edge-impulse-postprocessing-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: 4
- target: $.paths['/api/{projectId}/post-processing/{postProcessingId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a post-processing block's config
      effect: read
      questions:
      - How do I read the current settings of a post-processing block in my impulse?
      - What parameters is my post-processing block configured with?
      instructions:
      - text: Get the config of post-processing block {postProcessingId} in project {projectId}.
        slots:
          projectId: path.projectId
          postProcessingId: path.postProcessingId
      - text: Show the post-processing parameters for block {postProcessingId}.
        slots:
          postProcessingId: path.postProcessingId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/{projectId}/post-processing/{postProcessingId}'].post
  update:
    x-apievangelist-phrasing:
      intent: Configure a post-processing block
      effect: write
      questions:
      - Can I turn a post-processing block on or off and change its parameters?
      - Does saving post-processing settings overwrite values I leave out?
      instructions:
      - text: Enable post-processing block {postProcessingId} in project {projectId} with parameters {parameters}.
        slots:
          projectId: path.projectId
          postProcessingId: path.postProcessingId
          parameters: requestBody.parameters
      - text: Set post-processing block {postProcessingId} enabled to {enabled}.
        slots:
          postProcessingId: path.postProcessingId
          enabled: requestBody.enabled
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/{projectId}/post-processing/{postProcessingId}/samples/{sampleId}'].post
  update:
    x-apievangelist-phrasing:
      intent: Check post-processing results for a sample
      effect: read
      questions:
      - Has post-processing already generated features for this sample?
      - How do I check a single sample's post-processing results for a model variant?
      instructions:
      - text: Check post-processing results for sample {sampleId} on block {postProcessingId} using the {variant} variant.
        slots:
          sampleId: path.sampleId
          postProcessingId: path.postProcessingId
          variant: requestBody.variant
      - text: Look up whether sample {sampleId} in project {projectId} has post-processing features yet.
        slots:
          sampleId: path.sampleId
          projectId: path.projectId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/{projectId}/post-processing/{postProcessingId}/samples/{sampleId}/classify'].post
  update:
    x-apievangelist-phrasing:
      intent: Classify a sample with post-processing
      effect: write
      questions:
      - How do I run a classification on a sample with post-processing applied?
      - Can I try different post-processing configs when classifying a sample?
      instructions:
      - text: Classify sample {sampleId} with post-processing block {postProcessingId} using config {config}.
        slots:
          sampleId: path.sampleId
          postProcessingId: path.postProcessingId
          config: requestBody.config
      - text: Run post-processed classification on sample {sampleId} in project {projectId} for the {variant} model variant.
        slots:
          sampleId: path.sampleId
          projectId: path.projectId
          variant: requestBody.variant
      method: generated
      generated: '2026-10-01'

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/edge-impulse-postprocessing-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.