Eddy County New Mexico Drilling Permits And Reported Spuds (2026)

Eddy County had 640 New Mexico drilling permit records in the 90-day window ending August 28, 2026. The same review found 1,733 trailing-12-month permit records, 25 source-filed operator labels, and 151 reported-spud events in the separate source window.

Among the 7 New Mexico counties with current permit activity in this reviewed cut, Eddy ranks 1 by 90-day permit count. Use that rank as a filing-volume comparison only. It does not measure acreage, production, rig count, capital spending, or commercial awards.

Current Eddy County permit snapshot

The permit source runs through August 28, 2026. The reported-spud source runs through August 27, 2026. Those clocks are shown separately because permits and reported spuds are different record stages.

Leading source-filed operator labels

XTO PERMIAN OPERATING LLC. leads this public preview with 88 permits, or 13.8% of the county total. The 5 displayed labels account for 356 permits (55.6%). Operator names are preserved as filed; similarly named entities are not consolidated without separate identity evidence.

Permit and reported-spud timing

151 deduplicated reported-spud events appear in the separate window through August 27, 2026.

A permit is an authorization or filing-stage record. A reported spud is a later drilling-stage record. The two totals should not be added together or divided into a conversion rate because their reporting cadence, coverage, and population differ.

How Eddy County records are assigned

New Mexico county assignment uses the source county code and retains the source county name. Permit and reported-spud dates come from the New Mexico source record. Operator names remain source-filed labels unless separate evidence supports consolidation.

This method produces a county lookup page that can be refreshed from the same state snapshot. It does not publish individual permit numbers, API identifiers, well names, coordinates, or the complete operator table. Those record-level fields remain in the app and API workflow.

Browse the New Mexico active county permit directory to compare current county totals, or use the Texas and New Mexico county permit hub to switch states.

Frequently Asked Questions

How many recent drilling permits are in Eddy County?

Eddy County has 640 permit records in the reviewed 90-day window ending August 28, 2026 and 1,733 permit records in the trailing 12 months.

Which operator has the most recent Eddy County permits?

XTO PERMIAN OPERATING LLC. leads the current source-filed preview with 88 permits. This is a filing-label ranking, not a corporate-family, acreage, production, or spending ranking.

Does a drilling permit mean the well was drilled?

No. A permit is a filing-stage record. Reported-spud, completion, and production records are later stages and should be checked separately.

Where can I get the individual Eddy County permit records?

The EnergyNetWatch app and API workflow provide the record-level identifiers, dates, operator labels, map context, filters, exports, and monitoring options that are intentionally omitted from this public county summary.

Researching Eddy County beyond the totals

In the September 1 snapshot above, XTO PERMIAN OPERATING LLC. has 88 recent permits and XTO ENERGY, INC has 78. Keep these as two filing labels in the first pass; a corporate-family view needs a documented mapping. The five displayed labels cover 356 of 640 records, leaving 284 outside the preview. A prospecting list built only from those five names would omit a substantial part of the reviewed permit activity.

For a land or service-territory review, start with the operator and permit date, then check the individual permit identifier and well identity. In New Mexico API identifiers, 30-015 identifies the state and county portion; it is not a complete well identifier. Preserve leading zeroes and treat identifiers as text. A well API number and an application programming interface are different uses of the term API.

The New Mexico snapshot above uses source county codes and retains source county names. The REST example below searches the source county name within New Mexico. Inspect returned county names and identifiers together; a county match does not establish a precise surface or bottom-hole location. Keep the snapshot window separate from the live rolling window.

Eddy County permits through the data API

Use this server-side example with your own API key. It requests the first five permit rows in a rolling 90-day window, not every record and not the fixed reporting window above. Store the key in a secure environment variable; never put it in browser code or a public notebook.

curl --fail-with-body --get \
  'https://api.energynetwatch.com/api/public/permits' \
  --header "X-API-Key: $ENW_API_KEY" \
  --data-urlencode 'state=NM' \
  --data-urlencode 'county=Eddy' \
  --data-urlencode 'days=90' \
  --data-urlencode 'page=1' \
  --data-urlencode 'limit=5'

The response contains data.permits, data.pagination, data.countWindow and source freshness metadata. Inspect the returned county values, dates and identifiers before using the records. A blank completion or spud field is not proof that the event never occurred.

This request was checked on September 11, 2026 and returned five Eddy rows. It is a live-query example, not a refresh of the September 1 public snapshot. The lookback is relative to the request date; this endpoint does not expose fixed start/end date parameters. Later calls can return different records.

To build a complete filtered operator table, follow data.pagination.nextPage while hasMore is true, within your request budget. Aggregate only after collecting the intended pages. Label a five-row result as a sample rather than ranking operators across the county. Record the request date and filters, and retain permit identifiers to check repeated records.

The published cost for this endpoint is six API units per request. At the $50 / 10,000-unit starter rate, that is $0.03 per request; each additional page is another request. Other tools have their own costs. Review API pricing and the developer documentation before a larger pull.

Using an AI assistant with the returned county table

After exporting the intended rows, ask your assistant:

Using only this Eddy County permit export, group rows by the exact source-filed operator name. Show record count and earliest/latest permit issue date for each group. State the export filters and whether pagination was completed. Flag missing county values, dates or identifiers. Do not infer drilling, completion, production or purchasing activity from a permit.

This is an export-analysis prompt, not a claim that the MCP permit-search tool accepts a county filter. The checked MCP server version 0.1.10 does not expose that filter on its permit-search tool. Do not pass a county name as an operator search or silently substitute a statewide sample. See MCP setup and supported workflows for connection instructions; confirm the installed tool schema before asking it to reproduce a county search.

For a returned New Mexico well identifier, check completion, status and production separately. This permit example does not establish that those follow-up fields or tools are available for every well. Do not apply the Texas RRC completion or lease-production workflow to a New Mexico API number. Review New Mexico coverage and the state data explorer for the available datasets and their individual reporting dates.

Request a Eddy County research table

Need a reviewed table rather than code? Request a Eddy County research scope. Include the date window, operators and the question you need answered. Scope, available fields and delivery are agreed before purchase; this is not an advertised recurring subscription. For repeatable programmatic research, compare prepaid API credits.