Pricing
Pricing for a living benefit data platform.
HealthPlanAPI is not a one-time data export. It is a continuously validated, versioned, and governed benefit plan infrastructure.
Developer
Explore the standard and integration surface.
non-commercial • sandbox only
- Sandbox environment
- Sample normalized plans
- Limited API calls
- No commercial usage
Growth
Commercial access to public normalized plans.
per month • includes ongoing validation & updates
- Access to public normalized plan library
- Commercial usage rights
- Weekly updates and corrections
- Versioned plans with validation status
- Up to 10,000 API calls per month
- Schema upgrades as standards evolve
Enterprise
Full benefit data infrastructure at scale.
regulated, private, and high-scale environments
- Private ingestion pipelines
- Employer and carrier-specific plans
- Audit-grade traceability and source references
- Dedicated ingestion queues
- SLA-backed uptime and support
- Optional isolated environments
How pricing works
Normalizing a benefit plan is a discrete action. Trusting and using that plan over time is an ongoing service.
- Plans receive mid-year corrections, riders, and updates
- Validation rules improve as carrier behavior is discovered
- Standards evolve and schemas gain new modules
- Downstream decisions require defensible, traceable data
What subscriptions cover
A subscription provides ongoing access to:
- Versioned, validated benefit plans
- Corrections and reprocessing as documents change
- Query, filtering, and comparison APIs
- Schema upgrades and compatibility guarantees
- Operational reliability and availability
Ingestion and usage
- Ingestion fees apply when converting new documents into normalized plans
- API usage applies to retrieval, filtering, comparison, and analysis
- Subscriptions cover validation updates, schema evolution, and availability
Data storage and redistribution
HealthPlanAPI 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.