Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstedi.com%2Fstedi-enrollment" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstedi.com%2Fstedi-enrollment" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Stedi Enrollment API.
DeleteEnrollmentDocument
CreateEnrollmentDocumentDownload
CreateEnrollment
ListEnrollments
ExportEnrollmentsCsv
GET STARTED
UpdateEnrollment
GetEnrollment
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
15 endpoints — the stedi enrollment service manages provider enrollments with healthcare payers.
METHOD
PATH
DESCRIPTION
/documents/{documentId}
DeleteEnrollmentDocument
/documents/{documentId}/download
CreateEnrollmentDocumentDownload
/enrollments
CreateEnrollment
/enrollments
ListEnrollments
/enrollments/export
ExportEnrollmentsCsv
/enrollments/{enrollmentId}
UpdateEnrollment
/enrollments/{enrollmentId}
GetEnrollment
/enrollments/{enrollmentId}
DeleteEnrollment
/documents/{documentId}
DeleteEnrollmentDocument
/documents/{documentId}/download
CreateEnrollmentDocumentDownload
/enrollments
CreateEnrollment
/enrollments
ListEnrollments
/enrollments/export
ExportEnrollmentsCsv
/enrollments/{enrollmentId}
UpdateEnrollment
/enrollments/{enrollmentId}
GetEnrollment
/enrollments/{enrollmentId}
DeleteEnrollment
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Stedi Enrollment API by hand means setting up its Authorization header key, targeting the US region host with its dated path, and threading enrollment and document ids through the export and download calls yourself. Through Jentic you install once, import the Stedi Enrollment API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Enrollment API puts the enrollment id in the URL path (/enrollments/{enrollmentId}), so a rule can pin your agent to one enrollment: it can read and update that enrollment and nothing else. You choose the operations it may call, so deleting an enrollment or a document is not included unless you add it.
Credential isolation
Your Stedi 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.
Intent-based discovery
Agents search Jentic by intent such as 'create an enrollment' or 'download an enrollment document', and Jentic returns the matching Stedi Enrollment operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the Stedi Enrollment API?
Yes. Because you run Jentic One yourself, you write the rules that decide which Stedi Enrollment operations and credentials your agent may use. Since the enrollment id lives in the URL path (/enrollments/{enrollmentId}), you can pin the agent to a single enrollment so it only reads and updates that one and touches nothing else. You also choose the operations it may call, so destructive actions like DELETE /enrollments/{enrollmentId} or DELETE /documents/{documentId} stay off unless you explicitly allow them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically deleteenrollmentdocument, createenrollmentdocumentdownload. Covers 15 operations with apiKey authentication.
Use for: I need to deleteenrollmentdocument, I want to createenrollmentdocumentdownload, Search for createenrollment, Find all listenrollments
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
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.