Permit records in. Evidence-linked events out.
Filter an archived City of Chicago permit sample. The page calls a real read-only endpoint, applies visible field mappings, and returns source-linked event records as JSON.
https://elkwai.com/api/demo/chicago-permits
... Waiting
ydr8-5enu. This bundled sample is dated July 22, 2026 and is historical, not live.
Run the query
Change either filter and run it again. The records, event output, and request path below come from the same API response.
Loading the archived sample...
Source fields
record-level evidence| Permit ID | Type | Issue date | Area | Reported cost |
|---|---|---|---|---|
| Waiting for the endpoint... | ||||
Normalized response
application/jsonLoading...
GET /api/demo/chicago-permitsExact transformation
permit_ | Preserved as the source record identifier and used to create a stable event ID. |
|---|---|
permit_type | Mapped through a fixed lookup table to one of the event types shown in the response. |
issue_date | Normalized to an ISO timestamp at 00:00 UTC; the original date remains in source_record. |
community_area | Retained as a Chicago community-area identifier. No street location is inferred. |
reported_cost | Passed through as reported. The sum is arithmetic only; it is not a verified project budget or sales estimate. |
What is not inferred
This sample has no parcel, owner, applicant, work-description, or future-plan fields. It therefore makes no claim about who owns a property, what materials a project will need, which local supplier may win, or whether a permit is still active. Those results require additional compatible records and independently evidenced entity matches.
Need this run against your own data?
A paid pilot can define the source, fields, matching rules, evidence trail, and acceptance test before private records are connected.