PROPERTY DATA INFRASTRUCTURE FOR KOREA

Every portal, every listing.
One clean record.

Korean property listings are scattered across portals, written in free-text agent notes, and duplicated everywhere. JipData collects them, merges the duplicates, and extracts structured fields — then Claude writes the descriptions agents actually publish.

Multi-portal ingestion
One record per property
Structured fields from free text
Early access — onboarding in batches
The data

What one listing looks like after JipData

The same apartment appears on multiple portals in different formats. After collection and deduplication, it becomes a single structured record.

  normalized_listing.json
{
  "listing_id": "jd_8f3a21",
  "type": "apt_jeonse",
  "address": { "dong": "잠실동", "complex": "○○자이", "floor": 14 },
  "price_krw": 580000000,
  "price_per_pyeong": 21400000,
  "maintenance_fee": { "amount": 230000, "includes": ["heating", "water"] },
  "station": { "name": "잠실새내역", "walk_min": 6 },
  "sources": 3,  // merged from 3 portals
  "agent_note_parsed": true
}
Price & 평단가Sale / jeonse / monthly rent, normalized to price per pyeong
Maintenance feeAmount plus what's included — parsed from agent notes
Floor planLayout, direction, area in both m² and pyeong
Station distanceNearest station and walking time, geocoded
Move-in dateAvailable date extracted from free text
Source historyWhich portals listed it, and when it first appeared
Pipeline

What we're building

Three pieces of the same system — each usable on its own.

IN DEVELOPMENT

Collection & dedup pipeline

Scheduled collectors pull listings from Korea's major portals. Address, floor plan, price and photo similarity merge the same property across sources into one record.

IN DEVELOPMENT

DescMaker

Claude-powered listing copy in natural Korean. A structured record in — an agent-ready description out, in the office's own tone.

EARLY ACCESS SOON

JipData API

Clean, queryable real-estate data for proptech builders. Search by district, price band, size or station distance — delivered as JSON.

Roadmap

Where we are

We're a small team in Seoul. This is what we're doing — in order.

NOW

Pipeline coverage

Running the collection + dedup pipeline against Seoul districts, expanding coverage area by area. Measuring dedup accuracy before we open anything.

NEXT

DescMaker pilot

Listing-description generation tested with a small group of agent offices — their listings, their tone, their feedback.

LATER

Public API

The normalized dataset opened to outside builders, with a field dictionary and honest coverage notes.

FAQ

Questions we get

Where does the data come from?

Public listings on Korea's major property portals. We collect them on a schedule, merge duplicates across sources, and keep a record of which portals carried each listing.

Why does dedup matter?

Agents post the same property on every portal — often with slightly different wording. Without deduplication, any search or analysis counts the same apartment several times.

What does Claude do in the pipeline?

Korean agent notes are unstructured free text — "관리비 23만 수도·난방 포함, 입주 협의". Claude extracts structured fields from them and generates natural listing descriptions. Rule-based parsing can't handle the variety.

Can I use the API today?

Not yet — we're onboarding early-access partners in small batches while coverage expands. Join the list below and we'll reach out when your region is covered.

Contact

Early access & hello

Coverage updates, pilot openings and API invites — in your inbox.

Early access list

Tell us your region and use case — we onboard in batches as coverage lands.

Work with us

Agent office pilot, custom extraction fields, or data partnership — tell us briefly what you need.

Email us