atHome.lu
Included in the maintained Luxembourg source scope. Record-level provenance identifies the contributing listing when present.
Luxembourg coverage
Luxembourg property listings, with the operating state visible.
Search one maintained view of sale and rental listings across the supported Luxembourg source scope. The page separates the current serving snapshot from source observations, examples, and availability limits.
Current scope
What the Luxembourg market page represents.
The scope is defined by the maintained delivery contract, not by every source or listing that may exist in the country.
- Transactions
- Sale and rent
- Geography
- Luxembourg, resolved through canonical places
- Sources
- atHome.lu and Immotop.lu
- Delivery
- Authenticated console, REST API, JSON and CSV
Source scope
Two maintained integrations. Source evidence stays attached.
Current records may be supported by one or more source assertions. Source names identify the integration scope only; CleanedWeb is not affiliated with the referenced platforms.
Immotop.lu
Included in the maintained Luxembourg source scope. Record-level provenance identifies the contributing listing when present.
Source coverage matrix
What publication proves for each integration.
| Source | Maintained scope | Provenance | Equal field depth |
|---|---|---|---|
| atHome.lu | ✓ Included | Attached when contributing | — Not asserted |
| Immotop.lu | ✓ Included | Attached when contributing | — Not asserted |
The delivery contract
Ask one bounded question. Receive one reviewable shape.
The following request and response are documented contract examples. They demonstrate the Luxembourg schema and are not presented as a live listing or current search result.
{
"market": "LU",
"response_schema": "property-profile-v2",
"deal_type": [
"buy"
],
"location": "Belair",
"location_place_id": "lux-neighbourhood-belair",
"property_categories": [
"apartment"
],
"price_qualities": [
"known"
],
"min_price": 500000,
"max_price": 1000000,
"min_bedrooms": 2,
"sort_by": "observed_at",
"sort_order": "desc",
"limit": 100
}{
"total_matched": 1,
"returned": 1,
"snapshot": {
"dataUpdatedAt": "2026-08-18T08:15:00+00:00",
"availableRecords": 33947,
"projectionGenerationId": "projection_lu_20260818_081500"
},
"results": [
{
"schema_version": "property-profile-v2",
"property_entity_id": "property_01JEXAMPLE",
"availability": {
"status": "active",
"active_deal_types": [
"Buy"
],
"determined_at": "2026-08-18T07:58:12+00:00",
"method": "current_source_observation",
"coverage_receipt_ids": [
"receipt_01JEXAMPLE"
],
"limitations": []
},
"location": {
"city": "Luxembourg",
"neighbourhood": "Belair",
"postal_code": "L-1150",
"latitude": 49.6123,
"longitude": 6.1021,
"precision": "neighbourhood"
},
"property": {
"category": "apartment",
"floor_area": 82,
"bedrooms": 2,
"bathrooms": 1,
"year_built": 2018,
"energy_class": "A",
"amenities": [
"Lift",
"Terrace"
]
},
"sources": [
{
"source_id": "example_property_marketplace",
"listings": [
{
"listing_id": "A-1842",
"deal_type": "Buy",
"status": "active",
"is_current": true,
"first_observed_at": "2026-08-01T06:20:00+00:00",
"observed_at": "2026-08-18T07:58:12+00:00",
"pricing": {
"asking_price": {
"amount": 895000,
"currency": "EUR"
},
"quality": "known"
},
"content": {
"title": "Apartment for sale in Belair"
}
}
]
}
]
}
]
}Comparable records
The fields downstream products can keep.
Values remain evidence-bound. Missing fields stay missing, and source assertions remain available beside the preferred canonical view.
Normalized delivery
- Canonical property identity
- Source listing identity
- Price and currency
- Transaction and lifecycle state
- Property category
- Floor and land area
- Rooms, bedrooms and bathrooms
- Address and canonical geography
- First-seen and observed timestamps
- Advertiser and contact channels when present
Search filters
- Location
- Transaction type
- Property category
- Price
- Floor and land area
- Rooms and bedrooms
- Lifecycle state
- Advertiser type
- Source count
- Observation date
Contract breadth
Interface surface, not a completeness percentage.
These counts describe the published contract and filters. Whether a field is present still depends on the contributing source observation.
Normalized field groups10
Search filters10
Transaction types2
Active integrations2
Property entity, source listing, source count
Price, currency, transaction and lifecycle state
Category, areas, rooms, bedrooms and bathrooms
Address components and canonical place resolution
First-seen, observed and serving-snapshot timestamps
Contributing source and advertiser context when present
Freshness is a timestamp
A request time does not make the underlying record current.
The capabilities manifest reports when the maintained serving projection was last rebuilt. Each delivered record separately reports when its source evidence was observed.
01
Projection rebuilt
02
Evidence checked
03
Request performedRuntime event — not a source-observation timestamp
- Available records and the rebuild timestamp are a dated snapshot of the public capabilities manifest.
- Source inclusion identifies the maintained Luxembourg integration scope; it does not imply equal depth or complete inventory from each source.
- Record availability is not a source-real-time guarantee. Individual records retain their own observation timestamps.
Canonical property example
Several listing assertions can support one reviewable property.
This is a documented contract illustration, not a live Luxembourg listing. It shows the identity relationship expressed by the public example response.
Source-scoped identity and observed evidence remain attached.
- Market
- LU
- Category
- apartment
- Source count
- 1
- Schema
- property-profile-v2
Known limits
What this page does not imply.
These boundaries are part of the product description, not fine print.
- 01
The serving count is a dated projection snapshot, not a promise that every record remains available at request time.
- 02
Source coverage does not imply complete inventory or identical field depth across atHome.lu and Immotop.lu.
- 03
An observed asking price is not a completed transaction, valuation, deed, or ownership record.
- 04
Availability can change between source observations. Last-known state and observation time remain distinct.
- 05
Descriptions, images, floor plans, and other source media have separate use and republication rights.
- 06
MCP transport is not advertised for Luxembourg while the public capabilities manifest has no MCP endpoint.
Where the market fits
Use Luxembourg inventory inside a real operating workflow.
Continue with the evidence
Read the article behind each market decision.
Start with Luxembourg
Test the market against your own search.
Review the available locations, run a bounded query, and inspect canonical identity, source evidence, timestamps, and Unit receipts before automating the workflow.