Versioning & changelog

The public API uses a global major version in its URL: /api/v1. Compatible additions can remain within v1. Breaking changes require a new major version and a documented migration path.

Consumers should tolerate additional response fields. Existing field meanings and types should remain stable within a major version.

An API version defines the interface. A CMS data release defines the source data. A new fee-schedule release does not, by itself, require a new API version.

date selects the service date, not a frozen copy of the dataset. Rates identify their accepted release and optionally include exact source provenance. Explicit release pinning is not supported.

Final monetary amounts are integers in the currency's minor unit. For USD, that means cents. A real zero is 0; an unavailable amount is null.

Calculation factors requiring more precision use exact decimal strings. Keep decimal arithmetic throughout calculations and convert the final rounded amount to cents.

Resource expansion · October 6, 2026

Added separate code search, date-specific code facts, batch rates, locality discovery, accepted releases, utilization, curated code sets, and therapy estimates. Rates now support 26/TC components, provider pricing, release IDs and optional breakdown/source expansions. Every successful bounded data request counts once.

Initial v1 implementation · October 6, 2026

The first rate contract covers a single code, facility or non-facility setting, national or local geography, service date, and optional QP status. The rate endpoint is implemented with API-key authentication and plan metering.

Team API keys and the GET /api/v1/me account endpoint are implemented in the application. Deployment is managed separately from this implementation changelog.