Stedi APIs for AI Agents
Developer ToolsSource ControlEhr EmrThird-Party SpecsAPI keyAgent Ready
Stedi API Catalog
6 APIs across 3 product groups. All share one credential.
Developer Tools2
Healthcare2
Which Stedi API should I use?
| I want to... | Use | Why |
|---|---|---|
| Check patient eligibility or submit and status a claim | Stedi Healthcare | Runs real-time eligibility checks, claim status inquiries, and professional and institutional claim submissions in JSON or raw X12. |
| Attach a document to a healthcare claim | Stedi Healthcare Claims | Handles claim attachment files and raw X12 attachment submissions, which the main healthcare API does not cover. |
| Run eligibility for many members at once | Stedi Manager | Starts batch eligibility runs, polls them to completion, and returns batch items and per-check PDFs. |
| Look up which payer to route a transaction to | Stedi Payers | Searches and lists the payer directory and returns individual payer records by Stedi id. |
| Track a provider's enrollment with a payer | Stedi Enrollment | Creates, updates, lists, and exports provider enrollments and their supporting documents. |
| Inspect or retry the processing behind a transaction | Core | Lists executions, reads their faults and input, and retries failed events and executions. |
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the six Stedi APIs by hand means configuring the Authorization header key against separate dated US regional hosts for healthcare, claims, enrollment, payers, and the core engine, and threading ids between them yourself. Through Jentic you install once, add the Stedi APIs you need from the Jentic API Directory, store the one API key, and your agent calls them.
Permission scoping
Your own rules decide which Stedi operations an agent may call, so a read-only agent can look up payers, check eligibility, and read enrollments while claim submission, enrollment deletion, and execution retries stay out of reach unless you add them. Where an API puts a resource id in the path, such as an enrollment or execution id, a rule can pin the agent to a single record.
Credential isolation
FAQs
Specific to using Stedi APIs through Jentic.
What can an agent do across the Stedi APIs?
An agent can check patient eligibility, submit professional and institutional claims and their attachments in JSON or raw X12, poll claim status, run batch eligibility jobs, look up payers in the directory, track provider enrollments, and inspect or retry the executions that process these transactions. These span the healthcare, enrollment, payer, and core execution APIs.
Do the Stedi APIs share one set of credentials?
Yes. All six APIs use the same apiKey model, with a Stedi API key passed in the Authorization header, so a single credential covers eligibility, claims, enrollment, payer lookup, and the core execution engine.
Which Stedi API should I use for a given task?
Use the Stedi Healthcare API for eligibility, claim status, and claim submission; the Stedi Healthcare Claims API for claim attachments; the Stedi Manager API for batch eligibility; the Stedi Payers API for the payer directory; the Stedi Enrollment API for provider enrollments; and the Stedi Core API to inspect and retry the executions behind them.
Do the Stedi APIs support raw X12 as well as JSON?
Yes. The healthcare and claims APIs accept both JSON and raw X12 for eligibility checks, claim submissions, and claim attachments, so an agent can work in whichever format the downstream payer or workflow requires.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
