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

# Stedi Healthcare Claims

stedi.com/stedi-healthcare-claims-api version 2025-03-07. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically createclaimattachmentfile, submitclaimattachmentrawx12. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- CreateClaimAttachmentFile
- SubmitClaimAttachmentRawX12
- Integrate Stedi Healthcare Claims into automated workflows
- Query and filter Stedi Healthcare Claims records by parameters
- Monitor Stedi Healthcare Claims operational status and events

## Use cases

### Healthcare Operations

Use the Stedi Healthcare Claims to perform healthcare operations programmatically. The API provides 2 endpoints covering core functionality including createclaimattachmentfile, submitclaimattachmentrawx12.

Example prompt: Call POST `/claim-attachments/file` to createclaimattachmentfile

### Data Retrieval and Monitoring

Query Stedi Healthcare Claims resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Stedi Healthcare Claims endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Stedi Healthcare Claims 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 'createclaimattachmentfile', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/claim-attachments/file` | CreateClaimAttachmentFile |
| POST | `/claim-attachments/raw-x12-submission` | SubmitClaimAttachmentRawX12 |

## Key resources

- **Claim Attachments** — Operations for claim attachments

## Why Jentic

- **Setup:** Wiring Stedi Healthcare Claims by hand means handling its API-key auth in the Authorization header, targeting the US claims host at claims.us.stedi.com, and managing the X12 attachment payloads yourself. Through Jentic you install once, import Stedi Healthcare Claims from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API accepts the claim attachment in the request body rather than a resource id in the URL path, so scope it by operation: limit the agent to the operations it needs, such as submitting a claim attachment file or a raw X12 submission. You choose which of those operations are in the allowed set, so anything you do not add stays out of reach.
- **Credential handling:** Your Stedi Healthcare Claims 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 'attach a file to a healthcare claim' or 'submit a raw X12 claim attachment', and Jentic returns the matching Stedi Healthcare Claims 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 Claims use?

The Stedi Healthcare Claims 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 createclaimattachmentfile with the Stedi Healthcare Claims?

Yes. Use the POST `/claim-attachments/file` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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 createclaimattachmentfile through Jentic?

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

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

The Stedi Healthcare Claims exposes 2 endpoints covering claim attachments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Stedi Healthcare Claims operations and credentials the agent may use. This API takes the claim attachment in the request body rather than a resource id in the URL, so you scope it by operation: add only what the agent needs, such as creating a claim attachment file (POST `/claim-attachments/file`) or submitting a raw X12 attachment (POST `/claim-attachments/raw-x12-submission`). Anything you leave out of the allowed set stays out of the agent's reach.