Can I search by operator name?
Yes. Operator search is one of the core API workflows.
Oil and gas data API
Operator data API
Oil and Gas Operator Data API for Profiles, Permits, and Activity Signals
EnergyNetWatch operator API workflows help teams resolve operator names, retrieve profiles, check activity context, and connect operators to permits, production summaries, wells, facility records, and infrastructure signals where coverage supports the request.
Access model
API keys, endpoint access, usage units, request IDs, rate limits, and hard-stop billing controls.
Pricing
Prepaid API credits start at $50 for 2,500 units, with larger packs or custom plans for heavier use.
Source context
Responses should keep source dates, coverage notes, and caveats visible when they are available.
An example you can inspect before buying
Use the operator data API to prepare an account-research table
Before contacting an operator, identify where its permit activity appears and bring specific well records to the conversation. This Mewbourne example shows the evidence a sales or research team can work from.
Where does Mewbourne have permit activity?
The September 18, 2026 review returned 37 permit-date records: 25 in Eddy and 12 in Lea, with a June 20 lower date bound. Every returned operator label was MEWBOURNE OIL CO.
A separate REST reported-spud screen returned 42 records: 27 in Eddy and 15 in Lea. These are independent populations. Do not add them or treat them as a permit-to-drilling conversion rate.
This is an editorial brief based on retained API responses, not a recording of an AI session or a live count. A rolling-window query run today can return different records.
Three records from the 37-row permit sample
Filed operator: MEWBOURNE OIL CO. State: New Mexico. Missing spud dates do not prove drilling has not started.
RUNWAY 26 30 FEDERAL COM #557H
- API identifier
- 3001558956
- County / permit issued
- Eddy / 2026-09-11
- Reported spud date
- Not reported in reviewed row
PILE DRIVER 24 13 FEDERAL COM #528H
- API identifier
- 3002556872
- County / permit issued
- Lea / 2026-09-09
- Reported spud date
- Not reported in reviewed row
AWESOME BLOSSOM 24 23 FEDERAL COM #554H
- API identifier
- 3001558924
- County / permit issued
- Eddy / 2026-09-08
- Reported spud date
- Not reported in reviewed row
Enter your name, company and email to receive a verification link. No account or payment required. CSV dates use YYYY-MM-DD. Import API identifiers as text. The download contains selected fields from the permit-date population only, with retrieval time and source link.
Build this into your own workflow
Use the authenticated requests below to retrieve records for your software. Keep the two date screens separate, retrieve every result page and preserve source dates. Match operator names before importing an account activity table into your CRM; this is not a native CRM connector.
Prefer an AI assistant? See the MCP prompt and setupWhat does this workflow cost?
Each permit-search request uses 6 API units. The retained 37-row permit response fits one 50-row MCP request: 6 units, equivalent to $0.12 of a $50 / 2,500-unit pack. The two historical REST screens used 12 units ($0.24 equivalent). This is data-request consumption, not a purchase price or a fixed cost for an AI conversation. Additional pages, retries and other tool calls cost more; AI-provider charges are separate.
The minimum credit purchase is $50. No Premium app subscription or separate standard MCP plan is required. After payment is processed and API access is active, create your key and download the local MCP package from API Access.
Example: Mewbourne permit and reported-spud activity
Reviewed September 18, 2026; June 20 lower date bound. Later rolling-window requests will return different records.
Send authenticated requests to https://api.energynetwatch.com with your X-API-Key header. Keep the key in a server-side environment or secret store, never browser code or an AI prompt.
GET /api/public/permits?state=NM&search=MEWBOURNE&days=90&limit=200&page=1GET /api/public/permits?state=NM&search=MEWBOURNE&days=90&limit=200&page=1&spuddedOnly=trueSelected results from the dated review
A readable summary, not the complete JSON response or a live query.
- Filed operator label
- MEWBOURNE OIL CO
- Permit-date screen
- 37 rows: Eddy 25; Lea 12
- Separate reported-spud screen
- 42 rows: Eddy 27; Lea 15
- One returned permit
- RUNWAY 26 30 FEDERAL COM #557H; API 3001558956; Eddy County
- Example issue / spud dates
- September 11, 2026 / no reported-spud date in the reviewed row
Search matches name text, not a verified corporate family. Inspect every returned operator label and pagination.total; retrieve all pages. The two date screens are independent populations, not a permit-conversion rate or a rig count. Blank spud dates do not prove drilling has not started. Keep identifiers as text; api12 contains a ten-digit identifier in this example.
Read the dated Mewbourne review and selection methodRecords
What this API workflow can support
operator profiles
operator search
permits summary
production summary
facility permits
infrastructure leads
Workflows
Common use cases
- Resolve operator names before enrichment or outreach.
- Build operator activity reports.
- Compare operators by permit and production context.
- Feed operator context into dashboards, CRMs, and AI tools.
Caveats
Use source records with context
- Operator names can vary across source systems and historical filings.
- Production and permit records may use subsidiaries or legacy names.
- Returned context depends on coverage, scope, and source cadence.
FAQ
Questions this page answers
Can I connect an operator to permit and production context?
Yes, where source coverage supports the operator and the requested state or endpoint family.
Next step
Start with prepaid API credits
Create an account, verify your email when required, then buy credits and create a key after access activates. Standard MCP uses the same API credits; no Premium subscription is required. AI-provider charges are separate. Ask about custom delivery or redistribution separately.