Skip to content
NL

Migrating from Matrixian

Based on Matrixian's public documentation, October 2026.

Using Claude Code? The migrate-from-matrixian skill moves your code over with these tables; see the Claude Code plugin.

MatrixianWhatHuispedia
GET /homevalue, GET /homevalue/valueHome valuationGET /v5/properties/{locator}/valuation
GET /homevalue with your own characteristicsValuation with your own inputsPOST /v5/valuations/scenarios
GET /homevalue?nReferences=Valuation with referencesGET /v5/properties/{locator}/valuation/plus (contract)
With the five best reference homes.
GET /leadtoolValue rangeGET /v5/properties/{locator}/valuation
The range is lower to upper.
GET /mx-reference-finderReference homesGET /v5/properties/{locator}/references (contract)
GET /mx-transaction-finderSale priceGET /v5/properties/{locator}/transactions (contract)
GET /woz-value, GET /woz-value/liveWOZ valueGET /v5/properties/{locator}/woz
GET /mx-house-detailsProperty characteristicsGET /v5/properties/{locator}
GET /v5/properties/{locator}/energy-label
GET /bag-dataBAG dataGET /v5/addresses/{locator}
GET /v5/buildings/{bag_pand_id}
GET /buurtinfoNeighbourhood informationGET /v5/areas/{area}/demographics
GET /v5/areas/{area}/stats
GET /v5/areas/{area}

Transactions, reference homes and home valuation plus come with a contract: [email protected].

MatrixianHuispedia
KeyAuthorization: Bearer <api-key>Authorization: Bearer hp_… or X-API-Key: hp_…
Base URLhttps://api.matrixian.com/v1https://huispedia.dev/v5
MethodGET with query parametersGET with the home in the path; POST only for scenarios
Response{id, params, data, error, meta, status}The data at the top level; meta with request_id and credits
MatrixianHuispediaNote
postalCode + houseNumber + houseLetter + houseNumberExt1076LJ-12-2Postcode, number and extension with hyphens in the path; letter and extension go together in the last part.
houseLetter, houseNumberExthouse_number_extNot sure: GET /v5/addresses/1076LJ-12?all=true returns every home with its house_number_ext.
bagId, bagNumberId (nummeraanduiding)bag:0363200000028422
bagObjectId, bagBuildingIdbag_verblijfsobject_id, bag_pand_idIn GET /v5/addresses/{locator}; ask for a building with GET /v5/buildings/{bag_pand_id}.
valuationDate (2026-09-01)as_of_date (2026-09-01)
buurtCode (BU04170328)neighbourhood:BU04170328An area is level:code; GET /v5/areas/lookup?postcode=1076LJ gives the codes.

More in Addresses and areas.

Home valuation

GET /homevalue → GET /v5/properties/{locator}/valuation

MatrixianHuispediaNote
postalCode, houseNumber, houseLetter, houseNumberExt{locator}
valuationDate?as_of_date=Up to six months back; further back with the valuation history.
data.predictedValue, data.weightedValuevaluation.value
data.valueDatevaluation.as_of_date
data.accuracyconfidence.score_pctHere the probability that the value is within 10% of a sale price.
data.confidenceClassconfidence.classThere 0 to 5; here high, medium or low.
data.weightedValueRange (Leadtool)valuation.lower, valuation.upper, valuation.intervalTwo numbers with their certainty (80%).
data.bagId, postalCode, houseNumber, houseNumberExt, street, city, municipalityaddress.bag_id, address.postcode, address.house_number, address.house_number_ext, address.street, address.city, address.municipality
data.buildType, buildYear, useSurface, parcelSurface, volume, energyLabel, roomstype.house_type, construction.construction_year, dimensions.living_area_m2, dimensions.plot_area_m2, dimensions.volume_m3, energy.energy_label, rooms.rooms
In GET /v5/properties/{locator}
From Property characteristics.
data.indexedPrice, histTransactionPrice, histTransactionDatedata[].price_indexed, data[].price, data[].transaction_date
In GET /v5/properties/{locator}/transactions
Every sale of the home, with a contract.
data.references[]references[]
In GET /v5/properties/{locator}/valuation/plus
data.numZip*, medZip*, numStr*, medStr*market.transactions_count, market.avg_transaction_price
In GET /v5/areas/{area}/stats
Per neighbourhood, district or municipality; not per postcode or street.

Valuation with your own characteristics

GET /homevalue → POST /v5/valuations/scenarios

MatrixianHuispediaNote
postalCode, houseNumber, houseNumberExtdata[].postcode, data[].house_number, data[].house_number_ext
useSurfacedata[].living_area_m2
parcelSurface, volumedata[].plot_area_m2, data[].volume_m3
buildYear, numberOfRoomsdata[].construction_year, data[].rooms
buildTypedata[].house_typeterraced, corner, semi_detached, detached or apartment.
energyLabeldata[].energy_label
monumentNot available here
data.predictedValuedata[].valuation.value

Property characteristics

GET /mx-house-details → GET /v5/properties/{locator}

MatrixianHuispediaNote
objectTypetype.object_type
buildYearconstruction.construction_year
livingSurface, useSurfacedimensions.living_area_m2, dimensions.bag_area_m2
otherIndoorSpace, attachedOutdoorSpace, externalStorageSpacedimensions.other_indoor_m2, dimensions.building_bound_outdoor_m2, dimensions.external_storage_m2
parcelSurface, volumedimensions.plot_area_m2, dimensions.volume_m3
numberOfRooms, numberOfBedrooms, numberOfBathrooms, numberOfToiletsrooms.rooms, rooms.bedrooms, rooms.bathrooms, rooms.separate_toilets
energyLabelenergy.energy_label
energyLabelRegistrationValidUntilvalid_to
In GET /v5/properties/{locator}/energy-label
latitude, longitudeaddress.location.lat, address.location.lon
bagObjectId, bagBuildingId, neighbourhood and municipality codesbag_verblijfsobject_id, bag_pand_id, neighbourhood.code, municipality_code
In GET /v5/addresses/{locator}
descriptionNot available here

Reference homes

GET /mx-reference-finder → GET /v5/properties/{locator}/references

MatrixianHuispediaNote
nReferences?limit=3 to 30.
valuationDate?as_of_date=
maxDistance, minTransportDate?max_distance_m=, ?max_age_months=
minUseSurface, maxUseSurface?min_living_area_m2=, ?max_living_area_m2=
minBuildYear, maxBuildYear?min_construction_year=, ?max_construction_year=
allowedHouseTypes?same_type=Only the same type, or all types.
locationWeight, houseDetailsWeight, transportDateWeight?sort=Sort by similarity, distance or date; no weights of your own.
references[]data[]
distance, dateSaledata[].distance_m, data[].transaction_date
houseType, buildYear, useSurfacedata[].house_type, data[].construction_year, data[].living_area_m2
referenceScore, locationScore, houseDetailsScoreNot available here
offeredPrice, imageFront, descriptionNot available here

Transactions

GET /mx-transaction-finder → GET /v5/properties/{locator}/transactions

MatrixianHuispediaNote
valuationDate, dateTransportNot available hereYou get every sale of the home; filter on transaction_date yourself.
saleDate, transportDatedata[].price_agreement_date, data[].transaction_date
transactionPricedata[].price
transactionPriceIndexeddata[].price_indexedAt today's price level.

WOZ value

GET /woz-value → GET /v5/properties/{locator}/woz

MatrixianHuispediaNote
wozValues[].valuationDate, wozValuevalues[].reference_date, values[].value
characteristicstype, dimensions, construction
In GET /v5/properties/{locator}

Neighbourhood information

GET /buurtinfo → GET /v5/areas/{area}/demographics

MatrixianHuispediaNote
buurtCode or an address{area}Codes from GET /v5/areas/lookup?postcode=.
Bevolkingpopulation, households, age
Wonenstock
In GET /v5/areas/{area}/stats
geometrygeometry
In GET /v5/areas/{area}
With include=geometry.
Inkomen, Energie, CriminaliteitNot available here

An error is application/problem+json with a fixed code; every code is on Errors.

MatrixianHuispediaNote
400 (errors[].reason is the parameter)400 invalid_requesterrors names what is wrong per field.
401401 unauthenticated, 401 key_revoked, 401 key_expired
403 (access_denied, missing_subscription)403 entitlement_required, 403 forbidden
403 (rate_limit)429 rate_limitedHere 429; wait Retry-After seconds.
404 (unknown address)404 not_found
500500 internal_error
503503 upstream_unavailable
{id, status: "failure", error: {code, message, errors}}application/problem+json with code, detail, errors, request_id
MatrixianHuispedia
RateNot published; at the limit 403 rate_limit6 per second and 6 at once on a paid plan; 1 and 2 on Free; X-RateLimit-Remaining in every response
BulkNo bulk endpoint documentedPOST /v5/valuations/scenarios: 100 homes per call
Correlationid, X-Amzn-Trace-Idmeta.request_id, request_id

Matrixian

curl "https://api.matrixian.com/v1/homevalue?postalCode=1076LJ&houseNumber=12&houseNumberExt=2" \
-H "Authorization: Bearer $MATRIXIAN_KEY"

Huispedia

curl https://huispedia.dev/v5/properties/1076LJ-12-2/valuation \
-H "Authorization: Bearer $HUISPEDIA_KEY"
  • Checking availability first (/homevalue/available): not available here; a 404 not_found costs no credits.
  • Monument status as valuation input (monument): not available here.
  • Market figures per postcode or street (numZip*, numStr*): not available here; per neighbourhood instead.
  • Your own weights and scores per reference home: not available here; the order gives the likeness.
  • Income, energy and crime per neighbourhood: not available here.
  • Housing costs (/local-tax-energy-expenses): not available here.
  • Home photos (/house-images, /get_front_view): not available here.
  • Cadastral objects and ownership extracts: not available here.
  • Commercial transactions: not available here.
  • An interval with lower and upper bound on every valuation: no equivalent at Matrixian, except the Leadtool's range string.
  • 409 address_ambiguous with the candidates when an address has several homes: no equivalent at Matrixian.
  • What-if scenarios and up to 100 homes per call: no equivalent at Matrixian.
  • Monthly valuation history: no equivalent at Matrixian.
  • Price index per area (/v5/areas/{area}/trends): no equivalent in Matrixian's public documentation.
  • Environment (foundation, subsidence, noise, air) per address: no equivalent in Matrixian's public documentation.