Coverage

Every recorded document.
In our database.

We ingest county clerk records directly, patent to present, and store them in our own PostgreSQL database. No aggregator middleman.

Colorado coverage

We focus on Colorado's DJ Basin and Wattenberg Field, where drilling activity is highest and mineral title chains are most complex. Here's what patent-to-present coverage looks like in practice.

DJ

DJ Basin core

Niobrara & Codell formations

Patent-to-present. The complete grantor-grantee index from original US land patents through the most recent recordings. The most active oil and gas region in Colorado, and the core of the DJ Basin.

Patent-to-presentFull grantor-grantee indexDJ Basin coreOwn database
WF

Wattenberg Field

DJ Basin's western extent

Full clerk index. Covers the DJ Basin's western extent. Denver metro surface pressure means severances are common here, making mineral title research especially relevant.

Full clerk indexDJ Basin overlapDenver metro fringeOwn database

What “in our database” means

Most mineral data platforms license data from third-party aggregators. That constrains their data model, update schedule, and coverage. We took a different approach.

Direct ingestion

We pull records from county clerk systems ourselves and parse every field: grantor, grantee, document type, recording date, book/page, legal description.

Our own PostgreSQL

Records live in our database, not behind a third-party API. That's what makes graph traversals, BFS chain searches, and canonical party resolution possible.

Controlled updates

We decide when to re-ingest. When a county posts new recordings, we pull them on our schedule.

Expanding beyond Colorado

The DJ Basin is the starting point. We're adding Colorado counties and expanding into new regions across the country, wherever mineral activity and customer demand justify the ingestion work.

Each new county goes through the same process: full clerk index ingestion, field-level parsing, normalization, and integration into our chain-building and lead-scoring pipelines. We don't do partial coverage. When we add a county, we add all of it.

If there's a county you need, let us know. Customer requests directly influence which counties we prioritize. Email contact@mineralscout.ai with the county name and we'll let you know where it stands in our pipeline.

Frequently asked questions

Our database includes every recorded document affecting mineral title, from the original US land patent through the most recent recording in the county clerk's index. The complete chain, not a partial snapshot.

No. We ingest county clerk records directly into our own PostgreSQL database. That gives us full control over data quality and update frequency, and lets us build features like BFS chain traversal that require the raw grantor-grantee graph.

We re-ingest county records on a regular cadence. The exact frequency depends on the county, but our goal is to stay current with the clerk's index.

We're expanding across Colorado and into new regions around the country. We don't pre-announce markets or timelines, but customer demand directly influences what we add next. Reach out if there's an area you need.

Yes. Email contact@mineralscout.ai with the county and state you need. We use customer requests to prioritize which counties we onboard next.

See it in action

Run a title search on any parcel in Colorado's DJ Basin. Patent to present, in minutes.