# Oil & Gas Drilling Permits Tracker (Multi-State) (`jadey_orbit/drilling-permits-tracker`) Actor

A daily feed of new oil & gas drilling permits across US states — operator, API number, county, formation, and location — straight from public state-regulator data. Pay per permit.

- **URL**: https://apify.com/jadey\_orbit/drilling-permits-tracker.md
- **Developed by:** [Matt Sparks](https://apify.com/jadey_orbit) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 permit record delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Oil & Gas Drilling Permits Tracker (Multi-State)

A **daily feed of new oil & gas drilling permits** across US states — operator, API number, well name, county, target formation, and location — pulled directly from **public state-regulator data**. One normalized feed instead of a different website for every state. Pay per permit.

### Coverage

| State | Basin | Source | Freshness | Permit date |
|---|---|---|---|---|
| **New Mexico** | Permian | OCD/EMNRD | to yesterday | ✅ |
| **Pennsylvania** | Marcellus | DEP | to yesterday | ✅ |
| **North Dakota** | Bakken | NDIC/DMR | live (hourly) | newest-first by NDIC file # |
| Oklahoma | Anadarko | OCC | *public feed currently lags ~2 months* | ✅ |

*Roadmap: Texas (RRC) and Colorado (ECMC) are in development. Request states via the Issues tab.*

### What you get per permit

`state`, `operator`, `permitNumber`, `apiNumber`, `wellName`, `county`, `permitType`, `permitDate`, `status`, `formation`, `latitude`, `longitude`, `sourceUrl`.

```json
{
    "state": "NM",
    "operator": "MARATHON OIL PERMIAN LLC",
    "apiNumber": "30-015-58507",
    "wellName": "ATREIDES FEDERAL COM #701H",
    "county": "Eddy",
    "permitType": "H",
    "permitDate": "2026-07-16",
    "status": "New",
    "formation": "PURPLE SAGE, WOLFCAMP (GAS)",
    "latitude": 32.234, "longitude": -104.234,
    "sourceUrl": "https://ocdimage.emnrd.nm.gov/"
}
```

### Why this actor

- **Multi-state in one call** — the only comparable actors are single-state; this normalizes several states into one schema.
- **Official regulator data** — stable government ArcGIS services, not fragile website scraping.
- **Filter built in** — by state, recency (days back), operator, and county.
- **Pay per permit** — no subscription. Compare: DrillingEdge starts at $29.99 and Enverus DrillingInfo is enterprise-priced for the same category of data.

### Pricing

| Event | Price | When charged |
|---|---|---|
| Actor start | $0.02 | Once per run |
| Permit record | $0.01 | Per permit delivered |

**Example**: 500 recent permits across NM + PA + ND ≈ $0.02 + $5.00 = **$5.02**.

### Input

```json
{
    "states": ["NM", "PA", "ND"],
    "daysBack": 30,
    "operators": ["Marathon", "Devon"],
    "counties": ["Eddy", "Lea"],
    "maxPermits": 500
}
```

- **states** — which states to pull (see coverage table)
- **daysBack** — include permits from the last N days (states with a permit-date field)
- **operators / counties** — optional case-insensitive filters
- **maxPermits** — cap on records returned

### Use cases

- **Oilfield services & suppliers** — reach operators the moment a new permit drops
- **Landmen & mineral owners** — track permitting activity in your counties
- **Investors & analysts** — monitor operator drilling cadence and basin activity
- **Journalists & researchers** — the public permitting record, structured
- **AI agents** — an MCP-callable "what got permitted in the Permian this week?" tool ([Apify MCP server](https://docs.apify.com/platform/integrations/mcp))

### Notes

- Data comes only from public state-regulator systems. No login, no private data.
- **North Dakota's public feed carries no permit-approval date**, so ND returns the most recent permitted locations by NDIC file number (`daysBack` doesn't apply to ND).
- **Oklahoma's public hosted layer currently lags ~2 months** (a regulator-side refresh issue) — it's included but off by default; widen `daysBack` to see its data.
- Formation is present for NM and OK; PA/ND populate it only once drilling begins (often null at permit time).
- Want Texas, Colorado, more states, or webhook alerts on new permits matching your area of interest? Open an issue in the **Issues** tab.

# Actor input Schema

## `states` (type: `array`):

Which states to pull drilling permits from. Leave empty for all supported states.

## `daysBack` (type: `integer`):

Include permits issued/filed within this many days. Defaults to 30.

## `operators` (type: `array`):

Only keep permits whose operator name contains one of these (case-insensitive). Empty = all operators.

## `counties` (type: `array`):

Only keep permits in these counties (case-insensitive). Empty = all counties.

## `maxPermits` (type: `integer`):

Maximum number of permit records to return.

## `proxyConfiguration` (type: `object`):

Proxy settings. State government sites work fine without a proxy.

## Actor input object example

```json
{
  "states": [
    "NM",
    "PA",
    "ND"
  ],
  "daysBack": 30,
  "operators": [],
  "counties": [],
  "maxPermits": 500,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "operators": [],
    "counties": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("jadey_orbit/drilling-permits-tracker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "operators": [],
    "counties": [],
}

# Run the Actor and wait for it to finish
run = client.actor("jadey_orbit/drilling-permits-tracker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "operators": [],
  "counties": []
}' |
apify call jadey_orbit/drilling-permits-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=jadey_orbit/drilling-permits-tracker",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/pB6aTN6Wgn4jhzQkH/builds/T1CSg6w6oYFDfMjxt/openapi.json