The Insurance Eligibility API Built for AI Agents

May 15, 2026

insurance eligibility APIAI agentsVoice AIeligibility checkreal-time verification

The Insurance Eligibility API Built for AI Agents

Most insurance eligibility APIs were designed for billing staff running batch checks overnight. That works for RCM. It doesn't work when a Voice AI agent needs to verify a patient's coverage in the middle of a phone call.

Eligibility.dev is built for real-time AI agent workflows. Here's what that means in practice.

What AI Agents Need from an Eligibility API

When a Voice AI agent handles a patient call, it has a window of a few seconds to gather information, run a check, and respond naturally. The eligibility API has to fit inside that window.

That means:

Sub-second response time. Patients don't wait. If the check takes 5 seconds, the conversation breaks. Eligibility.dev returns results in under 1 second for the large majority of payers.

Structured JSON output. The agent needs to read the response and branch on it — is coverage active? What's the copay? A plain-text response or a raw X12 271 transaction is useless to an AI agent without a parsing layer on top. Eligibility.dev returns clean JSON every time.

A single endpoint for all payers. Voice AI agents don't know in advance which payer a patient has. The API has to accept a payer ID and route correctly without any per-payer configuration. Eligibility.dev covers 1,152+ payers through one endpoint with one request format.

No clearinghouse contract. AI agencies aren't healthcare billing companies. They shouldn't need to negotiate a clearinghouse agreement, handle payer enrollment, or test X12 EDI transactions. Eligibility.dev handles all of that on your behalf.

How It Works in a Voice AI Workflow

Here's a typical integration pattern with a Voice AI front desk agent on Bland AI, Retell, or Vapi:

  1. Patient calls the clinic. The AI agent answers.
  2. Agent collects: first name, last name, date of birth, insurance member ID, payer name.
  3. Agent maps the payer name to a payer ID using a lookup table or a built-in intent.
  4. Agent calls the Eligibility.dev API with the patient data and clinic NPI.
  5. API returns coverage status, deductible, copay, and plan details in under 1 second.
  6. Agent confirms coverage with the patient and continues booking, or flags the issue and routes to a human.

The entire check happens mid-conversation. The patient never waits for a callback.

The API Request

GET /api/eligibility/check
Authorization: Bearer <your-api-key>

{
  "npi": "1234567890",
  "member_id": "XYZ123456",
  "payer_id": "00001",
  "first_name": "Jane",
  "last_name": "Doe",
  "date_of_birth": "1985-04-12"
}

Same request format for Cigna, Blue Cross Blue Shield, Aetna, UnitedHealthcare, Humana, Medicare, Medicaid — every payer. The payer_id routes to the right payer. Nothing else changes.

The API Response

{
  "coverage_status": "active",
  "plan_name": "Blue Cross PPO Select",
  "group_number": "GRP-00123",
  "deductible_individual": 1500,
  "deductible_individual_met": 400,
  "deductible_individual_remaining": 1100,
  "out_of_pocket_max_individual": 5000,
  "out_of_pocket_max_individual_met": 400,
  "copay_primary_care": 30,
  "coinsurance": 20,
  "effective_date": "2026-01-01",
  "payer_name": "Blue Cross Blue Shield",
  "payer_id": "00001"
}

Your AI agent reads coverage_status first. If active, it surfaces the copay. If inactive, it routes to a human or sends a follow-up SMS through GHL.

Testing Without a Real Patient

Every Eligibility.dev account includes access to a mock endpoint that returns realistic eligibility responses — no real NPI, no real payer, no subscription needed.

GET https://www.eligibility.dev/api/eligibility/check/mock

Use it to build and test your Voice AI integration before you've set up a live clinic. Same request format, same JSON response, zero risk.

Getting Started

  1. Sign up at eligibility.dev — no card required
  2. Create a workspace (takes about 2 minutes)
  3. Hit the mock endpoint immediately with your API key
  4. Add your first clinic with the clinic's NPI when you're ready to go live
  5. Pick a plan and switch to the live endpoint

From signup to first mock check: under 5 minutes. From first mock check to first live check: under 20 minutes if you have the NPI.

FAQ

What Voice AI platforms does this work with?
Bland AI, Retell, Vapi, and any other platform that supports outbound HTTP calls or webhooks. If it can make a REST API call, it can use Eligibility.dev.

What if the AI agent doesn't know the payer ID?
You can map common payer names to IDs in a lookup table, or use a fuzzy match on the payer name field. The full payer list with IDs is available at eligibility.dev/payers.

How do I handle a failed check mid-call?
Build a fallback branch: if the check fails or returns inactive, route to a human, send a follow-up task in GHL, or ask the patient to call back with updated insurance info. Don't let the agent stall.

Is this HIPAA compliant?
Yes. See our security documentation for data handling details and BAA availability.

Can one agency account cover multiple clinics?
Yes. Each clinic gets its own NPI and configuration under your agency workspace. Adding a second clinic takes under 2 minutes.