# Soro Data, Healthcare Rate Data > Negotiated rates from 4,802 hospitals across 278,814 billing codes and 135 payers, quality-gated, cross-checked against the payer filings, and traceable to the row each one came from. Soro Data ## Every negotiated rate [Open the data platform](https://www.soro.health/go/data) [See pricing](https://www.soro.health/data-pricing) No seat yet? [Ask for a sample](https://www.soro.health/contact#data-sample) and we will send a real slice. **hospital-negotiated-rates.json** Live | Hospital | Code | Plan | Rate | | --- | --- | --- | --- | | Jersey Shore University Med Ctr | MS-DRG 470 | Horizon Indemnity | $114,356.00 | | Hackensack University Med Ctr | MS-DRG 470 | Horizon Indemnity | $104,610.00 | | Englewood Health | MS-DRG 470 | Horizon, all commercial | $55,646.82 | | Morristown Medical Center | MS-DRG 470 | Horizon BCBSNJ commercial | $47,170.00 | The corpus ### What the platform holds Hospitals **4,802** hospitals whose rate file we have pulled and parsed Billing codes **278,814** distinct billing codes tracked, across CPT, HCPCS, MS-DRG and revenue codes Verified at source **100%** of 5,471 sampled rates matched the live file on re-check Inside the platform ### The platform you log into A workspace over the whole corpus. Search a code and see every hospital that reports it, set one facility against the market, then take the slice out as a CSV or pull it from the API. [Open this at data.soro.health](https://www.soro.health/go/data) What is in there ### Four ways into the same corpus #### Compare Up to three facilities side by side on the same code: what each is paid, how each scores on quality, and how completely each one actually discloses. #### Benchmark Put one code against the whole market. You get the spread across every hospital that reports it, the distribution behind that spread, and each facility named with what it negotiated. #### Export builder Build a slice by source, code system, family and state, preview it, then take it as CSV, NDJSON or JSON. Saved slices can be rebuilt when the data refreshes. #### The API The same corpus programmatically. One bearer key, every endpoint a GET, amounts as plain numbers. [See what a subscription includes](https://www.soro.health/data-pricing) How a rate reaches you ### From two published files to one row you can cite ### Ask for a sample and check it yourself The rate data teams cite in a negotiation, with the source row attached to every figure. [Request a free sample](https://www.soro.health/contact#data-sample) Who uses it ### What people use it for #### Contract benchmarking See what every other facility in the market is paid for the same code by the same plan, before you sit down to renegotiate. #### Payment integrity Check what was paid against what was published. A claim priced above the rate the hospital itself posted is worth asking about, and the published file is the evidence. #### Research and disputes Every figure carries its provenance, so it survives contact with opposing counsel, a peer reviewer, or a hospital's finance office. Questions ### What buyers ask first **Can I get the market I care about?** Tell us the market and we will tell you where it sits. Holding a rate file and being willing to sell what is in it are two different bars, and packing runs market by market. Some markets are priced today. For the rest we will tell you what it takes, rather than selling you something that has not been through it. **How current is it?** The payer side is rebuilt monthly, because payers republish on a monthly cycle. The hospital side is re-checked against a stored baseline on the 1st and the 15th, and only what moved is re-fetched. **Is there any patient data in this?** None, by design. No claim or record is permitted to enter this platform, its storage, or a delivery bundle. It shares no store with the side of Soro that handles bills. --- This is the Markdown representation of , which also serves it under `Accept: text/markdown`. Site overview for agents: .