Build with AI
Stedi provides AI-powered tools and resources to help you build eligibility and claims processing workflows faster.
- Build agents that work with eligibility data: Install the Model Context Protocol (MCP) server
- Code with AI assistants: Give them AI-friendly versions of our developer guides and API specifications
Model Context Protocol server
The Model Context Protocol (MCP) server provides tools that AI agents can use to perform and troubleshoot eligibility checks through Stedi's APIs. It includes built-in logic for finding the correct payer, handling errors, and implementing retry strategies, so you can focus on building your agent's core functionality.
The MCP server is ideal for:
- Voice agents that need to verify benefits in real time
- Revenue Cycle Management (RCM) workflow agents that validate coverage before scheduling appointments
- Development teams using MCP clients to test integrations and troubleshoot issues
The MCP server supports both API key and OAuth 2.x authentication, and works with popular AI platforms like Claude Code.
AI-friendly documentation
Stedi's documentation is available in AI-friendly formats that you can provide to tools like ChatGPT, Claude, Cursor, and other AI assistants.
For best results, provide both OpenAPI specifications and llms-full.txt for comprehensive developer guides.
OpenAPI specifications
OpenAPI specifications provide machine-readable API definitions including endpoints, parameters, request/response schemas, and real-world examples.
When to use: Provide these to your AI assistant when you need it to help you generate API calls, understand API structure, or validate request and response formats.
llms.txt
A simple list of available documentation pages with titles and descriptions.
When to use: Use this to give your AI assistant a quick overview of available pages. Many AI assistants check for this file automatically.
llms-full.txt
The complete markdown content of all documentation pages in a single file. This includes guides, how-tos, troubleshooting, and conceptual explanations.
When to use: Provide this to your AI assistant when you need comprehensive context about how to build eligibility and claims processing workflows with Stedi.
Individual markdown pages
Individual documentation pages are available in markdown format at /llms.mdx/[page-url]. For example, /llms.mdx/healthcare/send-eligibility-checks. You can also copy them from the UI by clicking the Copy for LLM menu at the top of each documentation page.
When to use: Use individual pages when you have token limits that prevent loading llms-full.txt, or when you only need context about specific features.
How to use these resources
Follow your organization's data handling policies to ensure you stay compliant with HIPAA and other applicable requirements. Your organization likely requires a Business Associate Agreement (BAA) with any third-party AI tool before using it with production healthcare data.
The specific method depends on which AI tool you're using.
You may want to add references to your agent's configuration - for example, a Cursor rule or Claude skill file. This ensures the context is applied automatically across sessions.
You have access to Stedi's healthcare API documentation and specifications:
- Full documentation: https://www.stedi.com/docs/llms-full.txt
- OpenAPI specs: https://github.com/Stedi/openApi
When helping with Stedi integrations, consult these resources first.You can also provide these resources as context when starting a conversation with tools like ChatGPT, Claude, or Google Gemini.
I'm working with Stedi's healthcare APIs. Please reference:
- Full documentation: https://www.stedi.com/docs/llms-full.txt
- OpenAPI specs: https://github.com/Stedi/openApi
Help me [describe your task].Example prompts
Once your AI assistant has access to the documentation, you can ask it to help with tasks like:
- "Help me implement eligibility checks for a new RCM system. Show me how to construct the JSON request and handle the response."
- "Generate TypeScript code to submit professional claims using Stedi's API, including error handling and retry logic."
- "What's the correct Claim Frequency Code for resubmitting an institutional claim that was already adjudicated?"
Always review and test AI-generated code before using it in production. While AI assistants can help you build integrations faster, you should verify that the generated code meets your specific requirements and follows your organization's standards.