What we process, and what that lets you see.

Altitude Intelligence is built on payer-published Transparency-in-Coverage (TiC) machine-readable files — the same files federal rule requires every commercial payer to publish monthly. We process them at national scale and make them useful for contracting decisions.

Source data.

We process in-network rate files published under CMS's Transparency in Coverage rule. The files are JSON, often 30+ GB unzipped per payer, and contain negotiated rates between commercial payers and in-network providers at the CPT/HCPCS code level.

We ingest files across both of the schema versions in active use (1.x and 2.0), handle the plan-instance-level structure different payers organize their files around, and reconcile the heterogeneity between payers so the data is comparable across them.

Payer coverage today.

Processing at production scale

  • Cigna (national, acute + behavioral health)

In active rollout

  • UnitedHealthcare (national, Q2 2026)

On the roadmap

  • Additional national commercial payers, prioritized by client pull

Geography.

National, with the important caveat that file completeness varies by payer, state, and plan type. We're transparent about coverage on a per-engagement basis — we'd rather tell you the data is thin for a specific payer-state combination than paper over it.

How we process differs from what you'll find elsewhere.

Most vendors in this space either sample the files (processing a subset of plans or providers), truncate them (dropping rare or edge-case records), or deliver them as flat API feeds that require the buyer to do their own analytical work.

We process the files at full resolution, maintain a unified multi-payer schema, and build client deliverables on top of the processed data — not under it.

What's not in scope today.

  • Out-of-network rate data. In scope for future build.

  • Allowed amounts files. TiC Phase 2 was deferred by CMS and enforcement is not yet in effect.

  • Medicare Advantage commercial-equivalent rates. Partially covered today, payer-dependent.

  • Claims data. A different problem, and not what we do. If you need claims-level analytics, we'll point you to partners.