OilPriceAPI Research
Measured demand probe

Does a permit-to-production lifecycle join beat another isolated well dataset?

A measured demand probe for normalized permit, spud, completion, first production, status, and plugging milestones keyed by API number. No lifecycle endpoint is currently promised here.

Who this tests: Oilfield software, services forecasting, mineral and royalty operations, energy credit, insurance, research, and local planning teams that track what happened after a permit was filed.

Demand evidence so far

  • PostHog, prior 30 days through 2026-09-02: 24 consented visitors reached the well-permits hub and 23 reached the API-number lookup tool; this is observed product-adjacent traffic, not a conversion claim.
  • Exa surfaced active products selling normalized well headers, production, completions, status, violations, watches, and alerts, while regulator records remain split across forms and archives.
  • Keywords Everywhere returned zero estimated US volume for the exact phrases “oil well completion reports,” “well permit data,” and “permit to first production oil well”; direct workflow evidence must carry this decision.

Smallest useful dataset

  • Canonical API/UWI identity with preserved source identifiers and match confidence.
  • Permit, spud, completion, first positive reported production, status transition, and plugging events with source and observed-at timestamps.
  • Completion fields such as lateral length, perforated interval, water, and proppant only where explicitly reported.
  • Days-to-first-production and other derived intervals calculated from provenance-bearing events, never guessed dates.

Decision contract

Primary metric

Human-reviewed workflow-evidence submissions per 100 consented experiment exposures, followed separately by design-partner sample acceptance and first API activation.

Continue when

  • ✓ At least five qualified workflows name two or more lifecycle milestones they currently reconcile manually.
  • ✓ At least two design partners validate a 100-well sample and one accepts a paid pilot or LOI.
  • ✓ The sample achieves at least 95% audited milestone accuracy and publishes match and missingness rates by state.

Stop or redesign when

  • × Users only want raw bulk files or full decline-curve/petrophysics tooling outside the product wedge.
  • × Cross-source identity and date semantics cannot reach an auditable state-specific quality threshold.

Inspectable sources

FracFocus disclosures

A separate completion/disclosure source whose identifiers and reported fields must be reconciled with regulator records.

Does this replace work you do today?

Tell us which sources you reconcile, how often, and what decision the joined data changes. Prompt views, clicks, and successful submissions are measured separately; only a reviewed workflow submission counts as qualified demand.

Contribute workflow evidence