How access works
Request, scope, delivery.
There is no sign-up and no public key. A person reads your request, writes a scope, and sets up the delivery once you agree to it.
The four steps
- You send the request. Datasets, states or areas, delivery and what the data is for.
- We reply by email. Questions, plus a written scope: datasets, fields, geography, refresh schedule, delivery format, use terms and fee. Some counties are held back; the scope says so if your area includes one.
- You agree to the scope. Nothing is set up and nothing is billed before that.
- We set up your delivery. An API key, a file drop, or an agent endpoint, scoped to what was agreed, with a first sample for you to check.
What the written scope covers
- Datasets and fields
- States, and counties for the county index
- Refresh schedule: one time, monthly, weekly or daily
- Delivery: API, bulk files or agent endpoint, and where files land
- Use terms: internal use, inside your product, or as input to your agent; whether model training on the rows or redistribution is allowed is written into the scope
- Fee and how usage is counted
Three ways to receive it
API
JSON over HTTPS with a bearer key. Filter by state, county, API number or update date; page with a cursor. Fits applications that look up a well or permit at a time.
Available on request.
Bulk files
Parquet, CSV or JSONL per state with a manifest of row counts and checksums. Full drop first, then changed rows on your schedule. Fits a warehouse load.
Available on request.
Agent endpoint
An MCP server your agent connects to with its own key. A coverage tool tells the agent what we hold before it asks for rows. Use is metered per request.
Available on request.
Who supplies it
Our Landmen LLC, an independent land company in Cheyenne, Wyoming. We harvest the upstream feeds into our own lakehouse on each dataset's own schedule (nightly for permits and production headers, monthly for wells; the last unit harvest ran 2026-04-25), keep the silver views and a daily census of them, and serve deliveries from them. Jerry Ward runs the lakehouse and answers access requests.
Wells, permits, units and production come from Enverus feeds of state regulatory filings. The county index comes from the Enverus enhanced county clerk index. Each row carries its view and source update date.
Not here
- A private system built on your own records: landman.ai.
- Title search on a tract: title.wiki. A full land packet: landman.services.
- Owner names and contact data, and our own brokerage records: not offered.
- Self-serve keys or card checkout: not offered today.
Request access
Name the datasets, the states and what your system or agent will do with the rows. We reply by email.
Email gerald@ourlandmen.com or call (307) 263-8515 if you prefer.