Stedi · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Stedi Healthcare Real-time eligibility check API

3 actions 3 updates phrasing extends openapi/stedi-real-time-eligibility-check-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Stedi's API. It is a proposal applied on top of the contract, not a document Stedi publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/change/medicalnetwork/eligibility/v3'].post
$.paths['/change/medicalnetwork/eligibility/v3/raw-x12'].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 Stedi Healthcare Real-time eligibility check API
  version: 1.0.0
extends: openapi/stedi-real-time-eligibility-check-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['/change/medicalnetwork/eligibility/v3'].post
  update:
    x-apievangelist-phrasing:
      intent: Check a patient's eligibility in real time
      effect: read
      questions:
      - How do I verify a patient's insurance coverage and benefits before an appointment?
      - Can I check eligibility for a patient's dependents in the same request?
      - What is the minimum patient information a real-time 270 eligibility check needs?
      instructions:
      - text: Check eligibility with payer {tradingPartnerServiceId} for subscriber {subscriber} from provider {provider}.
        slots:
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
          subscriber: requestBody.subscriber
          provider: requestBody.provider
      - text: Verify benefits for subscriber {subscriber} and dependents {dependents}.
        slots:
          subscriber: requestBody.subscriber
          dependents: requestBody.dependents
      - text: Run a JSON eligibility check for patient {externalPatientId} at payer {tradingPartnerServiceId}.
        slots:
          externalPatientId: requestBody.externalPatientId
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/change/medicalnetwork/eligibility/v3/raw-x12'].post
  update:
    x-apievangelist-phrasing:
      intent: Check eligibility with raw X12
      effect: read
      questions:
      - Can I send a 270 eligibility request as raw X12 and get a 271 back?
      - Which endpoint accepts X12 EDI for real-time eligibility?
      instructions:
      - text: 'Send this X12 270 eligibility request: {x12}.'
        slots:
          x12: requestBody.x12
      - text: Run a raw EDI eligibility check {x12} for patient {externalPatientId}.
        slots:
          x12: requestBody.x12
          externalPatientId: requestBody.externalPatientId
      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/stedi-real-time-eligibility-check-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.