Obtain an OAuth2 access token from the Availity authorization server using your client credentials; store the token for the request header
Construct the 270 transaction: ISA/GS envelope, ST loop with transaction set 270, Loop 2000A sponsor loop, Loop 2000B subscriber loop with member ID and date of service
POST the 270 payload (or its JSON equivalent if the API accepts JSON wrappers) to the Availity eligibility endpoint, setting the appropriate Content-Type and Authorization headers with YOUR_TOKEN
On a 200 response parse the 271: navigate Loop 2100C/2110C EB segments — EB01 (benefit type), EB02 (coverage level), EB03 (service type code), EB06 (time period qualifier), EB07 (monetary amount)
Check EB01 value '1' (active) vs '6' (inactive) to gate downstream workflow; extract AAA segments in any rejection loops for reason codes
Log the payer trace number from TRN segments (Loop 2000B or 2100B) for audit and re-inquiry correlation
Known gotchas
Availity's sandbox may return synthetic 271 data that does not match production payer behavior; always test against a real payer connection in UAT before go-live
The 270 must include the correct information receiver ID (payer ID) in Loop 2000B NM109 or the clearinghouse will reject with a TA1 interchange error
Real-time eligibility responses can include multiple EB loops for the same service type with different time qualifiers; iterate all EB loops rather than stopping at the first match
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp