What Bluestem actually delivers.

Crawley Petroleum — Gaylen #1

A Halliburton-logged Radioactivity Log from the Sooner Trend field in Kingfisher County, OK. Multi-track recording covering from 213 ft down to 8,700 ft. End-to-end pipeline time on this log: ~4 minutes; the header extraction step alone took under 30 seconds. (Phone-photo header runs alone — without depth registration — finish in 20–60 seconds; full depth-registration runs land in the 3–5 minute range for a typical multi-track log.)

Every field above was extracted by the pipeline. The header metadata came from Halliburton's printed strip on the log image; the API number was confirmed against the Oklahoma OCC public well database. (Texas wells confirm against the TRRC RBDMS database via the same flow.) Same workflow you'd get from a phone photo of just the header strip.

Header extraction + confirmed API number

On a phone photo of just the header, this is the entire round trip. Take the picture, the pipeline reads the operator / well / location fields and matches them against our OCC (Oklahoma) and TRRC (Texas) public well databases — 1.95 million wells combined. High-confidence single match? $2, no review, usually in under a minute. Otherwise we show a 3–8 candidate shortlist for you to pick from — $1 if you confirm one, $0.50 if none of them are right and you keep the raw header instead.

{
  "header": {
    "operator": "Crawley Petroleum Corporation",
    "well_name": "Gaylen #1",
    "field": "Sooner Trend",
    "county": "Kingfisher",
    "state": "Oklahoma",
    "section": "33",
    "township": "19N",
    "range": "8W",
    "service_company": "Halliburton",
    "log_type": "Radioactivity Log"
  },
  "api_match": {
    "api_number": "35-073-20892",
    "confidence": "high",
    "match_type": "auto",
    "latitude": 36.0777287,
    "longitude": -98.0564857,
    "occ_record_url": "https://public.occ.ok.gov/..."
  }
}

Five depth-registered tracks, 82 calibration points

For full scans, we produce per-track depth registration: the original TIFF with depth labels burned in, plus an industry-standard IHS DepthRegFile XML calibration for each track. The XMLs are dense — the densest track on this log carries 38 calibration points across a 2,400 ft span, anchoring every depth tick we could read. The $4 price covers the full bundle (including the header + API match); pipeline wall-clock time on a typical log is 3–5 minutes.

What's inside each Track XML

Each calibration point pins a depth value (in feet) to a pixel coordinate on the original TIFF. Denser tracks carry more anchors, which means tighter depth interpolation when you're picking tops between cal points.

<?xml version='1.0' encoding='utf-8'?>
<DepthRegFile version="2.1">
   <DataSource>Well Log Digitizer</DataSource>
   <CalibrationApp>ELog</CalibrationApp>
   <WellInformation>
      <WellIdentifier type="API">35073208920000</WellIdentifier>
      <WellName>GAYLEN 1</WellName>
      <KBElev source="PI">992.00</KBElev>
      <GLElev source="PI">984.00</GLElev>
   </WellInformation>
   <CalibrationPoints>
      <CalibrationPoint>
         <Point><X>203</X><Y>36994</Y><Type>Index</Type></Point>
         <Index>6100.00</Index>
      </CalibrationPoint>
      <CalibrationPoint>
         <Point><X>203</X><Y>37328</Y><Type>Index</Type></Point>
         <Index>6200.00</Index>
      </CalibrationPoint>
      ... 36 more cal points ...
   </CalibrationPoints>
</DepthRegFile>

What this would cost

Tiered ceiling pricing. You pay only the highest tier you reach — depth registration includes the header and the API match for a single $4. The 5 tracks for this log all roll up under that same $4.

Manual landman / log analyst research alone runs $8–$25 per log just for the API matching step. We deliver header + API match for $2 — or the entire stack (header + API + multi-track depth registration) for $4.