availity
Availity is a healthcare information network and clearinghouse providing REST APIs for real-time HIPAA EDI transactions. The platform processes over 11 billion annual healthcare transactions connecting providers, health plans, and vendors nationwide. Create your application and subscribe to a plan to make use of Availity APIs for eligibility verification, claims management, prior authorization, and patient cost estimation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles availity the way a machine reads it — 164 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — availity scores 51.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile availity
Each block below is one kind of artifact we hold for availity. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Availity Healthcare HIPAA Transactions API
The Availity Healthcare HIPAA Transactions API provides a unified interface for standard HIPAA EDI transactions. REST APIs enable healthcare providers and vendors to submit and ...
Availity Patient Cost Estimator API
The Availity Patient Cost Estimator API enables healthcare providers and institutions to estimate service costs before delivery for both institutional and professional services....
Availity Eligibility & Benefits Value-Add APIs
The Availity Eligibility & Benefits Value-Add APIs provide supplementary data during eligibility transactions. The Care Reminders API retrieves real-time care gap information fr...
Availity Payer List API
The Availity Payer List API (v1.0.4) allows healthcare organizations to query available payers and the transactions they support. Returns payer identifiers, names, and supported...
Availity Configurations API
The Availity Configurations API (v1.0.0) provides provider details and payer-specific validation requirements. Returns configuration rules for enhanced claim status, prior autho...
availity Auth Attachments API
Attach documentation to authorization requests
availity Claim Attachments API
Electronic claim attachment submission and retrieval
availity Claim Status API
Claim status inquiries and tracking
availity Eligibility API
Real-time eligibility and benefits verification
availity Enhanced Claim Status API
Enhanced claim status with value-add data
availity Is Auth Required API
Check if authorization is required before submission
availity Service Reviews API
Prior authorization and service review requests
Scroll within the panel for all 12 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Availity Claim Attachments API
OPEN COLLECTIONAvaility Claim Status API
OPEN COLLECTIONAvaility Eligibility & Benefits API
OPEN COLLECTIONArazzo Workflows 4
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Availity Claim Attachment (X12 275)
Submit an X12 275 claim attachment, then poll for its processing status until the payer accepts it.
ARAZZOAvaility Claim Status Inquiry (X12 276/277)
Submit an X12 276 claim status request, then poll for the X12 277 claim status response until the payer finalizes it.
ARAZZOAvaility Eligibility and Benefits (X12 270/271)
Locate a payer that supports the 270 transaction, submit an X12 270 eligibility request, then retrieve the resulting 271 benefit response.
ARAZZOAvaility Prior Authorization (X12 278)
Determine whether authorization is required, create the X12 278 service review, attach supporting clinical documentation, then read back the authorization decision.
ARAZZOPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Availity Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Availity Finops
FINOPSSemantic Vocabularies 5
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Availity Availity Context
JSON-LDAvaility Claim Context
JSON-LDAvaility Context
JSON-LDAvaility Eligibility Context
JSON-LDAvaility Service Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
availity API Rules
SPECTRALavaility API Rules
SPECTRALJSON Schema 63
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AsyncJobResponse
JSON SCHEMAAttachmentRequest
JSON SCHEMAAttachmentStatusResponse
JSON SCHEMABenefit
JSON SCHEMAClaimAttachmentRequest
JSON SCHEMAClaimAttachmentResponse
JSON SCHEMAClaimStatusList
JSON SCHEMAClaimStatusRequest
JSON SCHEMAClaimStatusResponse
JSON SCHEMACoverage
JSON SCHEMADependent
JSON SCHEMADetailSearchRequest
JSON SCHEMAAvaility Eligibility Response
JSON SCHEMAEligibilityError
JSON SCHEMAEligibilityList
JSON SCHEMAEligibilityRequest
JSON SCHEMAEligibilityResponse
JSON SCHEMAError
JSON SCHEMAIsAuthRequiredRequest
JSON SCHEMAIsAuthRequiredResponse
JSON SCHEMAPayer
JSON SCHEMAPayerInfo
JSON SCHEMAPayerList
JSON SCHEMAPlanInformation
JSON SCHEMAProvider
JSON SCHEMASearchBy276Request
JSON SCHEMAServiceReviewList
JSON SCHEMAServiceReviewRequest
JSON SCHEMAServiceReviewResponse
JSON SCHEMASubscriber
JSON SCHEMASubscriberInfo
JSON SCHEMASummarySearchRequest
JSON SCHEMAClaimAttachmentRequest
JSON SCHEMAClaimAttachmentResponse
JSON SCHEMAAsyncJobResponse
JSON SCHEMAClaimStatusList
JSON SCHEMAClaimStatusRequest
JSON SCHEMAClaimStatusResponse
JSON SCHEMADetailSearchRequest
JSON SCHEMASearchBy276Request
JSON SCHEMASummarySearchRequest
JSON SCHEMABenefit
JSON SCHEMACoverage
JSON SCHEMADependent
JSON SCHEMAEligibilityError
JSON SCHEMAEligibilityList
JSON SCHEMAEligibilityRequest
JSON SCHEMAEligibilityResponse
JSON SCHEMAPayerInfo
JSON SCHEMAPayerList
JSON SCHEMAPayer
JSON SCHEMAPlanInformation
JSON SCHEMAProvider
JSON SCHEMASubscriberInfo
JSON SCHEMASubscriber
JSON SCHEMAAsyncJobResponse
JSON SCHEMAAttachmentRequest
JSON SCHEMAAttachmentStatusResponse
JSON SCHEMAIsAuthRequiredRequest
JSON SCHEMAIsAuthRequiredResponse
JSON SCHEMAServiceReviewList
JSON SCHEMAServiceReviewRequest
JSON SCHEMAServiceReviewResponse
JSON SCHEMAScroll within the panel for all 63 ·
JSON Structure 33
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Availity Eligibility Structure
JSON STRUCTUREAvaility Structure
JSON STRUCTUREClaim Attachments Claim Attachment Request Structure
JSON STRUCTUREClaim Attachments Claim Attachment Response Structure
JSON STRUCTUREClaim Status Async Job Response Structure
JSON STRUCTUREClaim Status Claim Status List Structure
JSON STRUCTUREClaim Status Claim Status Request Structure
JSON STRUCTUREClaim Status Claim Status Response Structure
JSON STRUCTUREClaim Status Detail Search Request Structure
JSON STRUCTUREClaim Status Search By276 Request Structure
JSON STRUCTUREClaim Status Summary Search Request Structure
JSON STRUCTUREEligibility Benefit Structure
JSON STRUCTUREEligibility Coverage Structure
JSON STRUCTUREEligibility Dependent Structure
JSON STRUCTUREEligibility Eligibility Error Structure
JSON STRUCTUREEligibility Eligibility List Structure
JSON STRUCTUREEligibility Eligibility Request Structure
JSON STRUCTUREEligibility Eligibility Response Structure
JSON STRUCTUREEligibility Payer Info Structure
JSON STRUCTUREEligibility Payer List Structure
JSON STRUCTUREEligibility Payer Structure
JSON STRUCTUREEligibility Plan Information Structure
JSON STRUCTUREEligibility Provider Structure
JSON STRUCTUREEligibility Subscriber Info Structure
JSON STRUCTUREEligibility Subscriber Structure
JSON STRUCTUREService Reviews Async Job Response Structure
JSON STRUCTUREService Reviews Attachment Request Structure
JSON STRUCTUREService Reviews Attachment Status Response Structure
JSON STRUCTUREService Reviews Is Auth Required Request Structure
JSON STRUCTUREService Reviews Is Auth Required Response Structure
JSON STRUCTUREService Reviews Service Review List Structure
JSON STRUCTUREService Reviews Service Review Request Structure
JSON STRUCTUREService Reviews Service Review Response Structure
JSON STRUCTUREScroll within the panel for all 33 ·
Examples 35
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Availity Eligibility Example
EXAMPLEEligibility Benefit Example
EXAMPLEEligibility Coverage Example
EXAMPLEEligibility Payer Example
EXAMPLEEligibility Provider Example
EXAMPLEScroll within the panel for all 35 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for availity — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/availity · machine-readable index on apis.io