Property · 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. Fort Worth names no contractor; an installer is kept only where the project title is a registered business.
fortworth-permitsdaily · 1d rows44 entitiesWhat is in it
- Updates
- daily · 1d rows
- Entities
- 44 entities — 76179, 76052, 76036…
- Source timezone
- US Central — every timestamp Dryos serves is UTC
- Coverage
- 16 April 2026 to now
- Rows held
- 29,708
- Primary key
- permit_id
- On the map
- 44 of 44 placed
What it measures
Every value, its unit, and what the source means by it.
- Permits filedpermits
How many permit applications were filed in the day or week — the rollup's own row count, after any filter. Filter on status for issued work.
samples - Declared value$
Total job value declared on the applications in the day or week. Trade permits carry none; about one permit in four declares a value.
valuation_usd
Columns
Exactly what a request answers with, read from the API rather than written here.
| Column | Type | Description |
|---|---|---|
| interval_start_utcrequired | timestamp | The day the permit application was filed: midnight in Fort Worth, as UTC. Fort Worth publishes no issue date; `status` says how far a permit has got.e.g. 2026-09-12T05:00:00Z |
| permit_idrequired | string | The city's own permit number; its prefix is the trade (PB building, PE electrical, PM mechanical, PP plumbing).e.g. PB26-11652 |
| permit_typerequired | string | The city's permit type as a token, trailing 'Permit' dropped: PLUMBING, ELECTRICAL, MECHANICAL, RESIDENTIAL_BUILDING, PLUMBING_BACKFLOW, COMMERCIAL_BUILDING and a few more.e.g. RESIDENTIAL_BUILDING |
| permit_class | string | RESIDENTIAL or COMMERCIAL, read off the permit type where the type says.e.g. RESIDENTIAL |
| work_class | string | The city's subtype: New, Remodel, Addition for building work; Standalone or Umbrella for a trade permit on its own or under a building permit.e.g. Remodel |
| category | string | The city's permit category where it sets one: Construction or ReRoof.e.g. ReRoof |
| use_type | string | What the permitted structure is used as, in the city's words: Single Family Residence, Office, Storage Shed, Pool or Spa and so on.e.g. Single Family Residence |
| description | string | The work described on the permit, verbatim. This is where a re-roof, a solar array or a foundation repair is named.e.g. Express: Removal of existing roof and chimney section |
| valuation_usd | number | Job value declared on the application, US dollars.e.g. 7000 |
| contractor | string | The company named in the permit's project title, where the title is a registered business (it carries LLC, Inc, Corp and the like). Fort Worth publishes no contractor column, and the title is as often the homeowner, who is not stored.e.g. SUNRUN INSTALLATION SERVICES INC |
| statusrequired | string | The permit's status at the source: Plan Review, Issued, Finaled, Void and so on. Restated on every run, so it moves after filing.e.g. Issued |
| zip | string | Five-digit ZIP of the permitted address. The entity a page counts by.e.g. 78704 |
| lat | number | Latitude of the permitted address, degrees north, as geocoded by the city.e.g. 30.243 |
| lon | number | Longitude of the permitted address, degrees east of Greenwich.e.g. -97.751 |
| source_published_at_utc | timestamp | When the city last refreshed the layer. Always null: the map service carries no refresh time. |
| collected_at_utcrequired | timestamp | When Dryos collected this row, UTC. Stamped by the platform.e.g. 2026-09-07T14:00:10Z |
Read it
Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.
The newest rows
curl "https://api.dryos.ai/v1/datasets/fortworth-permits/query?node=76179&limit=12"The catalogue entry — every column, its type and the source
curl "https://api.dryos.ai/v1/datasets/fortworth-permits"Full parameters — bucketing, aggregation, filters and search — are on the API reference.
Ask an agent
The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.
claude mcp add --transport http dryos https://api.dryos.ai/mcpThen ask:
How many permits did Fort Worth issue each week this quarter, by trade?
Setup for every client is on the MCP server page.
How this stream is checked
- Pulled straight from City of Fort Worth Development Services — no reseller in between — and compared against that file before it is served.
- Null means the source did not report it — never zero.
- A reading lands daily; the interval timestamp is the start of the interval, in UTC.
- 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.
Related streams
- 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 - 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