Eligibility
Eligibilityeligibility
Providers using this tag (53)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 11 Limited public surface area
Emerging 9 Early or largely undocumented
APIs with this tag (54)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 5 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 53 providers in the APIs.io catalog tagged Eligibility, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 43.8 | 17.5 | +26.3 | 53 |
| Developer Ergonomics | 39.4 | 17.9 | +21.5 | 53 |
| Access Clarity | 38.8 | 22.3 | +16.5 | 53 |
| Discoverability | 74.5 | 60.4 | +14.1 | 53 |
| Contract Governance | 18.2 | 6.4 | +11.8 | 53 |
| Operational Transparency | 22.8 | 11.3 | +11.5 | 53 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 32% | 16% | +16 |
| MCP server (first-party) | 15% | 7% | +8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 32% | 9% | +23 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 30% | 13% | +17 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Stedi 85.6
- 2 Elation Health 84.1
- 3 Availity 75.4
- 4 Candid Health 64.7
- 5 Ribbon Health 64.2
- 6 Turquoise Health 63.8
- 7 Optum 63.4
- 8 Blockchain.com 59.7
- 9 Splitit 57.5
- 10 pVerify 56.5
- 1 Bluecore 54.1
- 2 Stedi 52.9
- 3 Turquoise Health 48.6
- 4 Elation Health 48.1
- 5 PlanSource 45.1
- 6 Color 43.7
- 7 Optum 42.6
- 8 Remote 41.3
- 9 Candid Health 39.6
- 10 Orum 38.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/eligibility"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/eligibility"
curl "https://apis.io/api/v1/cohorts/tag/eligibility/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.