Sondio Data Platform - Oil & Gas Wells and Production Data

Oil & Gas Drilling - one commercial aggregation layer over the whole American regulatory patch. Sondio pulls together the well listings and monthly production histories that state and federal agencies collect under statute, and serves them as a single queryable catalog: pick a country, narrow to a state, narrow further to a basin, and get wells back one row per borehole. Ask any single well for its production history and it returns month-by-month volumes over whatever rolling window you name - 120 months is the documented example.

The footprint underneath is the interesting part. The platform's own well search credits 27 upstream sources, led by the Texas Railroad Commission and running through the Alaska Oil and Gas Conservation Commission, the Arkansas Oil and Gas Commission, the Bureau of Land Management, BOEM, BSEE and a spread of state environmental quality departments. That is the onshore-plus-offshore span most analysts end up stitching together by hand from a dozen regulator portals, pre-assembled under one schema and one identifier scheme. Sondio ships sister verticals too - earthquakes, wind turbines, rail lines, agency-rule records such as EPA aquifer exemptions and PHMSA pipeline incidents - which makes it useful as an adjacency layer when a drilling thesis touches surface or midstream activity.

Get a sample of this dataset: name the states, basins or wells and rows arrive exactly in the shape documented below.

The documented shape comes in two halves - scope the wells, then walk one well backward through time:

Well listing - scoped by three filters
country : US
state   : TX
basin   : permian
-> one row per well, each carrying its platform identifier (external_id)

Production history - one well, one rolling window
external_id : <the identifier taken from the listing row>
months      : 120
-> one row per well-month: produced volumes across the requested span

Read the anatomy rather than the syntax. The first call is a geographic cut: nationwide, one state, or one basin - permian being the documented example - so a Permian-only acreage screen never has to download a statewide extract and throw half of it away. The second call is temporal: hand it the identifier from any listing row and a window length, and the history comes back month by month, which means decline curves, type curves and month-over-month comparisons fall straight out of the shape. Numeric and datetime values are coerced off their raw string form before you see them, so the parsing pass most regulatory extracts demand happens upstream.

The vendor publishes no column-level dictionary for either response, which is why this page documents the contract above and leaves exact column names to delivered rows. Live rows for whichever states, basins and wells you name ship with your sample.

Three elements are documented outright and anchor everything else: the external_id that gives every well one stable identity across the listing and its production history, the country / state / basin filters that define the geographic cut, and the months window that defines the temporal one. Treat those three as verified. The remaining columns - well identity, geography and status on the listing side, monthly volumes on the production side - follow the patterns of the 27 underlying regulatory sources, but the platform does not publish a per-column dictionary, so they sit under additional fields on request below and carry an inferred-confidence tag until your sample confirms them.

• Geo: United States, cut three ways - country, state, basin. The well search draws on 27 upstream sources led by the Texas Railroad Commission, with the Alaska and Arkansas conservation commissions, BLM, BOEM, BSEE and state environmental departments credited among the origins, so both onshore basins and federal offshore waters are represented.
• Temporal: Production history is pulled as a rolling month window - 120 months is the documented example - rather than a fixed archive start. How far back any individual well's series reaches is not published and gets settled against delivered rows.
• Granularity: Individual wells, with production reported per well per month - the grain decline analysis needs, not county rollups.

The differentiator against single-state regulators is breadth under one schema: the same identifier, filter vocabulary and monthly grain whether the well sits in Permian shale or Gulf federal waters.

API, files, or your warehouse. Daily, weekly, or hourly.

Ask for the whole catalog or just your acreage: every well in one basin, one operator's footprint across several states, or twelve years of monthly history for a shortlist of wells headed into a reserve report. Extracts arrive shaped to the dictionary above with identifiers intact, so listing rows join to their production series on arrival instead of after a reconciliation project. Sample first - request the states, basins and wells you actually work with, and check the columns against your own records before anything downstream depends on them.

• Data scientists get basin-scale panels with one join key, which is the tedious part of building production forecasts or anomaly detection over regulatory data. Patterns live on the data scientists use cases page.
• Investors and quant researchers run acreage screens - filter to a basin, pull rolling windows of monthly production, rank wells on trajectory - without maintaining a pipeline per state regulator. See investors quants use cases.
• Market researchers and consultants cite figures whose basis is mandated operator filings rather than sampling, and cover multi-state footprints from one place. See market researchers use cases.
• Developers and builders wire tabular well and production extracts into dashboards and valuation tools; the DataFrame-shaped responses mean no fixed-width parsers in the middle. See developers builders use cases.
• Journalists, academics and students trace any number back to the agency that collected it - useful when a story or thesis spans several states at once.
• Competitive intelligence teams track who operates what, where, and how it produces - basin by basin rather than press release by press release.

• Texas Railroad Commission Oil & Gas Data Sets - the deepest single upstream source behind this catalog, at weekly Full Wellbore file detail. Start here for breadth across states, there for Texas depth.
• BSEE Data Center - Offshore Well, Permit, Production & Platform Data - the federal offshore system of record; pairs with this platform's national scope when Gulf work goes deep.
• Colorado ECMC (COGCC) Data Portal - the Rocky Mountain counterpart when a basin screen crosses onto state land.
• GOGI Global Oil & Gas Infrastructure Features Database - global infrastructure context around the wells this platform catalogs.
• EIA U.S. Crude Oil & Natural Gas Active Well Service Rigs - activity counts that sit neatly beside well-level production when you need the drilling pulse, not just the output.

Three glossary notes sharpen the vocabulary before you commit: how well production data differs when cut per well versus per lease, what drilling permits actually certify, and why monthly production statistics lag the months they describe.

Three caveats ride with this record. First, the platform publishes no column-level dictionary for its well or production responses, so field definitions here carry an inferred-confidence tag until your sample confirms them. Second, total record count is not published; the credible bound is the 27-source upstream footprint, and sizing gets established against delivered rows. Third, no historical start date is documented - production arrives as the rolling window you request, and older vintages vary by source agency. None of these blocks a sample; all three get settled before anything depends on them.