Urgent.News

What's breaking now, across thousands of outlets.

Tech

MLIT Japan Property Prices — Free Data for AI Agents & Real Estate Investors

Japan's Ministry of Land, Infrastructure, Transport and Tourism (MLIT) publishes detailed real estate transaction prices for all 47 prefectures — but accessing this data programmatically has always been clunky. I've built an open tool that makes it trivially easy for AI agents and investors to query this data. What's in the data 47 prefectures with transaction price records Q3 2005 onwards — over…

The Ministry of Land, Infrastructure, Transport and Tourism (MLIT) in Japan has made extensive property transaction price data available for all 47 prefectures. This data, which spans over a decade starting from Q3 2005, includes information such as price, land area, location, building details, and zoning classification. The data is clean and provided in JSON format via an API.

Access to this data is made simple through two options. The first is an Apify actor, which is API-friendly and allows users to query transaction prices directly via the Apify API. The second option involves an MCP server, designed for AI agents like Claude or Cursor, which enables them to query the data using natural language.

This tool is particularly useful for real estate investors, market analysts, AI agents conducting research, and data journalists who can use it to build maps and charts of real estate trends in Japan. The Ministry of Land, Infrastructure, Transport and Tourism (MLIT) is Japan's department responsible for land, infrastructure, transport, and tourism. Their Reinfolib system (XIT001 dataset) is the primary source of this property price data, which is the most comprehensive official property price database in Japan.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I benchmarked seven hotel price APIs on the same Rome room, and the prices were 16% apart because of tax

I run FlightPowers, a small API that reads live Booking.com rates, so I'm biased about one row of this table. I wanted to know how it holds up next to the APIs people usually compare it with, so I…

  • Seven hotel price APIs benchmarked for same Rome room
  • 16% price discrepancy found among APIs, primarily due to tax differences
  • API choice and market sourcing significantly impact final price

Sitecore Search API Key Authorization - How We* Tackled It

Sitecore sent out an email yesterday that was actually a "kick the can" email, regarding a mandatory API key authorization for Search and Events APIs.

  • Sitecore mandates API key authorization for Search and Events APIs, delayed to mid-December 2026.
  • Non-production environment configured to test rule enforcement for Sitecore Search widget provider.
  • New widget provider object developed to securely handle customer key and authorized API key.

Nodejs Queue Publish for Offline Users: 12-Minute Live Poll Notifications

Nodejs Queue Publish for Offline Users: 12-Minute Live Poll Notifications Short answer: in a Nodejs-style service, queue the result before you publish it so offline users still get notified.

  • Queue events before publishing to ensure delivery to offline users
  • Use per-recipient inbox with idempotent fan-out for strong delivery evidence
  • Implement client acknowledgements or durable cursors for proof of notification visibility

Anti-Patterns in Software Blogging

Anti-Patterns in Software Blogging Some excellent writing advice from Michael Lynch. Michael warns against "meandering intros", misjudging your reader's existing knowledge, assuming they'll read your…

More from Wednesday 7 October →