Pull the allowed-amounts schema from the CMSgov/price-transparency-guide repository at the schema 2.0 revision and review its required top-level and nested fields.
For each out-of-network item or service, encode the billing code, billing code type, billing code type version, and description.
Within each claim object, encode the billed charge, the allowed amount, the service code, place of service code, and the provider's NPI and TIN using the schema 2.0 provider_reference structure.
Apply any applicable repricing method or reference-based pricing detail in the allowed amounts record as required by the schema.
Validate the file with the CMSgov/price-transparency-guide-validator specifying the allowed-amounts schema target.
Host the file at a stable public URL and update the index file to include a reference to the allowed amounts MRF alongside the in-network MRF entry.
Known gotchas
Billed charges must reflect the amount actually billed to the insurer for the specific claim instance, not a chargemaster rate; confusing these two figures is a common compliance error.
Each allowed amount entry must correspond to an individual claim observation, not an aggregate; averaging across claims and submitting a single row is not compliant.
The allowed amounts file can grow extremely large for high-volume payers; plan for gzip compression and verify that the public hosting infrastructure serves the compressed file with correct Content-Encoding headers so downloaders can decompress automatically.
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