Home / Data, access and reuse

Data, access and reuse

The price data behind every page is available as JSON and CSV. It is meant to be checked, quoted and argued with.

5 sections74 products, 273 plans, 219 metersLatest recorded source date 2026-07-26Reviewed

Getting the data

The machine-readable files are served as JSON at /api/latest.json and as CSV at /prices.csv. They state the full record billing unit and how many records were withheld. A price row appears only after its source-redistribution rights are explicitly reviewed; unknown rights fail closed, so the current bulk files may contain metadata and headers without price rows even while the cited web pages remain available.

There is no key, no account and no rate limit worth mentioning. If you are pulling it on a schedule, once a day is plenty: the underlying vendor pages change a few times a year each.

What you may do with it

The prices themselves are facts about what companies charge, and facts are not ours to license. Publishing a public price with attribution and a date is ordinary practice, and these vendors publish each other's.

Our normalization, the billing-rule structure and the written explanations are our work. Quote them, build on them, and link back rather than republishing them wholesale.

Records are included in bulk exports only when their rights.public_pricing_page field is explicitly true. A missing rights decision and an explicit restriction are both withheld rather than silently treated as permission, and the JSON export reports each withheld count.

How to credit it

Name the site and the date you pulled the figure. The date matters more than the name: a scraping API price without a date is not a fact anyone can check.

If you are citing a computed bill rather than a published price, say what workload it was computed for. The same vendor can be the cheapest and the most expensive option in the same month depending on the job.

Using it in a product

Machine access is expected and welcome, including by answer engines and agents. The structured endpoints exist precisely so that a machine does not have to parse a page to get a figure right.

If you need a shape we do not publish, or a historical series, ask before scraping the pages for it. It is easier for both of us to add an endpoint.

Corrections and questions

Wrong number, missing vendor, or a billing rule we have misread: tell us which page and which figure. Vendor corrections are welcome and are checked against your own published documentation, which is the only thing that can settle it.

Reach us at data@scrapingapiprices.com.

Last materially reviewed: