# Japan Used Cars (carsensor.net) (`jpopendata/japan-used-cars-carsensor`) Actor

Japanese used-car listings from carsensor.net — price, year, mileage, repair history, inspection and dealer info by maker/prefecture, English schema. Unofficial; not affiliated with Recruit Co., Ltd.

- **URL**: https://apify.com/jpopendata/japan-used-cars-carsensor.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 57.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 per records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Used Cars (carsensor.net)

**Japanese used-car listings — price, year, mileage, repair history, inspection status and selling-dealer info — from carsensor.net, one of Japan's largest used-car marketplaces, in a clean English schema.**

This Actor searches carsensor.net's public used-car listings by maker and prefecture and returns each vehicle as English-schema JSON: maker (Japanese + English), model and grade, base vehicle price and total payment in JPY, first-registration year, mileage in km, engine displacement, transmission, repair-history flag (修復歴), inspection (車検) expiry, color, body type, and the selling dealer's business name, city and prefecture. With `detailFetch` it adds drive type, engine type (hybrid/EV/…), steering side, seats, doors and the dealer's business address from each vehicle's detail page. Optional client-side filters narrow by model keyword, price window (万円) and year window.

Japan's used-car market is a major export source (JDM icons, hybrids, kei trucks), but carsensor.net is Japanese-only — invisible to most international tooling. This Actor is the bridge.

> **Unofficial tool.** Not affiliated with or endorsed by Recruit Co., Ltd. or carsensor.net. It collects **publicly available data only** (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), and extracts **factual data only** — vehicle facts and dealer business identity; no review content, no dealer marketing prose, no personal data of any kind (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

***

### Who is this for?

- **Used-car exporters & overseas dealers** — source JDM vehicles by maker, model, price and repair history before they hit the auctions; the repair-history flag (修復歴) and inspection status are exactly the fields export buyers check first.
- **Market & price analysis** — used-car price levels by model, year and mileage across all 47 prefectures; a public-listing alternative to closed auction-sheet data.
- **Automotive SaaS & valuation tools** — feed live Japanese retail asking prices into pricing models.
- **Data teams** — a stable English schema over a Japanese-only source.

### Sample output (dataset item)

```json
{
  "carName": "トヨタ プリウスα G 5ニンノリ",
  "maker": "トヨタ",
  "makerEn": "Toyota",
  "model": "プリウスα",
  "grade": "G 5ニンノリ",
  "priceJpy": 1050000,
  "totalPaymentJpy": 1173000,
  "year": 2016,
  "mileageKm": 53000,
  "displacementCc": 1800,
  "transmission": "その他AT",
  "repairHistory": false,
  "inspectionUntil": null,
  "inspectionNote": "車検整備付",
  "color": "パールマイカ",
  "bodyType": "ミニバン",
  "driveType": "2WD",
  "engineType": "ハイブリッド",
  "steering": "right",
  "seatingCapacity": 5,
  "doors": 5,
  "dealerName": "ネッツトヨタニューリー北大阪（株） 千里店",
  "dealerPrefecture": "大阪府",
  "prefectureEn": "Osaka",
  "prefectureCode": "27",
  "dealerCity": "吹田市",
  "dealerAddress": "大阪府吹田市山田西１－３６－１０",
  "url": "https://www.carsensor.net/usedcar/detail/AU7231736290/index.html",
  "detailFetched": true,
  "source": "カーセンサーnet (carsensor.net)",
  "sourceUrl": "https://www.carsensor.net/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T13:10:00Z"
}
```

### Input example

```json
{
  "maker": "Toyota",
  "prefecture": "Osaka",
  "model": "プリウス",
  "yearMin": 2016,
  "priceMax": 150,
  "maxItems": 50
}
```

`prefecture` is required (JIS code, Japanese or English name). `maker` is optional and applied upstream (supported: Toyota, Lexus, Nissan, Honda, Mazda, Subaru, Suzuki, Mitsubishi, Daihatsu, Isuzu, Mitsuoka, Hino, Mitsubishi Fuso, UD Trucks, Mercedes-Benz, BMW, Audi, Volkswagen, Porsche, Mini, Volvo, Peugeot, Renault, Citroen, Fiat, Alfa Romeo, Abarth, Jeep, Chevrolet, Ford, Cadillac, Dodge, Chrysler, Tesla, Jaguar, Land Rover, Rolls-Royce, Bentley, Aston Martin, McLaren, Lotus, Ferrari, Lamborghini, Maserati, Smart, Opel, DS, Alpine, Saab, BYD, Hyundai, Kia — Japanese names work too). `model`, `priceMin`/`priceMax` (万円 = 10,000 JPY units) and `yearMin`/`yearMax` filter client-side.

### Pricing

Pay per result — see the pricing tab. A maker × prefecture query is typically hundreds to thousands of vehicles upstream; `maxItems` caps what you take.

### FAQ

**Where does the data come from?**
Live from carsensor.net's public, login-free static list and vehicle detail pages at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

**Is this an official carsensor.net / Recruit service?**
No. **Unofficial**, independently built and maintained, and **not affiliated with or endorsed by Recruit Co., Ltd.** It reads only publicly available pages.

**Are reviews or dealer marketing texts included?**
No. Dealer review scores/texts and reviewer names are **never extracted**, and neither is dealer marketing prose (sales copy, catch-phrases, photo captions) — deliberately: review prose is user-generated copyrighted content, and marketing copy stays on the source site. The output is strictly factual vehicle data plus the dealer's business identity (name/address — business information, not personal data). Phone numbers are never collected.

**Who is responsible for how the data is used?**
You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

**Are prices accurate?**
Prices are what carsensor.net advertised at retrieval time: `priceJpy` is the base vehicle price, `totalPaymentJpy` the advertised total payment including fees. They change constantly — treat them as a snapshot, and re-run for fresh data.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, ~30 vehicles per list page, one extra request per vehicle detail (opt-in), hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If carsensor.net changes its page format, the Actor stops with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails visibly.

### Search terms this Actor answers

carsensor scraper · carsensor.net scraper · Japan used car export data · Japan used car scraper · JDM cars database · Japanese used car prices · Japan used car auction alternative · used car Japan dataset · 中古車 データ · Japan car dealer listings · JDM import sourcing · Japanese domestic market cars · used hybrid Japan · kei truck export

### More Japan data Actors by the same developer

- **Japan Hotels & Ryokan Prices** — hotel/ryokan prices and facility facts from jalan.net.
- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Renewable Energy FIT/FIP Facilities** — METI-certified renewable installations, privacy-safe schema.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's official register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Unofficial tool; not affiliated with Recruit Co., Ltd. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected.*

# Actor input Schema

## `prefecture` (type: `string`):

REQUIRED. Prefecture of the selling dealers: JIS code ("27"), Japanese ("大阪府") or English ("Osaka"). carsensor.net static list pages are prefecture-scoped.

## `maker` (type: `string`):

Optional maker filter, applied upstream via the static maker/prefecture list pages. English ("Toyota"), Japanese ("トヨタ") or a carsensor code ("bTO"). Leave empty for all makers. Unrecognized values fail loudly (the README lists supported makers).

## `model` (type: `string`):

Optional case-insensitive substring filter on the model/grade name (e.g. "プリウス", "Land Cruiser" as published — Japanese usually matches best), applied client-side after parsing.

## `priceMin` (type: `integer`):

Optional lower bound on the base vehicle price, in 万円 (10,000 JPY units — e.g. 50 = ¥500,000). Applied client-side.

## `priceMax` (type: `integer`):

Optional upper bound on the base vehicle price, in 万円. Applied client-side.

## `yearMin` (type: `integer`):

Optional lower bound on the first registration year (初度登録, e.g. 2018). Applied client-side.

## `yearMax` (type: `integer`):

Optional upper bound on the first registration year. Applied client-side.

## `detailFetch` (type: `boolean`):

When true, each vehicle costs one extra request but adds drive type, engine type, steering side, seats, doors, exact color and the dealer's business address. When false (default) the actor emits list data only (name, prices, year, mileage, repair history, transmission, displacement, dealer name/city) — cheaper.

## `maxItems` (type: `integer`):

Stop after this many dataset records.

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to carsensor.net for this run (list pages of 30 vehicles + 1 per vehicle detail when detailFetch is on). Requests are strictly serial with >= 1.2 s spacing. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default: no proxy. Never used for rotation/evasion — one client identity per run.

## Actor input object example

```json
{
  "prefecture": "Osaka",
  "maker": "Toyota",
  "model": "プリウス",
  "detailFetch": false,
  "maxItems": 10,
  "maxApiRequests": 30
}
```

# Actor output Schema

## `records` (type: `string`):

Structured used-car records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "prefecture": "Osaka",
    "maker": "Toyota",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-used-cars-carsensor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "prefecture": "Osaka",
    "maker": "Toyota",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-used-cars-carsensor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "prefecture": "Osaka",
  "maker": "Toyota",
  "maxItems": 10
}' |
apify call jpopendata/japan-used-cars-carsensor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-used-cars-carsensor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fntE4JVFB8SB8KTI7/builds/HdbcnxJ7YEGOIySgB/openapi.json