B2C · Individual
EmlakIQ Verify
Evidence-backed property check for buyers and advisors.
- Property identity and resolution confidence
- Zoning, risk and market context
- Missing and flagged fields
- Source, freshness and limitations
Institutional property data and decision infrastructure · Turkey
Turkey's property data and decision infrastructure.
EmlakIQ brings address, parcel, zoning, building, risk, market activity, and macro context under one property identity. The same core produces institutional screening, product integrations, and evidence-backed property reports.
A single property data spine for screening, integrations, and evidence-backed property reports.
Currently in early access for supported areas. See coverage
Delivery surface Report, screening, and API
Decision context Zoning, risk, market, and missing fields
Institutional discipline Provenance and freshness notes
Not an official appraisal, legal opinion or structural safety certificate. Every output includes coverage, source, freshness, confidence and explicit missingness.
Single property identity
Zoning and building context
Risk and seismic signals
Market activity
Source and confidence level
Data fragmentation
A property decision in Turkey cannot be read from a single source.
The same asset appears as disconnected fragments across address text, parcel ID, municipal zoning notes, building records, regional market activity, geological risk layers and macro credit indicators. Buyers, lenders, developers and product teams end up reconciling the same record over and over again. EmlakIQ brings those fragments back under one property identity, one decision backbone, and one traceable output surface.
| Source family | Raw shape | EmlakIQ normalization |
|---|---|---|
| Cadastral and address records | Inconsistent identifiers, geometry, text | Canonical entity identity |
| Zoning records | Municipal notes, parcel-level rules | Normalized zoning context |
| Building facts | Unit, floor, usage attributes | Physical context profile |
| Risk layers | Fault lines, hazard grids, geological polygons | Risk context fields |
| Market activity | Monthly sales/mortgage/transfer signals | Temporal market context |
| Macro-credit series | TÜİK and BDDK period data | Geography-linked macro overlay |
How it works
From a raw address to a decision backbone.
You submit an address, parcel ID, or exact location.
Even partial or incomplete input. EmlakIQ resolves it against authoritative cadastral records, location context, and building data, then returns a single, traceable property identity.
Address text Parcel ID Exact location
We cross-reference multiple authoritative sources.
Zoning records, cadastral boundaries, seismic risk layers, market activity data, project inventory and macro credit indicators are attached to the same cadastral spine. Each source is traced, freshness-rated, and flagged where missing or unreliable.
TKGM · Zoning · TÜİK MTA · EFEHR · BDDK
You receive an evidence-backed decision file.
Every output tells you what is known, what is missing, what is inferred, and its confidence level. No hidden uncertainty. The same decision backbone becomes a report, a screening output, or a structured JSON payload.
Report Screening output API payload
The full data pipeline (Raw → Evidence → Normalization → Gold → Intelligence → Dossier) is documented in Methodology.
Products
One data backbone, three product surfaces.
B2B · Institutional
EmlakIQ Analyst
Professional portfolio screening and exception detection for institutional teams.
- Automated portfolio-wide screening
- Zoning change and coverage monitoring
- Macro data compliance analysis
- Anomaly, missing data and risk queue
API · Developer
EmlakIQ Data API
Production-ready data gateway for property identity, zoning, risk and market context.
- Address, parcel, coordinate and record resolution
- Normalized JSON outputs
- Source and confidence fields
- Batch audit and Dossier production
Trust system
There is a larger platform underneath the report surface.
EmlakIQ Verify reads like a simple report. Underneath is an institutional platform with a canonical cadastral spine, cross-domain intelligence profiles, replay-safe dossier assembly, and serving verification discipline. The same backbone also powers Analyst and the Data API.
Control dimension Example display Why it matters
Identity resolution tr_34_kadikoy_bagdat_cad_0412 · building · confidence 0.84 Address, geometry, and parcel reference resolve into one property identity.
Snapshot contract snapshot dos_2026_06_sample · replayable dossier The same inputs can reproduce the same dossier deterministically.
Source manifests imar_ibb_2026_03 · afad_seismic_2018 · market_may_2026 Fields are served with the exact batch and source family behind them.
Freshness contract zoning 2026-03-15 · market 2026-05 · seismic 2018-12-01 Source date and load window stay explicit on the output surface.
Coverage and field state supported / partial / missing · known / inferred / missing Derived or missing fields are disclosed directly instead of being softened.
Decision outputs Verify report · Analyst queue · Radar view · API payload The same evidence contract is enforced across every product surface.
Why it is different
Not a data vendor. A property intelligence backbone.
01
Canonical identity spine
Address, parcel, building and project records converge on one stable property identity.
02
Cross-domain intelligence graph
Zoning, risk, market, macro and project signals attach to parcel, building and neighborhood profiles.
03
Replay-safe output discipline
Source trace, snapshot identity and serving verification preserve the same decision standard.
Sample report
One report, read at three levels.
01
Decision summary
A readable decision summary on the first page.
02
Evidence ledger
Source, freshness and confidence level.
03
Technical output
JSON object and snapshot metadata.
Institutional
Built for decision operations, not manual portfolio research.
EmlakIQ Analyst does not turn asset lists into a manual review panel. It resolves records, measures coverage, tracks changes, reads zoning, risk, market and macro context against one institutional decision standard, and produces an exception queue.
Data API
The same serving contract becomes a JSON surface inside your product.
Every output carries coverage, source, freshness, confidence and explicit missingness. This is not just data delivery. It is the EmlakIQ decision backbone exposed inside your application.
GET /v1/property/resolve
200 OK Versioned payload Source trace Missing-field disclosure
{
"emlakiq_id": "tr_34_...",
"resolved_scope": "building",
"identity_confidence": "bounded",
"zoning": {
"status": "known",
"source_freshness": "2026-06-..."
},
"risk_context": {
"seismic_hazard": "available",
"confidence": "derived"
},
"market_context": {
"grain": "district_month",
"period": "2026-04"
},
"missing_fields": ["energy_class"],
"provenance_refs": ["source_manifest:..."],
"snapshot_id": "dos_..."
}Growth layers
Market outlook and editorial analysis.
Radar
District-level market signals.
Track zoning change, macro deviation and market activity signals by district and project. We started with Kadıköy.
Kadıköy Beşiktaş · Coming soon Üsküdar · Coming soon
Radar Overview → Pulse
Methodology and data notes.
EmlakIQ Pulse publishes source changes, methodology updates and regulatory developments in an editorial format.
Methodology notes Data updates Regulation
View Pulse → Coverage and limitations
What we know. What we don't.
Known Cadastral identity · Zoning context (supported regions) · Seismic context
Missing Energy performance certificate · Unit-level records (partial)
Inferred Market activity at district level · Macro indicators
Not supported Official valuation · Title deed legal opinion · Structural safety certification