Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically batcheligibilitychecks, getbatch. Covers 5 operations with apiKey authentication.
Use for: I need to batcheligibilitychecks, I want to getbatch, Search for getbatchitems, Find all geteligibilitycheckpdf
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
stedi.com/stedi-manager-api version 2024-04-01. The API exposes 5 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stedi Manager, 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-manager" | 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-manager" | 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 Manager API.
BatchEligibilityChecks
GetBatch
GetEligibilityCheckPdf
BatchEligibilityPolling
Monitor Stedi Manager operational status and events
Patterns agents use Stedi Manager API for, with concrete tasks.
★ Developer Tools Operations
Use the Stedi Manager to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including batcheligibilitychecks, getbatch, getbatchitems.
Call POST /eligibility-manager/batch-eligibility to batcheligibilitychecks
Automated Eligibility Manager Management
Automate eligibility manager operations by combining multiple Stedi Manager endpoints. Agents can getbatch and then getbatchitems in a single workflow.
Call GET /eligibility-manager/batch/{batchId} to getbatch, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Stedi Manager 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 'batcheligibilitychecks', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — stedi.
METHOD
PATH
DESCRIPTION
/eligibility-manager/batch-eligibility
BatchEligibilityChecks
/eligibility-manager/batch/{batchId}
GetBatch
/eligibility-manager/batch/{batchId}/items
GetBatchItems
/eligibility-manager/eligibility-checks/{eligibilityCheckId}/pdf
GetEligibilityCheckPdf
/eligibility-manager/polling/batch-eligibility
BatchEligibilityPolling
/eligibility-manager/batch-eligibility
BatchEligibilityChecks
/eligibility-manager/batch/{batchId}
GetBatch
/eligibility-manager/batch/{batchId}/items
GetBatchItems
/eligibility-manager/eligibility-checks/{eligibilityCheckId}/pdf
GetEligibilityCheckPdf
/eligibility-manager/polling/batch-eligibility
BatchEligibilityPolling
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Stedi Manager by hand means handling its API-key auth in the Authorization header, targeting the US manager host at manager.us.stedi.com, and polling batch eligibility jobs to completion yourself. Through Jentic you install once, import Stedi Manager from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Stedi Manager puts the batch id in the URL path (/eligibility-manager/batch/{batchId}/...), so a rule can pin your agent to reading one batch and its items. You choose the operations it may call, so starting new batch eligibility runs is not included unless you add it.
Credential isolation
Your Stedi Manager 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 'start a batch eligibility run' or 'get the items in an eligibility batch', and Jentic returns the matching Stedi Manager 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Stedi Manager API through Jentic.
What authentication does the Stedi Manager use?
The Stedi Manager 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 batcheligibilitychecks with the Stedi Manager?
Yes. Use the POST /eligibility-manager/batch-eligibility endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Stedi Manager?
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 batcheligibilitychecks through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'batcheligibilitychecks'. Jentic returns the matching Stedi Manager operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Stedi Manager have?
The Stedi Manager exposes 5 endpoints covering eligibility manager operations.
Can I limit what my agent is allowed to do with the Stedi Manager API?
Yes. Because you self-host Jentic One, your own rules decide which Stedi Manager operations and credentials your agent may use. Since the API puts the batch id in the URL path (/eligibility-manager/batch/{batchId}/items), you can pin the agent to reading a single batch and its items or fetching a check PDF, while leaving out starting new batch eligibility runs with POST /eligibility-manager/batch-eligibility. Only the operations you explicitly allow are available to the agent.
GET STARTED