PropData Real Estate OS

Automated enrichment control plane - live in production
COLLECTING UPTIMELIVE PRODUCTIONBuild with the API
PROPDATA_V51_AUTOMATED_ENRICHMENT_LAYER_TRUTHThis dashboard measures the automated enrichment layer.It does not include manual county ingestion, the nightly parcel pipeline or the full property-and-parcel foundation. Every number shown is backed by enrichment production state.
Independently observed production reliability

Availability you can audit—not a marketing claim.

Three customer-facing surfaces are probed every five minutes by a separate reliability Worker. Missing observations count against availability; enrichment motion and data freshness remain separate truths.

No seeded history · No synthetic uptime
Collecting first-party observations now.Percentages appear only after the minimum real sample window is satisfied.
The automated enrichment factory behind the API

Turn fragmented public records into product-ready property intelligence.

The operating system for real estate intelligence.

Ship underwriting, acquisition, risk and research products without building hundreds of fragile jurisdiction integrations. PropData converts official infrastructure into one governed, property-linked intelligence layer while uncertainty is stopped before it can reach your customers.

Ship intelligence fasterBuild on one normalized contract instead of maintaining source-specific plumbing.
Reduce integration dragReuse property identity, provenance and classification across every customer workflow.
Protect product trustKeep uncertain records outside customer products until authority and jurisdiction are proven.
The commercial return is reusable infrastructure: faster launches, fewer brittle dependencies and defensible customer-facing decisions.
Official-source discoverySchema intelligenceProperty graph attachmentPublication truth
Live autopilot trust pipelineOperating now
01
Official source discoveryFind authoritative public infrastructure
Observed
02
Jurisdiction proofVerify authority, ownership and geography
Proven
03
Schema intelligenceInfer identity, fields and lifecycle meaning
Understood
04
Property graph attachmentConnect records to parcels and locations
Attached
05
Publication boundaryPromote trusted output; quarantine uncertainty
Governed
Customer-facing intelligenceTruth gate enforced
-Autopilot enrichment records
-Autopilot records published
-Autopilot data jurisdictions
The national intelligence command network - live
Verified automated-enrichment signals converge on PropTechUSA.ai's Saint Paul command center. Routes represent logical production flow, not physical network paths. Select a state to inspect its output.
System scope - no inflated totals

One intelligence platform. Three operating layers. This dashboard measures the automated middle layer.

PropData is larger than the activity visible here. The live metrics below isolate the automated enrichment OS so its output, motion and truth boundary can be evaluated without mixing in manually acquired or nightly refreshed parcel data.

01Broader platform

Property + parcel foundation

The national base layer assembled and maintained through direct data work outside this autopilot.

Manual county ingestion and validationCanonical property and parcel recordsNightly parcel ingestion and refresh
02This dashboard

Automated enrichment OS

The autonomous layer created to continuously expand, understand and govern enrichment intelligence.

Official-source discoveryJurisdiction and schema proofClassification, attachment and publication
03Customer outcome

API-ready intelligence

Trusted enrichment output is attached to property context and made usable across customer products.

Property-linked public signalsGoverned customer publicationReusable API and integration outputs
Not counted in this dashboard
Manual and county ingestion workNightly parcel ingestion or refreshTotal parcel and property coverageOther PropData intelligence products
Why isolate it? Mixing every PropData data source into these totals would obscure whether the automation itself is moving, producing trusted output and delivering customer value.
The proprietary decision layer

The hard part is not collecting a row. It is teaching infrastructure when that row deserves to become intelligence.

Anyone can call an endpoint. PropData built the control plane that can determine who published it, where it belongs, what its fields mean, whether it represents a new record, how it connects to a property and whether a customer should ever see it.

-Enrichment records understood
-Passed the publication boundary
-Average classification confidence
-Production lanes moving now
Unfamiliar official source
Representative source shape
case_no"CV-..."
insp_status"OPEN"
site_addr"..."
pin_or_apn?unknown
record_identity?unproven
jurisdiction?must verify
Collection is not publication.Raw availability creates questions. The decision layer must produce evidence before this row can enter the graph.
Decision kernel active
01Authority + jurisdiction proofVerify
02Schema + identity inferenceResolve
03Lifecycle classificationUnderstand
04Parcel + property attachmentConnect
05Confidence + publication gateGovern
Governed intelligence contract
Eligible for customer publication

Property-linked signal

Normalized, traceable and reusable
authority_idJurisdiction proven
source_record_idIdentity stable
parcel_linkProperty attached
lifecycle_stateMeaning classified
confidenceEvidence scored
provenanceSource preserved
Uncertainty never disappears into the total.Records that cannot prove identity, jurisdiction, structure or fitness are held for review instead of being marketed as coverage.

Jurisdiction-aware reasoning

Authority identity, official ownership, geography and source provenance are tested before data is trusted.

Stops the right data from landing in the wrong place

Adaptive schema intelligence

The OS identifies case IDs, parcel links, addresses, lifecycle states, dates, values and enforcement signals across unfamiliar schemas.

Converts source-specific columns into a reusable contract

Stable identity resolution

Source-native identifiers are preserved so records remain distinct, updates are idempotent and refreshes do not collapse the graph.

Creates durable memory and real change detection

Quarantine-first governance

Low-confidence, mismatched or structurally incomplete records are held outside customer products instead of padded into coverage claims.

Uncertainty is contained instead of hidden

Property graph attachment

Municipal records connect to parcels, coordinates and normalized locations so isolated cases become property-level context.

Turns public records into product-ready intelligence

Outcome-truth orchestration

Transport success, source discovery, ingestion, publication and historical completion remain separate observable outcomes.

A green request is never confused with customer value
The compounding advantage

Every new source teaches the infrastructure how to understand the next one.

The source memory, jurisdiction evidence, schema decisions, identity rules and property relationships become reusable operating knowledge. That is the moat: not a downloaded file, but an intelligence system that gets harder to replicate every time it runs.

Enterprise orchestration

Customer priorities enter a dedicated production lane

Requested jurisdictions move through discovery, proof, ingestion and publication with their actual outcome visible.

Active autonomous lanes

The live view below shows atomic run tokens, stage progression and fresh heartbeats from production.

Live transformation proof

What the OS understood in the last 24 hours

These are field families genuinely detected inside newly ingested records - not assumed attributes or decorative platform-wide zeros.

24-hour new-record velocity

This chart isolates brand-new entities and newly published entities. Existing-record refresh throughput is reported separately above so successful refresh ingestion cannot be mistaken for zero activity.
Evidence-backed autonomy

Every production lane must prove motion and customer value

This control plane separates queue activity from real progress, trusted-source proof and published output. A successful request alone never earns a healthy state.
Edge-state diagnostics

When trust proof fails, the reason stays visible.

Enterprise teams can see the failing proof boundary, the source reason retained by the OS and the next verification step. Quarantine is an observable decision, not a black box.

Authority proofGeographic proofSource fitnessPublication truth

Record families becoming API-ready intelligence

Classified from row content. The collection lane is never used as the answer.
One intelligence platform

One property identity. Every intelligence layer working as a system.

A parcel is not a product. A comp is not a product. A violation is not a product. The advantage appears when property, parcel, geospatial, market, rent, comps, neighborhood, hazard and public-record intelligence resolve around the same place.

One property identityShared resolution layer
Eight intelligence systemsComposable capabilities
One API surfaceReusable customer delivery
Continuous enrichmentInfrastructure that compounds

Stop stitching vendors together. Start with a property intelligence layer.

PropData gives product teams a shared identity and context system that can power underwriting, acquisition, risk, research and automation without rebuilding the data foundation for every workflow.

Autonomous compounding infrastructure

The operating loop does not finish. It gets smarter.

This is reusable infrastructure that compounds, not a one-time collection project. Each cycle produces customer output and preserves the operating knowledge needed to make the next cycle faster, safer and more precise.

Compounding source memoryEvery cycle expands what the OS knows how to find, understand and trust.
01

Discover

Locate official public infrastructure and preserve source memory.

02

Prove

Verify authority, geography, ownership and source fitness.

03

Understand

Infer schemas, stable identities and real field meaning.

04

Attach

Resolve locations, parcels and property relationships.

05

Publish

Promote trusted intelligence and quarantine uncertainty.

06

Revisit

Observe known records again and surface meaningful change.

Coverage and jurisdiction evidenceState queue, exact production jurisdictions and rolling output.
Field coverage methodologyExact live-graph coverage and categories not yet detected.
Counts below come from production entity rows. Undetected categories remain explicit and are never presented as universal zeros.
Registry census and technical evidenceCustomer-data tables separated from telemetry, queues and configuration.

Public Records Registry census

Populated field cells are evidence, not deduplicated property counts.

Durable snapshot history

Historical graph deltas shown with their recorded timestamps; these are audit events, not the current live run.

Why teams build on PropData

The commercial advantage is an intelligence layer that improves underneath every product.
Independent

Own the intelligence layer

Reduce dependence on static vendor feeds with reusable, source-aware infrastructure.

Observable

See the truth in production

Know what was discovered, trusted, held, published and refreshed - without inflated coverage theater.

Extensible

Prioritize customer demand

Enterprise requests can enter dedicated lanes while the national graph continues compounding.

API-first

Ship intelligence, not plumbing

Build property and risk workflows on normalized outputs instead of maintaining hundreds of brittle source adapters.

Build on a real-estate intelligence system that can prove its work.

Use the API today, or talk with us about a custom endpoint, priority jurisdiction or enterprise integration.