canonical: https://jentic.com/apis/stedi.com/stedi-healthcare

# Stedi Healthcare

Stedi Healthcare provides programmatic access to healthcare functionality. The API exposes 22 endpoints secured with apiKey authentication.

## For AI agents

Programmatically claimstatus, claimstatusrawx12. Covers 22 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for healthcare only.

## Capabilities

- ClaimStatus
- EligibilityCheck
- EligibilityRawX12Check
- InstitutionalClaimsRawX12Submission
- InstitutionalClaimsSubmission
- ClaimsRawX12Submission

## Use cases

### Healthcare Operations

Use the Stedi Healthcare to perform healthcare operations programmatically. The API provides 22 endpoints covering core functionality including claimstatus, claimstatusrawx12, eligibilitycheck.

Example prompt: Call POST `/change/medicalnetwork/claimstatus/v2` to claimstatus

### Automated change Management

Automate change operations by combining multiple Stedi Healthcare endpoints. Agents can claimstatusrawx12 and then eligibilitycheck in a single workflow.

Example prompt: Call POST `/change/medicalnetwork/claimstatus/v2/raw-x12` to claimstatusrawx12, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stedi Healthcare endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'claimstatus', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/change/medicalnetwork/claimstatus/v2` | ClaimStatus |
| POST | `/change/medicalnetwork/claimstatus/v2/raw-x12` | ClaimStatusRawX12 |
| POST | `/change/medicalnetwork/eligibility/v3` | EligibilityCheck |
| POST | `/change/medicalnetwork/eligibility/v3/raw-x12` | EligibilityRawX12Check |
| POST | `/change/medicalnetwork/institutionalclaims/v1/raw-x12-submission` | InstitutionalClaimsRawX12Submission |
| POST | `/change/medicalnetwork/institutionalclaims/v1/submission` | InstitutionalClaimsSubmission |
| POST | `/change/medicalnetwork/professionalclaims/v3/raw-x12-submission` | ClaimsRawX12Submission |
| POST | `/change/medicalnetwork/professionalclaims/v3/submission` | ClaimsSubmission |

## Key resources

- **change** — Operations related to change
- **coordination-of-benefits** — Operations related to coordination-of-benefits
- **dental-claims** — Operations related to dental-claims
- **electronic-remittance-advice** — Operations related to electronic-remittance-advice
- **export** — Operations related to export

## Why Jentic

- **Setup:** Wiring Stedi Healthcare by hand means handling its API-key auth in the Authorization header, targeting the US healthcare host at healthcare.us.stedi.com, and formatting the eligibility, claim-status, and X12 claim payloads yourself. Through Jentic you install once, import Stedi Healthcare from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** These operations take their subject in the request body rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as running an eligibility check or a claim-status inquiry. You pick which operations are in the allowed set, so submission operations you do not add are not available to the agent.
- **Credential handling:** Your Stedi Healthcare API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check patient eligibility' or 'look up a claim status', and Jentic returns the matching Stedi Healthcare operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Oystehr** — Alternative healthcare API
- **Athenahealth** — Alternative healthcare API

## FAQ

### What authentication does the Stedi Healthcare use?

The Stedi Healthcare uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I claimstatus with the Stedi Healthcare?

Yes. Use the POST `/change/medicalnetwork/claimstatus/v2` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stedi Healthcare?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I claimstatus through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'claimstatus'. Jentic returns the matching Stedi Healthcare operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stedi Healthcare have?

The Stedi Healthcare exposes 22 endpoints covering change, coordination-of-benefits, dental-claims operations.

### Can I limit what my agent is allowed to do with the Stedi Healthcare API?

Yes. Because you run Jentic One yourself and control which operations you import, you decide the exact set of Stedi Healthcare calls your agent can make. Each operation takes its subject in the request body rather than a resource ID in the path, so you scope by operation: for example, allow an eligibility check or a claim-status inquiry while leaving institutional or professional claim submission out of the allowed set. Any operation you do not add is simply unavailable to the agent, and your stored API key is injected only for the calls you have permitted.