4 live streams
Building permits data
A permit is an event, not a reading, so these streams are read as tallies: how many were issued, of what kind, by whom and where. The cities publish them on Socrata, CKAN and ArcGIS portals; Dryos normalises the three into one shape and labels every permit with a subject and an action of its own.
What is collected
Every Building permits stream Dryos holds, grouped the way the catalogue groups them.
- Streams
- 4 live
- Fastest cadence
- daily
- Entities
- 203 across every stream
- Access
- Public REST API and MCP server, no key
Permits
- Austin construction permits
Every building, electrical, mechanical, plumbing and driveway permit the City of Austin issues, one row per permit: the work described, the declared value, the contracting company and the place.
daily · 1d rows50 entitiesaustin-permits - San Antonio permits
Every building and trade permit the City of San Antonio issues, one row per permit, with its own re-roof permit type — the number a roofer, an adjuster or a carrier watches the week after a hailstorm.
daily · 1d rows71 entitiessanantonio-permits - Fort Worth permits
Every building and trade permit filed with the City of Fort Worth, one row per permit, by the day it was filed: the work described, the declared value, its status as it moves from plan review to issued, and the place.
daily · 1d rows44 entitiesfortworth-permits - Collin County permits
Building permits from every city in Collin County, as the Collin Central Appraisal District records them: the city, the work, the builder and the ZIP.
daily · 1d rows38 entitiescollin-permits
Worth knowing first
- The people are not stored. Contractor and applicant names, phones and addresses are never selected; the contractor company is kept, because which firms pull permits where is the point of the feed.
- Subject and action are Dryos's own versioned labels, stored beside the city's rows rather than in them — the city's data stays exactly what the city published.
- Most of unincorporated Texas needs no permit at all, so rural and co-op installs are invisible to every permit feed.
Read it
Public, read-only, no key and no sign-up. Every stream answers the same way.
Every stream in the catalogue
curl "https://api.dryos.ai/v1/datasets"Or point an AI agent at all of it
claude mcp add --transport http dryos https://api.dryos.ai/mcpFull parameters are on the API reference; every client's setup is on the MCP server page.