About this demonstration
What it is. inWell is a prototype by InLabs LLC that reads scanned legacy well records (well completion forms, driller's logs, well histories — typed and handwritten), extracts a structured record with per-field confidence and provenance (page and verbatim snippet), runs QC rules, and cross-checks the result against the public KGS master list. This site shows a processed sample of 22 documents. It is a public-data demonstration, not an operational tool; every output requires expert review.
Data sources
- Kansas Geological Survey, The University of Kansas — scanned well records downloaded from public KGS well pages (60 documents, downloaded 2026-11-05). Counties: Ellis, Russell, Barton.
- Kansas Geological Survey — master list of oil and gas wells (CSV), downloaded 2026-11-05. Used only for the field-by-field cross-check.
Method
Pages are rasterized and read by OCR/layout analysis (Azure AI Document Intelligence) and a language model (GPT-4.1, temperature 0, strict JSON schema); every model call is logged. Values are normalized (dates, feet, casing fractions, Sec-Twp-Rge), checked by rules (API format 15-CCC-NNNNN, date order, depth consistency, location ranges, elevation reference order, value present in its own snippet, duplicates) and compared with the KGS master list. Accuracy figures are measured against that list, not claimed.
Measured results
Over all 60 processed documents (126 pages), of which this site shows a sample: 59 were matched to a well in the KGS master list, and 44 carry at least one flag for expert review. Field-by-field agreement with the master list, where both values are present:
| Field | Match | Mismatch | Agreement |
|---|---|---|---|
| api_number | 58 | 0 | 100% |
| completion_date | 45 | 14 | 76% |
| elevation_ft | 41 | 2 | 95% |
| lease_name | 58 | 1 | 98% |
| location | 48 | 1 | 98% |
| operator | 56 | 3 | 95% |
| spud_date | 43 | 6 | 88% |
| total_depth_ft | 55 | 4 | 93% |
| well_number | 58 | 1 | 98% |
Depth within ±10 ft, elevation within ±3 ft on the same reference (KB, DF or ground), names fuzzy, dates exact. A mismatch can be a reading error or a master-list error; either way it needs expert review. Completion dates often differ because a form and the master list can record different events.
What it does not do
- No digital log-curve (LAS) parsing or import, and no integration with or import into any vendor platform.
- No seismic interpretation, drilling analytics or model training.
- No operational use: results are for illustration only, may contain errors and must be reviewed by an expert.
- No non-public data; no accounts; no live model calls from this site (search runs in your browser).
Provenance
All code and design are InLabs' own work. The only data used are public records of the Kansas Geological Survey. No employer, client, partner or vendor documents, code, designs or SDKs and no third-party proprietary material were used. © 2026 InLabs LLC.
Version 0.1.0 · published 2026-11-08.