bricks self-service data platform · Twin Cities

Brick & Mortar · datasets

Every dataset we publish.

Public records a city already emits, joined into one warehouse and handed back as a file. 19 datasets, 439,676 rows. Free, no account, no rate limit — anyone can buy reviews and anyone can scrape a county, but nobody else has them joined for one metro.

19 datasets
DatasetRows ColumnsCoverage
What shares a lot line with a property 115,652 28 all seven metro counties
Who is listed at every commercial address 88,433 20 all seven metro counties
Walk a corridor, address by address 44,151 57 all seven metro counties
What sold, and for how much per square foot 34,302 24 all seven metro counties
Healthcare providers with a federal NPI, statewide 32,257 18 the Twin Cities metro
Which properties FEMA puts in the floodplain 28,354 14 all seven metro counties
Who the landlord is, on a licensed rental property 23,303 35 Hennepin County
What the 911 calls around here are about 22,123 20 Hennepin County
How a neighbourhood differs from the typical one 10,797 12 Hennepin and Ramsey counties
Who owns it, and what else do they hold 9,251 13 Anoka, Dakota, Hennepin, Ramsey and Washington counties
What a bank actually lent, loan by loan 8,822 32 all seven metro counties
Cleanup and storage-tank files, by address 7,149 18 Hennepin and Ramsey counties
Who does the work here, and how to write to them 6,588 14 Hennepin and Ramsey counties
Who holds a licence to trade here 6,553 16 Anoka, Dakota, Hennepin and Ramsey counties
Subsidised homes, and when the subsidy runs out 1,500 23 all seven metro counties
Business counts by trade, five vintages 318 13 all seven metro counties
What the statewide parcel layer can answer, county by county 87 40 the Twin Cities metro
Who lives here, and what they pay 24 6 Hennepin and Ramsey counties
Building stock by era 12 7 Hennepin and Ramsey counties

Filter it to you first

The platform asks who you are and hands you the cut that fits — the same files, entered at the question you actually have.

What these files cannot tell you

Every layer states its own limits, with its own row counts and sources, on the system card. Coverage is not uniform: it runs from one county to all seven, and each page above says which.

What you may do with all of it

Everything here is CC BY 4.0. Use it commercially, build a product on it, sell what you build — just credit Brick & Mortar and link back. The licence, per source — and the two datasets we withhold, with the reason.

Point an AI at the whole warehouse

Every file carries its source, its capture date and the layer's own warnings above the header row, so a model reading one gets the caveats with the numbers. llms.txt describes the catalogue the same way, and /api/export with no arguments returns it as JSON.