Pipeline tariff data, consolidated.
Oil pipeline rates reach the public record as PDFs, operator by operator, filing by filing. We read them, normalize what they contain, and deliver the result in the format your systems already use.
02 │ Origin Station, Harris County, TX │ Delivery Terminal, Fulton County, GA │ [I] 31.39
- origin.station
- Origin Station
- origin.county
- Harris
- origin.state
- TX
- destination.state
- GA
- value
- 31.39
- currency
- US cents / barrel
- reference_mark
- [I] increase
- source
- page 4, line 12
The data is public. Using it is the work.
A single filing carries a base rate table plus incentive tiers, each repeating the same origin and destination pairs at a different rate. Footnotes narrow individual routes to one product. Marks in the margin flag which values moved, and the legend explaining them is often incomplete.
Every operator lays it out differently. Multiply by the pipelines you track, and by every filing they make, and you have a standing job that never quite finishes, or a feed in someone else's format that you spend the saved time re-mapping into your own.
Consolidate, normalize, deliver.
One relationship instead of a filing cabinet.
Consolidate
We work from published tariff filings across the operators you track, so the rates arrive in one place on one schedule instead of being gathered document by document.
Normalize
Wording varies between operators. We reconcile it, so a rate type, a product and a unit mean the same thing across your whole dataset rather than whatever each filing happened to call them.
Deliver in your format
Your column names, your key structure, your delivery mechanism. If you already consume a rates feed, we match that contract instead of asking you to adopt ours.
A tariff is a legal document, not a table.
The parts that get lost in a careless read are the parts that quietly corrupt a rates database. These are the ones we handle deliberately.
Rate tables and tiers
Base tables and volume-incentive tiers stay distinct, so one route at three rates remains three records rather than collapsing into one wrong one.
Footnotes
Kept with the routes they apply to, so a rate restricted to a single product is never silently generalized to all of them.
Reference marks
Increase, new, unchanged and wording marks are captured, including marks a filing uses but never defines in its own legend.
Origins and destinations
Decomposed into station, sub-station, city, county and state, with the original text preserved and anything ambiguous flagged rather than guessed.
Effective dates
Issued and effective dates, the governing tariff, and the filing each one supersedes, so a rate is always anchored to when it actually applies.
Currency and measure
The unit caption that establishes currency and volume measurement is read and applied, rather than assumed from the last document that looked similar.
Every value traces back to the page it came from.
Each rate we deliver records the page and the line of text it was read from. Automated reading does the volume; the record keeps the receipt. Anything uncertain is flagged rather than quietly filled in, and nothing reaches you without having been looked at.
Data you cannot check against the filing is not data. It is a guess with good formatting. That is why provenance travels with every record rather than sitting in a report somewhere.
However you already take data in.
- Mechanism
- A REST API, an SFTP drop, or scheduled flat files, whichever your systems already consume.
- Formats
- CSV, Excel or JSON, shaped to your column names and key structure rather than ours.
- Cadence
- Tariffs change on effective dates rather than continuously, so we work to your calendar: per filing, or on a schedule that suits your reporting cycle.
- Scope
- Tell us which operators you track and what you need in the record. Coverage is built around your requirements rather than a fixed catalogue.
- Deployment
- Hosted by us, or run inside your own tenant, region or private network path where your requirements call for it.
Where the data comes from, and what it is not.
- Public filings
- Tariff Lens works from tariffs filed with FERC and state regulators and published by the operators themselves. These are public record. We link to the issuing party's own published document and do not re-host or redistribute their PDFs.
- The filing governs
- What we deliver is a derived extraction, not the tariff itself. Where our data and the filed tariff disagree, the filed tariff is authoritative. The provenance on every record exists so that any value can be checked against it.
- No affiliation
- Binmodules is independent. We are not affiliated with, endorsed by, sponsored by, or acting on behalf of any regulator or pipeline operator, and we hold no special or non-public access to filings. Where company or pipeline names appear, they identify the source of the data and nothing more.
Start with a filing you already know
The fastest way to judge this is a tariff you have already worked through by hand. Send one over with the operators you track and the shape you need, and we will come back with the data in that format.
tariff-lens@binmodules.comWhere our data comes from: sources & independence →