Stedi
Stedi is the only API-first programmable healthcare clearinghouse, enabling health tech companies to submit claims, verify eligibility, and process electronic remittance advice (ERA) through a modern JSON API. The platform supports real-time X12 EDI transaction processing including eligibility checks (270/271), professional and institutional claim submissions (837), claim status inquiries (276/277), and electronic remittance advice (835). Stedi provides both SFTP and REST API access, webhooks for event-driven workflows, a sandbox test environment, and an MCP server for AI-assisted integration. Public OpenAPI specifications are available for all core APIs via the Stedi GitHub organization, and pricing is purely metered with no monthly minimums or setup fees.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Stedi the way a machine reads it — 47 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Stedi scores 54.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Stedi
Each block below is one kind of artifact we hold for Stedi. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Stedi Claim acknowledgments API
The Claim acknowledgments API from Stedi — 1 operation(s) for claim acknowledgments.
Stedi Claim Attachments API
The Claim Attachments API from Stedi — 2 operation(s) for claim attachments.
Stedi Claim submission API
The Claim submission API from Stedi — 8 operation(s) for claim submission.
Stedi Coordination of benefits API
The Coordination of benefits API from Stedi — 1 operation(s) for coordination of benefits.
Stedi Documents API
The Documents API from Stedi — 2 operation(s) for documents.
Stedi Enrollments API
The Enrollments API from Stedi — 4 operation(s) for enrollments.
Stedi Events API
The Events API from Stedi — 3 operation(s) for events.
Stedi Executions API
The Executions API from Stedi — 11 operation(s) for executions.
Stedi Fragments API
The Fragments API from Stedi — 1 operation(s) for fragments.
Stedi Insurance discovery API
The Insurance discovery API from Stedi — 2 operation(s) for insurance discovery.
Stedi Partnerships API
The Partnerships API from Stedi — 3 operation(s) for partnerships.
Stedi Payer API
The Payer API from Stedi — 1 operation(s) for payer.
Stedi Payers API
The Payers API from Stedi — 4 operation(s) for payers.
Stedi Polling API
The Polling API from Stedi — 2 operation(s) for polling.
Stedi Providers API
The Providers API from Stedi — 2 operation(s) for providers.
Stedi Real-time claim status API
The Real-time claim status API from Stedi — 2 operation(s) for real-time claim status.
Stedi Real-time eligibility check API
The Real-time eligibility check API from Stedi — 2 operation(s) for real-time eligibility check.
Stedi Remittances API
The Remittances API from Stedi — 2 operation(s) for remittances.
Stedi Tasks API
The Tasks API from Stedi — 1 operation(s) for tasks.
Stedi Transactions API
The Transactions API from Stedi — 11 operation(s) for transactions.
Stedi X12 API
The X12 API from Stedi — 1 operation(s) for x12.
Scroll within the panel for all 21 ·
Arazzo Workflows 5
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Stedi X12 276/277 Claim Status Inquiry
Resolve a claim-status-capable payer, run an X12 276 inquiry, and convert the X12 277 status report.
ARAZZOStedi X12 270/271 Eligibility and Benefits Check
Locate the right payer in the Stedi network, then run an X12 270 eligibility inquiry and read the 271 benefits response.
ARAZZOStedi Insurance Discovery
Start an insurance discovery check for a patient, then poll until the X12 270/271 coverage search completes and read the discovered coverage.
ARAZZOStedi X12 837 Professional Claim Lifecycle
Submit an X12 837 professional claim, check its 277 status, and retrieve the converted X12 835 remittance.
ARAZZOStedi Provider Enrollment for X12 835 ERA/EFT
Create a provider, open an enrollment, upload the signed agreement, and read the enrollment status for X12 835 ERA/EFT transactions.
ARAZZOPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Stedi Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Stedi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Stedi Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Stedi Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Stedi API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Stedi Claims Schemas
JSON SCHEMAStedi Core Schemas
JSON SCHEMAStedi Enrollment Schemas
JSON SCHEMAStedi Event-Destinations Schemas
JSON SCHEMAStedi Healthcare Schemas
JSON SCHEMAStedi Payers Schemas
JSON SCHEMAExamples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Stedi Claims Examples
EXAMPLEStedi Core Examples
EXAMPLEStedi Enrollment Examples
EXAMPLEStedi Healthcare Examples
EXAMPLEStedi Payers Examples
EXAMPLESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Stedi — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/stedi · machine-readable index on apis.io