Integration
The Interface Is Optional. The Intelligence Feed Is the Product.
Citylitics can review the intelligence here or consume the same reviewed records directly as structured JSON through a client specific pull API. Research scale counts describe source inventory and candidate detection. Only approved reviewed records are counted as reviewed findings. Source-checked previews are labeled separately and remain pending human review. This page illustrates a delivery format and is not a live production integration.
How a Record Reaches Your Product Layer
- 01
Primary Source
Federal and state publications, dockets, permit datasets, and program notices.
- 02
PolicySight Collection & Evidence
Material facts are captured with their publisher and source link.
- 03
Source Verification
Values, units, dates, and status are normalized and checked against the source.
- 04
Reviewed Structured Record
One record per change, with facts and analysis kept separate.
- 05
Citylitics API / Product Layer
Structured JSON pulled on your schedule and mapped to your entities.
Structured Delivery Fields
| Field | Type | Description |
|---|---|---|
| record_id | string | Stable feed identifier for the reviewed record. |
| schema_version | string | Data contract version, currently policysight.citylitics.intelligence.v2. |
| headline | string | Short factual description of the change. |
| summary | string | Neutral summary of what changed, drawn from the source. |
| record_type | enum | PERMIT, FUNDING, RULEMAKING, ENFORCEMENT, MARKET_SIGNAL. |
| status | enum | PROPOSED, FINAL, or OBSERVED, preserved from the source. "sample preview" is a separate review state label and is excluded from reviewed findings. |
| jurisdiction | object | Country, state, locality, agency, and authority level. |
| permit_id | string | null | NPDES permit identifier when the record is permit based. |
| previous_value / current_value / unit | mixed | Before and after values for measurable changes. |
| percent_change | number | null | Computed change between before and after values. |
| topics | string[] | Tags across areas so overlaps remain visible. |
| entities | object[] | Agencies, jurisdictions, and facilities related to the record. |
| dates | object[] | Typed dates with precision, tied back to the fact they support. |
| facts | object | Labelled source facts with value, type, unit, and confidence. |
| detail | object | Area specific fields such as permit limits or funding terms. |
| evidence | object | Publisher, source URL, and safe locator for each material fact. |
| commercial_relevance | string | PolicySight analysis, kept separate from source facts. |
| affected_entity_classes | string[] | Types of organizations affected by the change. |
| reviewed_at | timestamp | When the record passed review and entered the feed. |
Structured Record Example
Loading example record...
Review how source backed records can fit into Citylitics workflows. Delivery scope and field mapping can be aligned to Citylitics priorities.