Pricing
Pricing for a living benefit data platform.
Health Plan API is not a one-time data export. It is a continuously validated, versioned, and cited benefit data service. Pricing follows that shape: bringing a plan in is a one-time event, trusting its answers over time is a subscription.
Design Partner
For teams with real coverage-lookup pain, right now.
limited slots, shaped with you
- Cited coverage answers for your plan set
- Pharmacy and drug coverage lookups included
- Concierge onboarding, direct access to the team
- Priority influence on carriers and modules
- Locked-in preferred terms as the platform scales
Resolver Subscription
Ongoing access to cited coverage answers.
tiered by lookup volume
- Query the normalized, validated plan corpus
- Portal, API, and MCP access
- Versioned plans with validation status
- Corrections and reprocessing as documents change
- Schema upgrades as the standard evolves
Enterprise
Full benefit data infrastructure at scale.
regulated, private, and high-scale environments
- Private ingestion of employer and carrier plans
- Audit-grade traceability and source references
- BAA and dedicated ingestion queues
- SLA-backed uptime and support
- Optional isolated environments
How pricing works
Two kinds of value, two kinds of pricing:
- Ingestion brings a document into the normalized corpus. One-time, per plan version.
- Resolution answers coverage questions from that corpus, with citations. Ongoing.
- Many public plans are already in the corpus, so many answers need no ingestion at all.
- Private and employer plans are ingested into your own isolated tenant.
Why a subscription
Benefit data does not sit still:
- Plans receive mid-year corrections, riders, and updates
- Validation rules improve as carrier behavior is discovered
- Standards evolve and schemas gain new modules
- A citation is only as good as the live source it points to
Data storage and redistribution
Health Plan API provides governed access to benefit data. Long-term storage, redistribution, or embedding of normalized plans outside your organization requires an explicit enterprise or redistribution license.
This ensures consistent interpretation, legal defensibility, and long-term data integrity across downstream systems.