Pull the in-network-rates schema from the CMSgov/price-transparency-guide repository and confirm you are using the schema 2.0 specification, which became assessable for compliance on February 2, 2026.
Structure each in-network provider rate record according to the schema 2.0 object model, which reduces file size by removing duplicative data fields compared to the prior schema version.
Include the required reporting entity name, reporting entity type, plan name, plan ID type, plan market type, and last_updated_on top-level fields in the file header object.
For each negotiated rate entry, encode the negotiated type (negotiated, fee schedule, percentage, or per diem), the negotiated rate value, the expiration date, and the provider references rather than embedding full provider data inline.
Produce a companion table-of-contents (index) file named using the required pattern and host both files at a publicly accessible URL, updating the index to reference the new in-network file.
Run the CMSgov/price-transparency-guide-validator against both files before publishing and resolve any schema 2.0 compliance errors.
Known gotchas
Schema 2.0 separates provider information into a provider_references array to reduce repetition; embedding provider NPI and TIN data inline for every rate entry (the schema 1.x pattern) will fail schema 2.0 validation.
The index file must use the CMS-specified naming convention including the date prefix; a mismatch causes automated aggregators to fail to ingest the file.
Plans that straddle the February 2, 2026 effective date must ensure files posted on or after that date conform to schema 2.0 even if the underlying data was assembled under the prior schema.
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