Agent-consumable real-estate geospatial and entitlement data layer

Agent-consumable real-estate geospatial and entitlement data layer: parcel and ownership boundaries, county and city zoning, building permits, rezoning votes, tax-delinquency payment histories, electrical grid hosting capacity, water/sewer line geometry, and billboard regulation layers — each dataset machine-extracted from the originating county GIS server, utility capacity map, or decades of council meeting minutes, cleaned into queryable tables with per-record provenance back to the source document page, and continuously refreshed. Delivered as SQL and Python access to a cloud sandbox under a per-county subscription, with the notable twist that data requests arrive from AI assistants and the pipeline answers them, including through CAPTCHA-gated county sources.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Ploti and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Application SoftwareReal Estate Management & Development
Instruments: equitiesfixed_income

Dataset card

Type: not stated
Format: Multimodal
Volume: Printed per-dataset counts, which is the volume answer directly: 2.76M distribution circuit segments with hosting capacity plus utility territories and substations; 324 rezoning cases rebuilt from 1,823 meeting documents with page-level vote citations; 57 county and city zoning layers across 15 counties; 1,421 delinquent tax accounts with full payment history refreshed weekly; 16,486 regulated billboard structures checked against scenic highways and draft-ordinance exclusion zones; 10,744 potable water line segments. Coverage is organized as coverage cells — Travis County alone shows 42 coverage cells and 18 maintained datasets.
Users: N/A — developer and API subscription product for real-estate teams, not a registered-user platform; billing is per covered county rather than per seat and no account count is published. A team of ~2 implies an early customer roster measured in tens of accounts, not thousands.
History: 6 years
Update frequency: not stated
Growth: Active — the coverage pipeline is mid-expansion with named counties in explicit states (Travis, Hays and Williamson Active; Comal and Bexar Queued), datasets refresh weekly, and the request queue shows jobs progressing within the hour. Recently founded with a 2-person team, so pre-scale but visibly building.
Launched: ~2025 (the company record for this domain is newly created with no funding history, and the product is architected around assistant-initiated data requests — a design that only exists after 2024 adoption of AI-agent tool use).
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site