Licensed data

Planned products, priced by quote. Where we have no coverage, the product says so. Open datasets, free under an open license, are listed separately. How customer access works.

Paid products are free to every account through December 31, 2026 (midnight US Eastern). From January 1, 2027, paid plans apply only to accounts that choose one, and the free API key and free tier continue. Storm reports for storms already in the published tables, and the extras listed for those tables, are free with a free account. Licensed products are by quote. Create a free account · Plans from 2027

Products, coverage and delivery

Licensed data products. Select a column heading to sort.
Product Price Status What you get Coverage Updates Delivery
Data-center intelligence By quote In preparation U.S. data-center sites joined to hourly grid demand, generating capacity and planned power plants for each balancing authority (Licensed products are by quote.) United States Next release API, MCP server and files
Disaster catalog By quote In preparation U.S. disaster events by county, joined to the storm catalog and to reported utility outages. Open dataset downloads stay free forever. (Licensed products are by quote.) United States Next release API, MCP server and files
Federal review milestone feed By quote Planned Milestones, notices and schedule slippage for federal environmental reviews, filtered by region, state, agency or sector (Later product. Quotes on request.) All 50 states and the territories Planned API, GeoPackage and CSV
Portfolio monitoring By quote Planned Your saved boundaries checked against every source update, with a before-and-after for each change (After site screening) Same as site screening Planned API
Site screening evidence By quote Planned Every federal record that touches a boundary you supply: wetlands, floodplains, streams, habitat, contaminated sites, air-quality areas, historic places and prior federal reviews, each with its source, version, date and distance (Later product. Quotes on request.) National for these federal records; state and local layers added state by state Planned PDF evidence bundle, GeoPackage, file geodatabase, shapefile, API
Water observation histories By quote Planned One reconciled history per lake or reservoir you name: level, surface area, storage and flow, with a quality flag on every value (Planned.) Western U.S. first Planned CSV, Parquet, GeoPackage, API

Status and coverage are stated as they are today. Each product page has a sample, delivery formats and how to get started.

What a delivery looks like

  1. First page of a site screening evidence bundle: a boundary on aerial imagery with its mapped records and seven findings, each naming its source.

    Planned

    Site screening evidence

    For a boundary you supply, the supported federal environmental datasets that touch it: wetlands, floodplains, streams, habitat, contaminated sites, air-quality areas, historic places, and prior federal reviews, each with its source, version, and date.

    For Environmental consultants, engineering firms, developers, and GIS teams who screen many sites and want the evidence inside their own tools.

    Sample: a boundary we drew across the Ashley River, South Carolina, checked against seven federal layers on 26 September 2026.

    Read this product

  2. First page of a national milestone feed issue: a region table, filters, the month's notable changes, and a map of every tracked project.

    Planned

    Federal review milestone feed

    Milestones, notices, and schedule slippage for federal environmental reviews in the public systems we track, filtered by region, state, agency, or sector.

    For Developers, lenders, law firms, and public agencies whose schedules depend on a federal review.

    Sample: the national issue of 26 September 2026, every project on the Federal Permitting Dashboard.

    Read this product

  3. Map of 131 large solar facilities across four western states with counts and capacity by state.

    Planned

    Portfolio monitoring

    Your saved boundaries checked against every source update, with a before-and-after for each change and the source version on both sides.

    For Owners and operators of many sites: utilities, energy portfolios, infrastructure funds, and the firms that serve them.

    Illustration: a real portfolio, every solar facility of 100 MW or more in four states, from the USGS database.

    Read this product

  4. Line chart of Great Salt Lake daily water-surface elevation for both arms, 2019 to 2026.

    Planned

    Water observation histories

    One consistent history per eligible lake or reservoir: surface extent, plus level, storage and flow where a gauge publishes them, with units reconciled and a quality flag on every value.

    For Water managers, irrigation districts, utilities, and researchers who track many water bodies across several agencies' records.

    Illustration: Great Salt Lake elevation from USGS gauges, the public record the open dataset is checked against.

    Read this product

Sign in to the customer portal. Sign-in, keys, and delivery run there, separately from this website. Licensed products are by arrangement. Nothing is sold through a checkout yet.

What every product includes

  1. A A small block of metadata attached to every response: which source, which version of it, when it took effect, and when we first saw it. on every response

    Source, source version, effective date, and first-seen date on each value, so two people looking at the same result a month apart can tell whether the world changed or the record did.

  2. Coverage stated, gaps flagged

    A result distinguishes "nothing intersects" from "no coverage here" from "not evaluated." A missing layer is reported as missing.

  3. Source records for each finding

    We report what a public record says and where it lives. We do not make regulatory determinations, legal judgments, or predictions about outcomes.

  4. Versioned, with a changelog

    Schema and method carry a version. Changes are listed, and earlier versions remain readable for the life of your agreement.

  5. Source attribution

    Inputs are public government records and open satellite programs unless your agreement says otherwise. Any attribution a source requires travels with the data.

  6. A sample before a contract

    Every product starts with a real output on a boundary, agency, or site list you pick, so you judge the data before you pay for it.

How licensing works

License
A written data license per product and customer. It states permitted use (internal, client deliverables, redistribution, derived products), the number of users or sites, the term, and what happens to the data when the term ends. These products are not covered by the open license on our free datasets.
Pricing
Priced by coverage, update frequency, permitted use, and delivery method. Site screening, the milestone feed, and portfolio monitoring start with a quote. The weekly lake watch is planned. Paid plans start January 1, 2027, on Plans and prices. The customer app is open. See how it fits with services.
Delivery
Through a separate customer portal with its own sign-in, keys, and usage records. Keys are scoped to your organization and product and can be revoked or rotated at any time.
Sources and rights
We keep a register of every input: its license, its access terms, and what we may deliver downstream. A source that does not permit redistribution is used only to compute values we are allowed to deliver, and the register says so.
Your data
Boundaries, site lists, and results you send us stay yours, are used only to deliver your product, and are deleted at the end of the term on request.
Ask
To get started or request a quote, tell us the product, the area, and how you will use the data. To sign in, use the customer portal.

Getting started

Tell us the product and the scope. We send terms, a first output with its data card, and a quote. The customer app is open, with self-serve sign-up and free keys. Sign in here.

Request a quote Plans and prices API and MCP