Inspect the format before paying for the feed
This sample file is made up. Its 100 rows use invented addresses, permit IDs and cities, in the same 24-column format as real CivicDataForge output, so you can test your schema, joins and parsing. Real output comes from each city’s published registry. See the 32 supported jurisdictions.
SHA-256:b602572f3b0511615f91c014af0474fcaff031f6a438f60ae64b121d76c7e0db
This hash is for the made-up file published on 2026-10-21. A machine-readable checksum is also available at the checksum URL.
What the sample shows
Use it to inspect the 24-column schema: permit and unit identifiers, normalized and source status, address precision, coordinate fields, jurisdiction fields, dates, source URLs and retrieval timestamps. The values are invented. Coordinates are set to 0, and the source URL points to the sample note.
What it does not include
The sample holds no real records, so it says nothing about any real property or city. It has no owner/operator names, raw source objects, or phone or email columns. In the paid feed, government publishers can delay, correct or omit records; check important facts with the issuing authority.
Choose the paid path
On-demand or API: run the current Actor at $3.00 per 1,000 delivered records on Apify's Free tier, with current subscription-tier prices of $2.80 Starter, $2.60 Scale, and $2.40 Business or higher. Recurring delivery: use complete-scope scheduled monitoring or request the AWS monthly dataset after marketplace approval. Custom requirement: request a jurisdiction, cadence, history, or private delivery scope.
Use the STR Registry on Apify Request a private scope