Our data

The data under every screen.

118 map layers and about 155 live feeds, pulled from public records and regulatory filings, then cleaned, linked, and kept current.

Energy data is scattered.

Queues, parcels, permits, and grid capacity are all public. They live on thousands of county sites, ISO portals, and federal databases, each with its own format and update cycle.

Teams spend weeks collecting what should take minutes, then decide on a stale spreadsheet.

We built our own data layer so they do not have to.

How we build it
From raw filing to a record you can query.

Ingest

Pull from the source

FERC, EIA, state PUCs, ISO portals, county GIS, and utility filings on a rolling schedule. A new queue filing lands in Basepoint within hours.

Parse

Get structure out of PDFs

Most of it arrives as scanned PDFs and odd spreadsheets. Extraction models pull tables, legal descriptions, and units into records.

Normalize

One schema across ISOs and counties

CAISO, PJM, ERCOT, and SPP each name things differently. Everything maps to one model, so a project in Texas compares to one in Virginia.

Link

Connect the records

A substation links to its lines, queue entries, nearby parcels, zoning, and constraints, joined by geography, entity, and time.

Validate

Check and flag

Queue positions are checked against utility confirmations, parcels against county records. Conflicts are surfaced, not quietly resolved.

Deliver

Serve it everywhere

The same records power screening, grid analysis, models, agents, and the API. Each one carries its source.

Why build it ourselves.

Licensed feeds give everyone the same numbers.

Fresh

Rolling updates. A new queue entry or permit shows up in hours, not at the next vendor refresh.

Linked

Parcels, grid, zoning, and permits connected to each other, the way decisions actually get made.

Traceable

Every figure carries its source, date, and extraction method. Ask where a number came from and get an answer.

Ready for agents

Agents reason over clean, linked records rather than raw scrapes.

What we cover
Across the US, expanding every month.

Interconnection & Grid

ISO/RTO interconnection queues (CAISO, PJM, MISO, ERCOT, SPP, NYISO, ISO-NE)

Substation capacity and loading data

Transmission line ratings and congestion

Generator retirement and addition schedules

Land & Parcels

County parcel boundaries and ownership records

Zoning designations and land use classifications

Land value assessments

Utility territory maps

Topography, pipeline infrastructure, and flood zone data

Permitting & Regulatory

State and local permit applications and approvals

Municipal code and meeting minutes

Environmental impact assessments

FAA obstruction evaluations

Utility commission dockets, FERC filings and rate case proceedings

Resource & Market

Solar irradiance and yield estimates

Wind speed and power density

PPA pricing benchmarks by region and technology

Wholesale electricity price

REC and carbon credit market data

Our approach

Data is the product, not a feature.

Most energy software bolts data on later: a licensed feed here, a scrape there. Gaps and stale numbers follow, and nobody can say where a figure came from.

We started with the data. The pipelines, schemas, and validation came first. The platform sits on top of them.

Schema over shortcuts

One canonical model instead of stitched CSVs.

Provenance by default

Source, timestamp, and method on every record.

Continuous, not periodic

Rolling pipelines, not quarterly batches.

Validate before delivery

Conflicts flagged, not passed through.