Datasets to acquire or license, by domain and coverage

What it is for

Analysts and model builders often know exactly what data they need (permits by parcel, freight rates by lane, store-level foot traffic) but not who sells it, under what licence, or whether it exists at the coverage required. The licence matters as much as the fields: internal analysis, a commercial product and model training are priced and permitted differently. This records fields, coverage, cadence and intended use so that unmet data demand, and what buyers would pay, can be studied.

Data scientists and analysts, quantitative researchers, product teams building on third-party data, AI developers seeking licensed training data, and procurement staff buying data.

What happens to a request

Your data requirement is recorded as described. No data is supplied, sold or sublicensed, no vendor is contacted and no terms are negotiated. If you leave a contact and a source of that data can be identified, a reply may come; it is not promised. Contact details are stored apart from the requirement and deleted after 180 days.

What you get

A receipt with the request's identifier, the fields we could not match (a vendor, a sample or licence terms are never supplied here), and a plain statement of what happens next.

Scope and limits

Any coverage; the geography of the data is recorded as stated.

• No data is supplied or licensed; this records the requirement.
• Datasets of personal information about individuals are recorded only as a stated need; nothing is collected or traded.
• Licence terms are recorded as your requirement; nothing here interprets a licence.

What you can specify

• subject domain and the fields required
• geographic coverage and history
• refresh cadence and delivery format
• intended use: internal, commercial product, model training or redistribution

Next step

POST the data requirement to /dataset-licensing/requests (or /requests), use the form on this page, or call the submit_request MCP tool with proposition "dataset-licensing".

Or send JSON to POST /dataset-licensing/requests (schema: /dataset-licensing/schema.json). Example:

{
  "action": "license",
  "need": "Building permits issued in the 50 largest US metros since 2018, with permit type, valuation, contractor name and work address, refreshed weekly and licensed for use in a commercial software product.",
  "specifications": {
    "domain": "building permits",
    "fields": [
      "permit_type",
      "issue_date",
      "valuation",
      "contractor_name",
      "work_address"
    ],
    "coverage": "50 largest US metropolitan areas",
    "history_start": "2018-01-01",
    "refresh": "WEEKLY",
    "intended_use": "COMMERCIAL_PRODUCT",
    "delivery_format": "PARQUET"
  },
  "timing": {
    "earliest": "2027-01-01",
    "recurrence": "weekly"
  },
  "geography": {
    "country": "US"
  },
  "budget": {
    "amount": 60000,
    "currency": "USD",
    "per": "year"
  }
}