Stedi Enrollment

Name: Stedi Enrollment API
Brand: Stedi Enrollment
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey15 EndpointsREST

For Agents

Programmatically deleteenrollmentdocument, createenrollmentdocumentdownload. Covers 15 operations with apiKey authentication.

Connect the Stedi Enrollment to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stedi Enrollment, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Stedi Enrollment API.

DeleteEnrollmentDocument

CreateEnrollmentDocumentDownload

CreateEnrollment

ListEnrollments

ExportEnrollmentsCsv

GET STARTED

Start building with Stedi Enrollment API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Stedi Enrollment, keeping it validated and agent-ready.

The Stedi Enrollment Service manages provider enrollments with healthcare payers. It tracks enrollment status, provider details, and supports batch enrollment processing to ensure providers have the necessary credentials before processing healthcare transactions. The API exposes 15 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use Stedi Enrollment API for, with concrete tasks.

★ Payments Operations

Use the Stedi Enrollment to perform payments operations programmatically. The API provides 15 endpoints covering core functionality including deleteenrollmentdocument, createenrollmentdocumentdownload, createenrollment.

Call DELETE /documents/{documentId} to deleteenrollmentdocument

Automated Documents Management

Automate documents operations by combining multiple Stedi Enrollment endpoints. Agents can createenrollmentdocumentdownload and then createenrollment in a single workflow.

Call GET /documents/{documentId}/download to createenrollmentdocumentdownload, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Stedi Enrollment 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.

Search Jentic for 'deleteenrollmentdocument', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — the stedi enrollment service manages provider enrollments with healthcare payers.

METHOD

PATH

DESCRIPTION

DELETE

/documents/{documentId}

DeleteEnrollmentDocument

GET

/documents/{documentId}/download

CreateEnrollmentDocumentDownload

POST

/enrollments

CreateEnrollment

GET

/enrollments

ListEnrollments

POST

/enrollments/export

ExportEnrollmentsCsv

POST

/enrollments/{enrollmentId}

UpdateEnrollment

GET

/enrollments/{enrollmentId}

GetEnrollment

DELETE

/enrollments/{enrollmentId}

DeleteEnrollment

DELETE

/documents/{documentId}

DeleteEnrollmentDocument

GET

/documents/{documentId}/download

CreateEnrollmentDocumentDownload

POST

/enrollments

CreateEnrollment

GET

/enrollments

ListEnrollments

POST

/enrollments/export

ExportEnrollmentsCsv

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Stedi Enrollment apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'deleteenrollmentdocument') and Jentic returns the matching Stedi Enrollment operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Stedi Enrollment integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Stedi Enrollment API through Jentic.

What authentication does the Stedi Enrollment use?

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

Can I deleteenrollmentdocument with the Stedi Enrollment?

Yes. Use the DELETE /documents/{documentId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Stedi Enrollment?

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

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'deleteenrollmentdocument'. Jentic returns the matching Stedi Enrollment operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Stedi Enrollment have?

The Stedi Enrollment exposes 15 endpoints covering documents, enrollments, providers operations.